3. Overview The Effect of Delays Startup Initiation Concept Design Func Design Build / Test Tech Design Deploy Startup Initiation Concept Design Func Design Build / Test Tech Design Deploy Startup Initiation Concept Design Func Design Tech Design Build / Test Deploy Typical Project Plan: Option A: Cut Build / Test / Deploy Time and Decrease Quality Option B: Extend Project End Date and Increase Cost OR Typical Project Execution:
4. Startup Initiation Concept Design Func Design Tech Design Build / Test Deploy 12 Month Project (originally a 9 month project) Month 10: Value Is Visible (Client begins testing) Month 12: Value Is Achieved Months 1-9: No Visible Value Overview Perception of Slow Delivery
5. Startup Initiation Concept Design Functional Design Tech Design Build / Test Deploy 12 Month Project (originally a 9 month project) Theory: All requirements should be defined More requirements discovered. Conceptual Design changes More requirements discovered. Functional Design changes More requirements / problems discovered during build. Functional Design / Technical Design changes Overview Lack of Flexibility
7.
8.
9.
10.
11.
12. SDLC / Sprint Alignment Sprint 0 Complete all Startup and Initiation Artifacts Sprint 1 Approved Product Backlog 1st set of Functional Design Specs for Sprint 2 Dev. Complete All Other Artifacts Sprint 2 to Sprint N - 1 Product Backlog Review Sprint Backlog Settlement Develop Sprint Deliverables Complete Artifacts for Developed Functions Sprint demonstration & sprint retrospective Sprint N UAT Deploy Solution Complete All Artifacts. Startup Initiation Requirements Functional Design Technical Design Build & Test Deploy
13.
14.
15.
16.
17. Deliverables by Sprint Sprint 2 Sprint 3 Sprint 4 Sprint N-1 Code Test Functional Design & Use Cases Sprint 1 Project Initiation Doc Sprint 0 Sprint N Design Deliverables Agreement Test Strategy Training Strategy Project Mgmt Control Doc Traceability Matrix Performance Test UAT “ Go Live” Project Signoff Sponsor/User Survey Team Evaluations Code Test Functional Design & Use Cases Design Code Test Functional Design & Use Cases Design Update Relevant Documents Code Test Functional Design & Use Cases Design Update Relevant Documents Update Relevant Documents Update Relevant Documents Sprint Review & Retrospective Sprint Review & Retrospective Sprint Review & Retrospective Sprint Review & Retrospective Release Plan Approved Product Backlog Sprint 2 Detail Plan Update Product Backlog Sprint 3 Detail Plan Update Product Backlog Sprint 4 Detail Plan Update Product Backlog Sprint N - 1 Detail Plan Deployment Plan 0 1 2 4 5 Iterate Sprint N Detail Plan Conceptual Design
18.
19. Agile Adoption Risks Adoption Risk Comment Viewed as a replacement for a company’s SDLC Employ Agile practices within the SDLC. SDLC remains in place. The timing of some of the deliverables changes. Lacks control When combined with SDLC artifacts, provides additional level of control by reviewing deliverables after each sprint. Each sprint review acts as its own gate review. Business commitment The business must find the time to engage in the process and take ownership prioritizing the product backlog and making trade-offs. Ship jumpers (revert back to their old ways) It’s hard to break established habits, so it will be important to continually re-enforce the Agile process.
20.
21.
22.
23.
Notas del editor
Consider adding another animation for updating the product backlog per the sprint review. Product Backlog Owned by the business Business makes decision on what is important