Essay for you

Essay On Agile Software Development

Category: Essay

Description

Software Development Manager Agile - Leed - All UK, Yorkshire

Job Details

Software Development Manager [Agile] – Leeds - £100K-£125K OTE - Ecommerce
A Software Development Manager is URGENTLY required to join a West Yorkshire based software house and take full responsibility for the day to day management of cross disciplined Agile/Scrum teams and the future strategy of software engineering across design, build and test phases. The successful Software Development Manager would manage a team of 100 [40 onshore/60 offshore] which includes 6 direct reports [Principal Engineers & Product Owners].

As Software Development Manager you would be responsible for the product development of the core internal software platforms, customer CRM platforms and MI/BI platforms. You would manage the overall operation of the software development function responsible for all key decision surrounding quality and standards of all internal and external software. Working closely with IT Architecture you must also ensure alignment of technology roadmaps with appropriate processes, skills and tools. As part of the senior management team the successful Software Development Manager would work closely with business stakeholders to prioritise supply / demand challenges from major programmes.

Required experience:
- Previous experience of leading cross-discipline Agile Software Engineering divisions
- Be an advocate of Agile development & project practices including SCRUM & Kanban
- Have previously shaped IT Test & QA strategy including driven functions towards greater automation
- Previous experience of driving Engineering strategy for Customer facing software products
- Experience of leading cross-discipline Engineering teams that including Developers, QA/Test, BI / MI and CRM
- Experience of identifying leaders, mentoring & coaching staff within the Engineering function
- Experience work collaborating with global teams & partners to share ideas and leverage assets
- Strong vendor / partner relationship management skills including selection & contract negotiation

You would be able to confidently lead and inspire a software team [which includes 6 Software Team Leaders] that delivers a quality product in a fast paced environment and help shape the future direction of their existing/new products. You will help to continue to build a real enthusiasm and passion within the software team that has a focus on quality and pushes to continue to innovate and produce new ideas that will keep their business in front of their competitors.

Salary:
Salary is up to £90,000 p.a

Benefits:
Bonus [up to 30%], Car Allowance [£9,000], Pension [5% matched], 26 days [+5 can be purchased], Critical illness cover [up to £15,000], Life Cover, Healthcare [including partners & dependants], Flexible benefits, Free onsite parking

If you are an experienced Software Development Manager and passionate about well run Agile driven development teams then please click the APPLY NOW button below.

Additionally you can call me on 0161 974 0843 for a confidential discussion.

Please feel free to connect with me on LINKEDIN

Circle Recruitment is acting as an Employment Agency in relation to this vacancy'. Earn yourself a referral bonus if you refer somebody else who fills the role! We also offer an iPad if you refer a new client to us and we recruit for them. Follow us on Facebook - Circle Recruitment. Twitter - @Circle_Rec and LinkedIn - Circle Recruitment.

Other articles

AGILE DEVELOPMENT

Essays about: "Agile development"

Showing result 1 - 5 of 232 essays containing the words Agile development.

1. End-user Data Based Requirements Analysis and Design in Agile Software Development: An Experience Report

University essay from Göteborgs universitet/Institutionen för data- och informationsteknik

Abstract. The purpose of this thesis study is toinvestigate the effects of different end-user datacollection methods. The main research questionconducted in this study is: how can collection andanalysis of data from end-users be used for requirementsanalysis and design of features in agile softwaredevelopment? To carry out the study, we implementeddesign science as our main research methodology. READ MORE

2. Change Resistance in Continuous Integration: An Exploratory Case Study

University essay from Göteborgs universitet/Institutionen för data- och informationsteknik

Abstract. With continuous integration (CI) becoming more and more widely adopted amongsoftware organizations, tackling the resistance during the change process becomes an importantand inevitable step. This paper attempts to identify the change resistance in adopting continuousintegration and its corresponding mitigation strategies. READ MORE

3. Backlogs as a Communication Medium in Co-located and Distributed Agile Teams

University essay from Göteborgs universitet/Institutionen för data- och informationsteknik

Abstract. While uncommon, combining multiple forms of backlogs and scaled agile development is a challenge undertaken by some companies. This paper reports a study on communication with agile practices in a global software development organization distributed between three countries. READ MORE

4. Quality metrics in continuous delivery. A mixed approach

University essay from Blekinge Tekniska Högskola/Institutionen för programvaruteknik; Blekinge Tekniska Högskola/Institutionen för programvaruteknik

Abstract. Context.Continuous delivery deals with concept of deploying the user stories as soon as they are finished rather than waiting for the sprint to end. READ MORE

5. Application and evaluation of methods for merging user experience design with agilesoftware development

University essay from Umeå universitet/Institutionen för tillämpad fysik och elektronik

Abstract. Cinnober is an organization that develops advanced software solutions for financial institutions. As a part of the technology toolkit used at Cinnober there is a web framework with which GUI development can be driven from the data available on the server, through configuration rather than development. READ MORE

References by Author - Agile Software Development: The Cooperative Game (2nd Edition)

References by Author A

