1 Discipline vs. Agility. 2 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors.

Slides:



Advertisements
Similar presentations
Feb Alten Group Started in France in 1988 Currently more than people Presence in 10 countries Active in The Netherlands since 2002.
Advertisements

SOFTWARE DEVELOPMENT METHODOLOGIES Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM RUP.
SDLC – Beyond the Waterfall
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
Alternate Software Development Methodologies
An Agile ETL Data Development for ERA XML Submission Dr Paul Wong Research Office, Australian National University.
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
Agile development By Sam Chamberlain. First a bit of history..
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
1 Agile Methodologies in DoD Software By Cynthia Johnson.
Software Life Cycles ECE 417/617: Elements of Software Engineering
Agile Software Development. Traditional Software Development 1.Initiation (RFP) 2.Feasibility study Technical – can we build it? Economic – should we.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Programming with eyes wide open. Your host today Subby Angelov Team
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
An Agile View of Process
Introduction to Agile Methodologies and Concepts Roy Osherove Principal, Team Agile Blog : ISerializable.com.
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Chapter 3 – Agile Software Development Lecture 1 1Chapter 3 Agile software development That's been one of my mantras - focus and simplicity. Simple can.
Chapter 3 – Agile Software Development Lecture 1 1Chapter 3 Agile software development.
Discipline vs. Agility Report by Jason Cradit.
Software Engineering Modern Approaches
Chapter 4 Agile Development
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
Chapter 4 Agile Development 1. The Manifesto for Agile Software Development 2 “We are uncovering better ways of developing software by doing it and helping.
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
Balancing Agility and Discipline A Guide for the Perplexed By: Barry Boehm and Richard Turner EECS 811: Software Project Management Presented By: Gabe.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Balancing Agility and Discipline Chapter 2 : Contrasts and Home Grounds Presented By: Shawn Mulkey.
Balancing Agility and Discipline Chapter 4 Sharon Beall EECS 811 April 22, 2004.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Chapter 3 Agile Software Development (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 4 Agile Development Discussion of Agile Development and Agile Process.
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Agile Software Development By Kshitij Limaye CSC 532.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Steve Lundquist, PMP, M.Sc..  As a PMP certified program manager, there are numerous tools, processes, methodologies, and tricks that are available to.
Agile Gintarė Bernotaitytė © 2013.
Chapter 3 Agile software development 1 Chapter 3 – Agile Software Development.
Chapter 5 Agile Development Moonzoo Kim KAIST
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Project Management Athanasios Podaras
Agile Methods Agile Alliance
… but far from every time
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Development Processes “Make the Customer Successful”
Agile Software Development
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Agile Software Development Brian Moseley.
Project Management and the Agile Manifesto
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger Joanne M. Atlee 4th Edition.
Agile Process: Overview
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Introduction to Agile Blue Ocean Workshops.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Projects, Assignments, and other Assessments
Chapter 5: New and Emerging Process Methodologies
Presentation transcript:

1 Discipline vs. Agility

2 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors

3 Background Agile? Discipline? Perplexity? Project management Getting things done Perplexity on: − Each have multiple definitions − Distinguishing from use and misuse − Overgeneralization based on most visible

4 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors

5 Where Did Discipline Come From? DoD guidance documents − MIL-STD-1521 − DoD-STD-2167 − MIL-STD-498 Large commercial companies − IBM − Hitachi − Siemens

6 What is Disciplined? Adjectives Predictive Plan-driven Documentation Systematic

7 Related Concepts Process improvement Process capability Organizational maturity Process group Risk management Verification Validation Improve Process Measure Process Control Process Define Process Perform Process

8 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors

9 Where Did Agile Come From? Outgrowth of rapid prototyping Programming more of a craft than a process Address a common problem: After a long development cycle the product doesn’t meet expectations

10 What is Agile? Agile Manifesto We value – Individuals and interactions over process and tools – Working software over comprehensive documentation – Customer collaboration over following a plan – That is, while there is value in the items on the right, we value the items on the left more.

11 What is Agile? Adjectives: Iterations Test-driven Customer collaboration Methods: eXtreme Programming (XP) Adaptive Software Development Feature Driven Development Scrum Every 24 hours

12 What is Agile? Embrace change Fast cycle/frequent delivery Simple design Refactoring Pair programming Retrospective Test-driven development

13 Sounds Great, Why Not Use It? Agile has trouble scaling − Size of project − Size of group Cost can go up with group size Plan-driven has trouble trimming − Heavy documentation − Late cycle delivery No silver bullet

14 What Are The Key Differences? Plan-Driven values process over people Agile values people over process Document, document, document – chants the disciplined

15 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors

16 What are the misconceptions?

17 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors

18 Application Characteristics Contrasts and Home Grounds Primary goals Rapid value and responsiveness to change Plan-driven goals are predictability, stability, and high assurance Size Agile works best on smaller projects Plan-driven is a necessity on large complex projects Environment Agile approaches are comfortable in high-change environments with some risks Plan-driven methods need stability

19 Management Characteristics Contrasts and Home Grounds Customer relations – Agile encourages a dedicated collocated customer – Plan-driven methods depend on contracts and specifications Planning and control – Agilists see planning as a means to an end – Plan-driven methods use plans to communicate and coordinate Project communication – Agile methods depend on tacit knowledge – Plan-driven approaches use explicit, documented knowledge

20 Technical Characteristics Contrasts and Home Grounds Requirements Agile uses informal, user-prioritized stories as requirements Plan-driven methods prefer specific, formalized requirements Development Agile advocates simple design Plan-driven methods advocate architecture to anticipate changes Testing Agile methods develop tests before code, and test incrementally Plan-driven methods test to specifications

21 Personnel Characteristics Contrasts and Home Grounds Customers Both methods need collaborative, authorized, committed, and knowledgeable representative Plan-driven does not require them full-time Developers Agile developers need more than technical skills Plan-driven methods need fewer highly talented people than agile Culture Agilists like many degrees of freedom Plan-driven people need clear process and roles

22 Topics What is discipline? What is agility? What are the misconceptions? Contrasts and home grounds Five critical factors

23 Five Critical Factors Factors to measure: Personnel Size Dynamism Criticality Culture

24 Five Critical Factors: Personnel Agile − Requires continuous presence of critical mass of scarce Cockburn Level 2 or 3 experts. Risky to use non-agile Level 1 people. Plan-Driven − Needs a critical mass of scarce Cockburn level 2 and level 3 experts during project definition, but can work with fewer later in the project – unless the environment is highly dynamic. Can usually accommodate some Level 1 people.

25 Cockburn Scale Levels of Software Method Understanding and Use LevelCharacteristics 3Able to revise in unprecedented situation 2Able to tailor a method to fit new situation 1AWith training can perform discretionary steps, can train to level 2 1BWith training can perform basic procedural steps May have technical skills but unable or unwilling to collaborate

26 Five Critical Factors: Size Agile − Well matched to small products and teams Plan-Driven − Methods evolved to handle large products and teams

27 Five Critical Factors: Dynamism Agile − Simple design and continuous refactoring are excellent for highly dynamic environments, but a source of potentially expensive rework for highly stable environments. Plan-Driven − Detailed plans and big design up front excellent for highly stable environments, but a source of expensive rework for highly dynamic environments.

28 Five Critical Factors: Criticality Agile − Untested on safety-critical products − Open to change in requirements Plan-Driven − Methods evolved to handle highly critical products − Not open to change in requirements

29 Five Critical Factors: Culture Agile − Thrives in a culture where people feel comfortable and empowered by having many degrees of freedom Plan-Driven − Thrives in a culture where people feel comfortable and empowered by having their roles defined by clear policies and procedures.

30 Walking the Line – When to Use What