Stages in a Software Development Cycle?

Transcription

1 Agile practices

2 Stages in a Software Development Cycle?

3 Traditional Process Inception Functional specification Requirement? Design Specification Technology? Unknowns? Coding Testing Fix / Integrate 50% Time

4 Agile Values Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Agile Alliance - Feb agilemanifesto.org

5 Agile gives... Early and continuous delivery of valuable software - Highest priority Welcome changing requirements, even late in development Frequent conversation among business people and developers Working software is the primary measure of progress.

6 A Different Approach Inception Functional specification Project Estimates: End-User Feedback: Developer Productivity Delivery - Time-to-market - Business decides when to go live - Reduces risk of failure Design Specification Coding Testing Fix / Integrate Inception Release 1 Release 2 Release 3

7 Incremental? Credits: Jeff Patton

8 Iterative Credits: Jeff Patton

9 How Agile fits into software delivery Inception Business Case Baseline Requirements/ Stories Baseline Budget Develop Working Software Full Regression Test Suite Business Realisation Support Support Documentation Trained Support Staff

10 Release Inception High level requirements release 1 release 2 release 3

11 Decomposing a release release x Prioritized Release Level Stories Business Value Delivered Iterations Stories Completed

12 Anatomy of an Iteration Development Unit & Integration Testing Acceptance Testing Iteration Planning Daily Standup Meeting Development Retrospective Deploy to Production-Like Environment Iteration Planning Meeting Create Narratives Iteration Kick-off Meeting Unit & Integration Testing Acceptance Testing Iteration Planning Development Unit & Integration Testing Acceptance Testing Last Iteration Current Iteration Next Iteration

13 Comparison of the processes Project Plan/Estimation Requirements Gathering Use Cases / Functional Specs Design Specifications Code Test Inception Fix / Integrate $ $ $ $ $

14 Lower cost of change through higher quality software Traditional cost profile Time spent: lfinding defects lfixing Defects lregression Testing ldeploying Agile system cost profile More defects found & corrected causes lower cost of defect correction

15 Agile For Different Roles Analyst From business process to user stories Prioritization and planning Define acceptance criteria Playing proxy customer role Acceptance / SME testing Agile Developers/Architects Test Driven Development Incremental design and Architecture Refactoring Continuous Integration Craftsmanship Discipline Testers Early (and incremental) testing Collaboration with development Collaboration with analysts Automate, automate, automate! Managers Facilitating Getting the team what they need Removing roadblocks Looking Inwards and Outwards Self organized teams

16 Story-Based Requirements Story Card Format As a, I want to be able to so that. Acceptance Criteria I will know this is done when. Key Points to Writing Stories Keep stories short Seek a level of granularity that can be completed in a few days Keep stories mutually independent Do not include implementation details Independent Negotiable Valuable Estimable Small Testable

17 Lifecycle of a story In analysis lprioritised by Product Managers. lta and BAs investigate and document requirements lqas identify scenarios and acceptance criteria Analysed lrequirements and acceptance criteria are documented lstory is available to be planned for the next iteration Ready for Development literation planning meeting discusses and estimates the story and certifies it as available to be worked on by developers Story huddle ldevelopers, QA, BA, TA and Tech Lead review the story and discuss the desired implementation approach

18 The story lifecycle continues In Development ldevelopers implement lba and Product Manager review progress during implementation lqas prepare test scripts Ready for QA lgreen build ltech Lead/Architects review the code In QA lqa executes manual test scripts Ready for Signoff lqa confirms that required automated tests have been implemented Customer Sign off lproduct Managers reviews the functionality

19 Release Planning

20 Iteration Planning Meeting

21 Team Practices: Stand Up Meetings

22 Visibility- Digitized Card Wall

23 Visibility- Physical Card Wall

24 Track progress with Velocity

25 Progress Tracking

26 Agile Practices Automated Build/Deploy Pair Programming IKO Retrospectives Short Releases Automated Testing Story Wall Refactoring Daily Stand-ups Collective Ownership Coding Standards Continuous Integration Velocity Metrics User Stories Simple Design Test Driven Development INDIVIDUAL Iterations Sustainable Pace Co-location On-site Customer TEAM ORGANIZATIONAL