Alleman, G. Henderson, M. "Making Agile Development Work in a Government Contracting Environment: Measuring velocity with Earned Value," June 2003, online at <http://www.niwotridge.com/PDFs/ADC%20Final.pdf>.

Allen, T. Managing the Flow of Technology: Technology and the Dissemination of Technological Information Within the R & D Organization. MIT Press, Boston, 1984.

Ambler, S. "The Agile Edge: How Agile Are You?" Software Development. December 2005, online at <http://www.ddj.com/showArticle.jhtml;?articleID=184415445>.

Ambler, S. Jefferies, R. Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process. John Wiley & Sons, Inc. New York, 2002.

Anderson, D. Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results. Prentice-Hall PTR, Upper Saddle River, NJ, 2003.

Anderson, D. "Managing Lean Software Development with Cumulative Flow Diagrams," May 2004, BorCon 2004, online at <http://bdn1.borland.com/borcon2004/article/paper/0,1963,32096,00.html> or <http://www.agilemanagement.net/Articles/Papers/BorConManagingLeanDevWithCFDs.pdf>.

Anderson, D. Dumitriu, D. "From Worst to Best in 9 Months: Implementing a Drum-Buffer-Rope Solution in Microsoft's IT Department," November 2005, online at <http://www.agilemanagement.net/Articles/Papers/From_Worst_to_Best_in_9_Months_Final_1_3.pdf>.

Auer, K. Miller, R. Extreme Programming Applied: Playing to Win. Addison-Wesley, Boston, 2002.

Augustine, S. Managing Agile Projects. Prentice-Hall PTR, Upper Saddle River, NJ, 2005.

Austin, R. Measuring and Managing Performance in Organizations. Dorset House, New York, 1996.

Austin, R. Devin, L. Artful Making: What Managers Need to Know about How Artists Work. Pearson Education publishing as Financial Times Prentice Hall, Upper Saddle River, NJ, 2003.

B

Bach, J. <www.satisfice.com>.

Beck, K. Cunningham, W. "A laboratory for teaching object-oriented thinking," ACM SIGLPLAN 24(10):1-7, 1989.

Beck, K. Extreme Programming Explained: Embrace Change. Addison-Wesley, Boston, 2000.

Beck, K. Andres, C. Extreme Programming: Embrace Change (2nd Ed.). Addison-Wesley Professional, Boston, 2004.

Beck, K. Fowler, M. Planning Extreme Programming. Addison-Wesley, Boston, 2001.

Becker, S. Whittaker, J. Cleanroom Software Engineering Practices. Idea Group Publishing, Hershey, PA, 1996.

Boehm, B. "Get Ready for Agile Methods, With Care," Computer. Vol. 35, No. 1, January 2002, pp. 64-69.

Boehm, B. Turner, R. Balancing Agility and Discipline: A Guide for the Perplexed. Addison-Wesley, Boston, 2003.

Booch, G. Object-Oriented Analysis & Design with Applications. Benjamin-Cummings, San Francisco, 1994.

Booch, G, Object Solutions: Managing the Object-Oriented Project. Pearson Education, Menlo Park, CA, 1996.

Bordia, P. Prashant, K. "Face-to-face versus computer-mediated communications: A synthesis of the literature," The Journal of Business Communication 34(1), U of Illinois, Champaign, IL, Jan 1997, pp. 99-120.

Brooks, F. "No Silver Bullet: Essence and Accidents of Software Engineering," in The Mythical Man-Month: Essays on Software Engineering. 2nd Ed. Addison-Wesley, Reading, MA, 1995, pp. 177-204, online at <http://www.inst.eecs.berkeley.edu/

Brown, K. Klastorin, T. Valluzzi J. "Project Performance and the Liability of Group Harmony," IEEE Transactions on Engineering Management. 37(2), May 1990, pp. 117-125.

Burns, C. Dishman, E. Verplank, W. Lassiter, B. "Actors, Hairdos & VideotapeInformance Design: Using performance techniques in multi-disciplinary, observation based design," Computer Human Interaction '94 Conference Companion. Boston, April 24-28, pp.119-120.

C

The "C3" Team, "Chrysler goes to 'Extremes'", in Distributed Object Computing. October, 1998, pp. 24-28.

Cerasoli, R. "A History of Central Artery/Tunnel Project Finances 1994-2001: Report to the Treasurer of the Commonwealth," Office of the Inspector General, Commonwealth of Massachusetts, March 2001, online at <http://www.state.ma.us/ig/publ/cat01rpt.pdf>.

Charan, R. "Home Depot's Blueprint for Culture Change," Harvard Business Review. April, 2006, pp. 60-70.

Chase, T. "Revelation 13: The Big Dig," 1998-2006, online at <http://www.revelation13.net/bigdig.html>.

Coad, P. Java Modeling in Color with UML. Prentice-Hall, Upper Saddle River, NJ, 1999.

Cockburn, A. "Structuring Use Cases with Goals," Humans and Technology Technical Report 1995.01. 1995, online at <http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals>.

Cockburn, A. Surviving Object-Oriented Projects. Addison-Wesley, Reading, MA, 1998.

