Agile Overview 30,000 perspective Juha Salenius CSPO CSM PMI-ACP PMP SCGMIS Workshop January 23 rd, 2013
Agenda 30,000 Perspective The Players Initiating a Project Agile Estimating Agile Communications Agile Iteration (aka) Sprint Q&A 2
Agile Concepts 30,000 Level
Background Traditional Process Adoptive Process Fixed Scope Cost Time Value Driven Plan Driven Estimated Cost Time Features Source: DSDM (http://www.dsdm.org/content/2-fundamentals) [Dynamic Systems Development Method is an agile project delivery framework]
Framework comparison Source: http://greenlinesystems.com/wp-content/uploads/2012/01/agile.png 5
The Agile Umbrella Source: http://www.leadingagile.com/wp-content/uploads/2010/10/agile-umbrella-300x238.png 6
Agile Methodology Employed 2012 Source: http://www.versionone.com/pdf/7th-annual-state-of-agile-development-survey.pdf 7
What is Agile? It is more a philosophy The Agile Manifesto February, 2001 We value... Individuals and Interactions over Processes and Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to Change over Following a Plan That is, while there is value in the items on the right, we value the items on the left more. Note: Agile is not anarchy, it includes processes, tools, documentation, follows a plan and includes negotiating. Source: http://agilemanifesto.org 8
Agile Principles 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 9
Agile Principles 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity--the art of maximizing the amount of work not done--is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Source: http://agilemanifesto.org/principles.html 10
Why Agile? Stacey Diagrams Complexity considerations: multiple stakeholders, changing business & technology landscapes, unknown requirements & technology, system integrations, culture, the organization, customers, people. Source: http://cdn.brilligence.net/wp-content/uploads/2013/04/stacey-matrix-agile.png http://www.gp-training.net/training/communication_skills/consultation/equipoise/complexity/stacey.htm 11
Project Landscape Agile Hybrid Waterfall KANBAN-1W ITERATION-2W ITERATION-3W ITERATION 4W HYBRID < 5W LIGHT TRADITIONAL HEAVY TRADITIONAL He quoted two studies: a DuPont study quoted only 25% of a system's features were really needed. A Standish study found that 45% of features were never used and only 20% of features were used often or always. [traditional waterfall projects] From Jim Johnson, the chairman of the Standish Group (Chaos report). Source: http://martinfowler.com/articles/xp2002.html#! 12
Agile Process Map INPUT REVIEW MEETING (1 ST Half) Product Focus; Everyone Customers & End Users Stake Holders Team TEAM BACKLOG GROOMING DAILY SCRUM MTG SPRINT 1-4 Wks Team Planning and Accountability PRODUCT OWNER Team Selects and Commits How Much To Do No Changes In Duration Or Goal Potentially Shippable Product PRODUCT BACKLOG Rank Ordered (Groomed) Features Sprint Planning Meeting (Parts 1 & 2) ITERATION or SPRINT BACKLOG Tasks To Do RETROSPECTIVE MEETING (2 ND Half) Process Focus; Team, ScrumMaster & PO 13
Contact Information
Juha Salenius Training and coaching contact information email: build2use@yahoo.com phone: (803) 318-8978 15