Cockburn, A. "The Expert-in-Earshot Project Management Pattern", in Succi, G. Marchesi, M. Extreme Programming Examined. Addison-Wesley, Boston, 2001, pp. 245-247. (Cockburn 2001a)

Cockburn, A. Williams, L. "The costs and benefits of pair programming", in Succi, G. Marchesi, M. Extreme Programming Examined. Addison-Wesley, Boston, 2001, pp. 223-247. (Cockburn 2001b)

Cockburn, A. Writing Effective Use Cases. Addison-Wesley, Boston, 2001. (Cockburn 2001c)

Cockburn, A. "Agile Software Development Joins the "Would-Be" Crowd," Cutter IT Journal. January 2002, Vol. 15 No. 1, pp. 6-12, online at <http://alistair.cockburn.us/index.php/Agile_joins_the_would-be_crowd>. (Cockburn 2002a)

Cockburn, A. "Learning from Agile Software Development," parts 1 and 2, CrossTalk: The Journal of Defense Software Engineering. October 2002, pp. 10-14, and Nov, 2002, pp. 9-12, online at <http://www.stsc.hill.af.mil/crosstalk/2002/10/cockburn.html> and <http://www.stsc.hill.af.mil/crosstalk/2002/11/cockburn.html>. (Cockburn 2002b)

Cockburn, A. "ADC 2003 vision statement," July 2003, online at <http://alistair.cockburn.us/index.php/ADC_2003_vision_statement>. (Cockburn 2003a)

Cockburn, A. "The "Cone of Silence" strategy and related project management strategies," Humans and Technology Technical Report 2003.01, 2003, online at <http://Alistair.Cockburn.us/index.php/The_%22Cone_of_Silence%22_strategy_and_related_project_management_strategies>. (Cockburn 2003b)

Cockburn, A. "Process: the fourth dimension," Humans and Technology Technical Report 2003.02, 4 October 2003, online at <http://Alistair.Cockburn.us/index.php/Process:_the_fourth_dimension>. (Cockburn 2003c)

Cockburn, A. "Extending an Architecture as it Earns Business Value," Humans and Technology Technical Report TR 2004.01, Jan 14 2004, online at <http://alistair.cockburn.us/index.php/Extending_an_architecture_as_it_earns_business_value>. (Cockburn 2004a)

Cockburn, A. "The end of software engineering and the start of economic-cooperative gaming," Computer Science and Information Systems Journal. Comsis Consortium, University of Belgrade, Serbia and Montenegro, Vol 1. No. 1, February 2004, pp. 1-32, online at <http://Alistair.Cockburn.us/index.php/The_end_of_software_engineering_and_the_start_of_economic-cooperative_gaming>. (Cockburn 2004b)

Cockburn, A. "What the Agile Toolkit Contains," CrossTalk: The Journal of Defense Software Engineering. Nov. 2004, online at <http://www.stsc.hill.af.mil/crosstalk/2004/11/0411cockburn.html>. (Cockburn 2004c)

Cockburn, A. Crystal Clear: A Human-Powered Methodology for Small Teams. Addison-Wesley, Boston, 2005. (Cockburn 2005a)

Cockburn, A. "The Hexagonal (Ports & Adapters) Architecture," Humans and Technology Technical Report TR 2005.02, Sept 4, 2005, online at <http://alistair.cockburn.us/index.php/Hexagonal_architecture>. (Cockburn 2005b)

Cockburn, A. "A Governance Model For Agile and Hybrid-Agile Projects," Humans and Technology Technical Report 2005.03, September 2005, online at <http://Alistair.Cockburn.us/index.php/A_governance_model_for_agile_projects>. (Cockburn 2005c)

Cockburn, A. "Are Iterations Hazardous to Your Project?" Humans and Technology Technical Report 2005.04, 9 September 2005, online at <http://Alistair.Cockburn.us/index.php/Are_iterations_hazardous_to_your_project%3F>. (Cockburn 2005d)

Cockburn, A. "Two Case Studies Motivating 'Efficiency' as a Spendable Quantity," International Conference on Agile Manufacturing (Keynote), Helsinki, Finland, 23 September 2005, online at <http://alistair.cockburn.us/index.php/Image:Efficiencyasaspendablequantity020.ppt>. (Cockburn 2005e).

Cohn, M. User Stories Applied: For Agile Software Development. Addison-Wesley, Boston, 2004.

Cohn, M. Agile Estimating and Planning. Prentice Hall PTR, Upper Saddle River, NJ, 2005.

Constantine, L. Constantine on Peopleware. Yourdon Press, Englewood Cliffs, NJ, 1995

Constantine, L. Lockwood, L. Software for Use. Addison-Wesley, Boston, 1999.

Constantine, L. Lockwood, L. "Structure and Style in Use Cases for User Interface Design," In Mark Van Harmelen (ed.), Object-Modeling and User Interface Design. Addison-Wesley, Boston, 2001, online at <http://www.foruse.com/articles/structurestyle2.pdf>.

Conway, J. On Numbers and Games. Academic Press, London, 2000.

Coplien, J. Harrison, N. Organizational Patterns Of Agile Software Development. Prentice Hall PTR, Upper Saddle River, NJ, 2005, online at <http://www.bell-labs.com/cgiuser/OrgPatterns/OrgPatterns?OldOrgPatterns>.

Csikszentmihalyi, M. Flow: The Psychology of Optimal Experience. HarperCollins, New York, 1991.

Cummins, D. "The Development Game," C/C++ Journal. Vol. 20, No. 10, October 2002, pp. 18, 20-21, online at <http://www.ddj.com/184401568>.

Curtis, P. Dixon, M. Frederick, R. Nichols, D. "The Jupiter Audi/Video Architecture: Secure Multimedia in Network Places" in Proceedings of ACM Multimedia '95. San Francisco, pp. 79-90.

D

Dawkins, R. The Selfish Gene. Oxford University Press, Oxford, 1990.

DeCarlo, D. eXtreme Project Management: Using Leadership, Principles, and Tools to Deliver Value in the Face of Volatility. Jossey-Bass, San Francisco, 2004.

DeMarco, T. Lister, T. Peopleware: Productive Projects and Teams. 2nd Ed. Dorset House, New York, 1999.

Denne, M. Cleland-Huang, J. Software by Numbers: Low-Risk, High-Return Development. Prentice Hall PTR, Upper Saddle River, NJ, 2003.

Dixon, N. Common Knowledge: How Companies Thrive by Sharing What They Know. Harvard Business School Press, Boston, 2000.

E

Ehn, P. Work-Oriented Development of Software Artifacts. Arbetslivscentrum, Stockholm, 1988.

Ehn, P. "Scandinavian Design: On Participation and Skill", in Usability: Turning Technologies into Tools. P. S. Adler and T. A. Winograd, editors, Oxford University Press, New York, 1992, pp. 96-132, online at http://www.ilt.columbia.edu/Publications/papers/Ehn.html.

Evans, E. Domain-Driven Design: Tackling Complexity in the Heart of Software. Addison-Wesley, Boston, 2003.

F

Fox, R. "Shu Ha Ri", The Iaido Newsletter. 7(2), #54, February 1995, online at http://www.aikidofaq.com/essays/tin/shuhari.html.

Frakes, W. Fox, C. "Sixteen questions about software reuse," Communications of the ACM. 38(6): 75-87, 1995.

G

Gamma, E. Helm, R. Johnson, R. Vlissides, J. Design Patterns. Addison-Wesley, Boston, 1995.

Gladwell, M. Blink: The Power of Thinking Without Thinking. Little, Brown and Company, New York, 2005.

Glass, R. Vessey, I. Conger, S. "Software tasks: intellectual or clerical?," Information and Management. 23(4), Oct. 1992, pp. 183-191.

Glass, R. Software Creativity. Prentice-Hall, Upper Saddle River, NJ, 1995.

Goel, V. Sketches of Thought. MIT Press, Boston, 1995.

Goldman, S. Nagle, R. Preiss, K. Agile Competitors and Virtual Organizations. John Wiley & Sons, New York, 1995.

Goldratt, E. Theory of Constraints. North River Press, Great Barrington, MA, 1990.

Goldratt, E. The Goal. North River Press, Great Barrington, MA, 1992.

Goldratt, E. Critical Chain. North River Press, Great Barrington, MA, 1997.

Graham, I. Henderson-Sellers, B. Younessi, H. The OPEN Process Specification. Addison-Wesley, Boston, 1997.

Gries, D. The Science of Programming. Springer-Verlag, New York, 1987.

Guindon, R. Curtis, B. "Insights from empirical studies of the software design process", Future Generation Computer Systems. 7(2-3), April, 1992, pp.139-149.

H

Hammer, M. Champy, J. Reengineering the Corporation: A Manifesto for Business Revolution. HarperBusiness, New York, 1994.

Hammer, M. The Reengineering Revolution. Collins, New York, 1995.

Harmelen, M. Object-Modeling and User Iterface Design. Addison-Wesley, Boston, 2001.

Herring, R. Rees, M. "Internet-Based Collaborative Software Development Using Microsoft Tools," in Proceedings of the 5th World Multiconference on Systemics, Cybernetics and Informatics (SCI'2001), 22-25 July 2001, Orlando, FL. online at http://erwin.dstc.edu.au/Herring/SoftwareEngineeringOverInternetSCI2001.pdf>.

Highsmith, J. Adaptive Software Development. Dorset House, New York, 2000.

Highsmith, J. Agile Project Management: Creating Innovative Products. Addison-Wesley, Boston, 2004.

Hill, A. Wooden, J. Be Quick - But Don't Hurry. Simon and Schuster, New York, 2001.

Hock, D. Birth of the Chaordic Age. BerretKoehler, San Francisco, 1999.

Hohmann, L. Journey of the Software Professional. Prentice-Hall, Upper Saddle River, NJ, 1997.

Holtzblatt, K. Burns Wendell, J. Wood, S. Rapid Contextual Design: A How-To Guide to Key Techniques for User-Centered Design. Elsevier, San Francisco, 2004.

Hovenden, F. "A Meeting and A Whiteboard (describing the power to speak)," in Proceedings of the 4th World Multiconference on Systemics, Cybernetics and Informatics (SCI'2001), July 2000, Orlando, FL.

Humphrey, W. A Discipline for Software Engineering. Addison-Wesley, Boston, 1995.

Humphrey, W. Introduction to the Personal Software Process. Addison-Wesley, Boston, 1997.

Hunt, A. Thomas, D. The Pragmatic Programmer: From Journeyman to Master. Addison-Wesley, Boston, 2000.

I

IBM Object-Oriented Technology Center, Developing Object-Oriented Software: An Experience-Based Approach. Prentice-Hall, Upper Saddle River, NJ, 1997.

J

Jeffries, R. Hendrickson, C. Anderson, A. Extreme Programming Installed. Addison-Wesley, Boston, 2001.

Jeffries, R. "A Metric Leading to Agility," Xprogramming: an Agile Software Development Resource, 14 June 2006, online at <http://www.xprogramming.com/xpmag/jatRtsMetric.htm>.

Johnson-Laird, P. Byrne, R. Deduction. Lawrence Erlbaum Associates, Mahwah, NJ, 1991.

K

Keil, M. Carmel, E. "Customer-Developer Links," Communications of the ACM. May 1995, pp.33-44.

Kerth, N. Project Retrospectives: A Handbook for Team Reviews. Dorset House, New York, 2001.

Klein, G. Sources of Power: How People Make Decisions. MIT Press, Cambridge, MA, 1999.

Knuth, D. The Art of Computer Programming. Vol. 1-3. Addison-Wesley, Reading, MA, 1997, 1998.

Kohn, A. Punished By Rewards: The Trouble with Gold Stars, Incentive Plans, A's, Praise, and Other Bribes. Houghton Mifflin, Boston, 1999, online at <http://www.gnu.org/philosophy/motivation.html>.

Krutchen, P. The Rational Unified Process. Addison-Wesley, Boston, 1999

L

Laubacher, R. Malone, T. "Retreat of the Firm and Rise of the Guilds: The Employment Relationship in an Age of Virtual Business," M.I.T. Sloan School of Management 21st Century Initiative Working Paper #33, August 2000.

Larman, C. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process. 2nd Ed. Prentice-Hall, Upper Saddle River, NJ, 2002.

Larman, C. Agile and Iterative Development: A Manager's Guide. Addison-Wesley, Boston, 2003.

Laubacher, R. Malone, T. "Retreat of the Firm and Rise of the Guilds: The Employment Relationship in an Age of Virtual Business," MIT Sloan School of Management 21st Century Initiative Working Paper #33, August 2000.

Laufer, A. Simultaneous Management: Managing Project in a Dynamic Environment. American Management Association, New York, 1997.

Lave, J. Wenger, E. Situated Learning: Legitimate Peripheral Participation. Cambridge University Press, Cambridge, 1991.

Liker, J. The Toyota Way: 14 Management Principles From The World's Greatest Manufacturer. McGraw Hill, New York, 2003.

M

Maier, M. Rechtin, E. The Art of Systems Architecting. 2nd Ed. CRC Press, Boca Raton, FL, 2000.

Manns, M. Rising, L. Fearless Change: Patterns for Introducing New Ideas. Addison-Wesley, Boston, 2004.

Marcus, A. Big Winners and Big Losers: The 4 Secrets of Long-Term Business Success and Failure. Wharton School Publishing, Upper Saddle River, NJ, 2005.

Martin, J. Odell, J. Object Oriented Methods, Pragmatic Considerations. Prentice-Hall, Upper Saddle River, NJ, 1996.

Martin, R. "Estimating Prices Up Front," Online posting, 26 September 2004 7:42 am. Google Groups discussion, comp software.extreme-programming, <http://www.google.com/>, Path: More; Groups; Search for a Group "comp software extreme programming"; Comp.software.extreme-programming; Search This Group "estimating costs up front"; Estimating Costs Up Front; 25 Robert C.Martin (try <http://tinyurl.com/m2gb8>).

Mathiassen, L. Stage, J. "Informatics as a Multi-Disciplinary Education," in Scandinavian Journal of Information Systems. Vol. 11, No. 1, 1999.

Mathiassen, L. Pries-Heje, J. Ngwenyama, O. Improving Software Organizations. Addison-Wesley, Boston, 2002.

Maturana, H. Varela, F. The Tree of Knowledge: The Biological Roots of Human Understanding. Shambala Publications, Boston, 1998.

McCarthy, J. Dynamics of Software Development. Microsoft Press, Redmond, WA, 1995.

McCarthy, J. Monk, A. "Channels, conversation, cooperation and relevance: all you wanted to know about communication but were afraid to ask," in Collaborative Computing. Vol. 1, No. 1, March 1994, pp. 35-61.

McCarthy, J. McCarthy, M. Software for Your Head: Core Protocols for Creating and Maintaining Shared Vision. Addison-Wesley, Boston, 2002.

Meszaros, G. "Using Storyotypes to Split Bloated User Stories," Proceedings of the 2004 XP/Agile Universe conference, pp. 73-80, online at <http://storyotypespaper.gerardmeszaros.com/>.

Musashi, M. Cleary, T. (translator), The Book of Five Rings. Shambala Publications, Boston, 2000, online at <http://www.samurai.com/5rings/>.

N

NASA, "Deorbit flight software lessons learned," JSC38609, NASA Johnson Space Center, 19 January, 1998.

Naur, P. "Programming as Theory Building", Computing: A Human Activity. ACM Press, 1992, pp.37-48.

Naur, P. Randell, B. Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 October 1968, Brussels, Scientific Affairs Division, NATO. Eds. P. Naur and B. Randell. 1969, online at <http://homepages.cs.ncl.ac.uk/brian.randell/NATO/>.

Newkirk, J. Martin, R. Extreme Programming in Practice. Addison-Wesley, Boston, 2001.

O

O'Dell, C. Grayson, C. J. Jr. If Only We Knew What We Know: The Transfer of Internal Knowledge and Best Practice. The Free Press, New York, 1998.

Ohno, T. Toyota Production System: Beyond Large-Scale Production. Productivity Press, Portland, OR, 1988.

Ogunnaike, B. Ray, W. Process Dynamics, Modeling, and Control. Oxford University Press, Oxford, England, 1992.

Olson, G. Olson, J. "Distance matters," Human-Computer Interaction. Vol. 15, 2001, pp. 139-179.

Orbanes, P. "Everything I know about business I learned from monopoly," Harvard Business Review. Vol. 80, No. 3, March 2002, pp. 51-57.

Owen, H. Open Space Technology: A User's Guide. 2nd Ed. Berrett-Koehler Publishers, San Francisco, 1997.

P

Patton, J. "Usage Centered Design in Extreme Programming and Agile Development Environments," in the ForUSE Conference, October 20, 2003.

Patton, J. "It's all in how you slice it: Design your project in working layers to avoid half-baked incremental releases," Better Software. Jan 2005, pp. 16-22, 40, online at <http://www.abstractics.com/papers/HowYouSliceIt.pdf>.

Piattelli-Palmarini, M. Inevitable Illusions: How Mistakes of Reason Rule Our Minds. John Wiley and Sons, New York, 1996.

R

Raymond, E. "Homesteading the Noosphere," <http://tuxedo.org/

Reinertsen, D. Managing the Design Factory: A Product Developer's Toolkit. The Free Press, New York, 1997.

Rich, B. Janos, L. Skunk Works: A Personal Memoir of My Years at Lockheed. Little, Brown and Company, Boston, 1994.

Rigby, D. Vishwanath, V. "Localization: The Revolution in Consumer Markets," Harvard Business Review. April 2006, pp. 82-92.

Rusk, J. "Agile Charts," 30 July 2005, online at <http://www.agilekiwi.com/agile_charts.htm>.

S

Satir, V. "From Virginia Satir: Models of Perceiving the World: Attitude Toward Change," in Couples Therapy in Managed Care: Facing the Crisis. B. Brothers (Ed.), Haworth Press, Binghamton, 1999, p. 4.

Schön, D. The Reflective Practitioner: How Professionals Think in Action. Basic Books, United States of America, 1983.

Schwaber, K. Beedle, M. Agile Software Development with Scrum. Prentice-Hall, Upper Saddle River, NJ, 2002.

Schwaber, K. Agile Project Management with Scrum. Microsoft Press, Redmond, WA, 2004.

Shannon, C. Weaver, W. Mathematical Theory of Communication. U. of Illinois Press, Champaign, IL, 1963.

Shrage, M. "The Proto Project," in Fast Company. May 1999, p. 138, online at <http://www.fastcompany.com/online/24/schrage.html>.

Schwaber, K. Beedle, M. Scrum: Agile Software Development. Prentice-Hall, Upper Saddle River, NJ, 2002, online at http://www.controlchaos.com).

Sillince, J. A. "A model of social, emotional and symbolic aspects of computer-mediated communication within organizations," in Computer Supported Cooperative Work. Vol. 4, 1996, pp. 1-31.

Simon, H. The Sciences of the Artificial. MIT Press, Boston, 1987.

Stapleton, J. DSDM Dynamic Systems Development Method: The Method in Practice. Addison-Wesley, Boston, 1997.

Stapleton, J. DSDM: Business-Focused Development, Second Edition. Addison-Wesley, London, 2003.

Sullivan, K, Chalasani, P. Jha, S. Sazawal, V. "Software Design as an Investment Activity: A Real Options Perspective," in Real Options and Business Strategy: Applications to Decision Making. L. Trigeorgis (Ed.), Risk Books, December 1999.

Sully, P. "Liveware matters," EXE Magazine. 3(1), June, 1988, pp.42-46.

T

Torvalds, L. D. Diamond, Just for Fun: The Story of an Accidental Revolution. HarperBusiness, New York, 2001.

W

Webb, D. Humphrey, W. "Using TSP on the TaskView Project," in CrossTalk, The Journal of Defense Software Engineering. February 1999, pp. 3-10, online at <http://www.stsc.hill.af.mil/crosstalk/1999/feb/webb.asp>.

Weick, K. The Social Psychology of Organizing. 2nd Ed. McGraw-Hill, New York, 1979.

Weick, K. Making Sense of the Organization. Blackwell Business, Oxford, 2001.

Weick, K. Sutcliffe, K. Managing the Unexpected: Assuring High Performance in an Age of Complexity. Jossey-Bass, San Francisco, 2001.

Weinberg, G. The Psychology of Computer Programming. Silver Edition. Dorset House, New York, 1998.

Wilkinson, N. Using CRC Cards: An Informal Approach to Object-Oriented Development. SIGS Books and Multimedia, New York, 1995.

Wirfs-Brock, R. Wilkerson, B. Wiener, L. Designing Object-Oriented Software. Prentice-Hall, Upper Saddle River, NJ, 1990.

Wirfs-Brock, R. McKean, A. Object Design: Roles, Responsibilities, and Collaborations. Addison-Wesley, 2003.

Womack, J. Jones, D. Roos, D. The Machine That Changed the World: The Story of Lean Production. Harper Perennial, NewYork, 1991.

Wright, O. How We Invented the Airplane: An Illustrated History. F. Kelly (Ed.), Dover, 1953.

Wysocki, R. Effective Project Management: Traditional, Adaptive, Extreme. 3rd Ed. Wiley Publishing, Inc. Indianapolis, 2003.

X

Extreme Programming, <http://extremeprogramming.com>.

Y

Yourdon, E. Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects. Prentice-Hall, Upper Saddle River, NJ, 1997.

Disciplined Agile Software Development: Definition

A lot of people have been asking the question "What is Agile Software Development?" and invariably they get a different definition depending on who they ask. Many people will correctly say that agile software development conforms to the values and principles of the Agile Manifesto, and those sites are clearly great resources. But, if you're looking for a "sound bite" definition of agile software development, that's a little harder to come by. Furthermore, the definition that you get might not promote the level of maturity, or perhaps discipline is a better word, that you're hoping to achieve. Here's a definition that I think is pretty good (the layout of the points may be important) which I hope you find useful. Disciplined agile software development is:

An iterative and incremental (evolutionary) approach to software development

which is performed in a highly collaborative manner

by self-organizing teams within an effective governance framework

with "just enough" ceremony

that produces high quality solutions

in a cost effective and timely manner

which meets the changing needs of its stakeholders.

You might find my articles The Criteria for Determining Whether a Team is Agile. Examining the Agile Manifesto. and Agile System Development Lifecycle (SDLC) to be interesting introductions to agile software development. Also, my various agile surveys provide some insight into the how Agile is being adopted within organizations.





Share with friends:

Let Us Help

We actively work with clients around the world to improve their information technology (IT) practices, typically in the role of mentor/coach, team lead, or trainer. A full description of what we do, and how to contact us, can be found at Scott Ambler + Associates .

Recommended Reading

This book, Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise describes the Disciplined Agile Delivery (DAD) process decision framework. The DAD framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and provides the foundation for scaling agile. This book is particularly important for anyone who wants to understand how agile works from end-to-end within an enterprise setting. Data professionals will find it interesting because it shows how agile modeling and agile database techniques fit into the overall solution delivery process. Enterprise professionals will find it interesting beause it explicitly promotes the idea that disciplined agile teams should be enterprise aware and therefore work closely with enterprise teams. Existing agile developers will find it interesting because it shows how to extend Scrum-based and Kanban-based strategies to provide a coherent, end-to-end streamlined delivery process.

The Object Primer 3rd Edition: Agile Model Driven Development with UML 2 is an important reference book for agile modelers, describing how to develop 35 types of agile models including all 13 UML 2 diagrams. Furthermore, this book describes the fundamental programming and testing techniques for successful agile solution delivery. The book also shows how to move from your agile models to source code, how to succeed at implementation techniques such as refactoring and test-driven development(TDD). The Object Primer also includes a chapter overviewing the critical database development techniques ( database refactoring. object/relational mapping. legacy analysis. and database access coding) from my award-winning Agile Database Techniques book.

Agile Methodology Essay 2 - Research Paper - 2961 Words

Agile Methodology Essay 2

Agile methods are one of the most recently conceived methodologies for developing software intensive systems. Agile methods refer to a family of methods that tend to favor working code over documentation, individuals over tools, collaboration over negotiation and thriving in volatile environments over following a plan ("Agile Manifesto" 2001). However, agile methods are not indicated for all projects; project managers, with organizational support, must decide if agile methods will provide the most benefit over conventional software engineering methods for developing new software intensive projects. What I hope to ascertain is that agile methods are probably not appropriate for large, stable, well understood, long lasting projects but are well suited for rapidly deployed systems that require responsive, flexible development with smaller, short-term projects. The additional prerequisites are that the software provider's organization must be willing to support such methods and that there is sufficient collaboration from a knowledgeable customer base. This paper will briefly present background material for the introduction and motivation for agile methods. Next, the critical factors that influence the selection of software development methodology is discussed, comparing agile and conventional methods. Then, using these observations, a single software development application is examined to determine if agile methods would be appropriate.

Background
Methodologies are one of four major factors that need to be taken into consideration in the field of software engineering (Nance, slide 40, Session 1). Methodologies are an organized, documented set of rules and practices that provide a framework to guide a software project from concept, requirements collection, and design, through implementation maintenance and retirement of the product. Rico (n.d.) describes five major periods covering 50 years of computer history (mainframe, midrange, micro, internet and personal) and identifies 32 of the foremost methodologies that emerged within each time period. His work shows that essentially, methodologies evolved as a reaction to a) failures or inadequacies of earlier methods, b) opportunities arising from the revolution in technology or c) changes in business perspectives including information-age economics. Conventional methodologies, such as Structured and Object Oriented (OO) methodologies are also known as heavyweight methodologies because they typically include numerous rules, and documents, require a lot of time to develop and bureaucratic in nature (Fowler, 2003; Cockburn n.d.). However, even with the structured nature of these methodologies, the majority of software projects developed has not produced software products that are within budget; meet their performance goals; or success criteria (Nance, slide 15, Session 1). Other names for heavy weight methodologies include plan-driven, rigorous, predictive and "thick". In contrast, lightweight methodologies have few rules and practices; strive for a compromise between no process and unwarranted process, favor working code over excessive document and collaboration over contract negotiation (Constantine, 2002; "Agile Manifesto" 2001). Light weight methodologies go by names such as agile, adaptive and "thin". These light weight or agile methods are characterized by small releases, collaborative communications between developers and customers, simplicity and their ability to react quickly to changing requirements (Abrahamsson, 2003; "Agile Manifesto" 2001). Figure 1, Evolutionary map of agile methods, depicts the evolution of agile methods in time. Figure 1. Evolutionary map of agile methods. Source: Abrahamsson (2003), figure 1 page 246.

Selecting a methodology
Deciding what software development methodology to implement depends on many factors such as project priorities and project types. Project priorities would include factors such as scheduling, quality and.

Please sign up to read full document.

YOU MAY ALSO FIND THESE DOCUMENTS HELPFUL

Introduction to AgileMethodology What is Agile . Agilemethodology is an approach to the project management which help to respond to the unpredictability of building software through incremental, iterative work cadences, known as sprints. This methodology was developed to deal with situation where the waterfall model fails. The biggest drawback of waterfall model is that it assumes that every requirement of.

2132 Words | 7 Pages

A Survey of Agile Development MethodologiesAgile development methodologies are emerging in the software industry. In this chapter, we provide an introduction to agile development methodologies and an overview of four specific methodologies . • Extreme Programming • Crystal Methods • Scrum • Feature Driven Development Plan-driven methods work best when developers can determine the requirements in.

8016 Words | 26 Pages

Agile Development Methodology Q.NO.1 Why are agile development methodology considered by many to be the best approach to software development for small projects? Also briefly explain the agile software development methods. Answer Introduction Agile methods have become so popular in last few years because of their in time development, total quality management and continuous process improvement.

620 Words | 3 Pages

Systems Analysis | AgileMethodology | A Short Story | Dan Burns 1/23/2010 | 1/23/2010 AgileMethodology The Paper Basically what I have been able to relate too is that AgileMethodology is a process of small groups of people (teams) that are located in the same place working together. They communicate either through e-mail, voice mail, or direct contact. There is little documentation because.

897 Words | 4 Pages

Abstract 3 2 . Keywords 4 3. Introduction 5 4. Literature Review 6 4.1. The V-Model 6 4.2. AgileMethodology 6 4.3. Comparative study of V-Model V/S Agile 8 4.3.1. V-model 8 4.3.2. Agile 8 5. Project Management Techniques Comparison 9 5.1. Constructive Cost Model (COCOMO) 9 5.1.1. V-Model 9 5.1.2. Agile 10 5.2. Earned Value Management (EVM) 10 5.2.1. V-Model 10 5.2.2.

2703 Words | 14 Pages

AgileMethodology What Is Agile . Agilemethodology is an approach to project management, typically used in software development. It helps teams respond to the unpredictability of building software through incremental, iterative work cadences, known as sprints. But before discussing agilemethodologies further, it’s best to first turn to the methodology that inspired it: waterfall.

4954 Words | 17 Pages

Methodologyessay While conducting research there are many different methods in which to find out results. It is essential to use and carry out the best form of research technique in order to gain the best and most accurate results for the intended piece of research. Firstly the researcher should be able to identify if they need primary or secondary research to gain data upon before they start identifying which different techniques they should use. Primary.

1419 Words | 4 Pages

Chapter 3 Methodology The methodology used by the proponents is the classical waterfall model. The waterfall model is the classical model of software engineering. This model is one of the oldest models and is widely used in government projects and in many major companies. As this model emphasizes planning in early stages, it ensures design flaws before they develop. In addition, its intensive document and planning make it work well for projects in which quality.

681 Words | 3 Pages