Steven Borg | Co-founder & Strategist, Northwest Cadence

1. 04 | Define a Software Iteration Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM

2. Module Overview • Plan a release • Define project-tracking process • Scope a project

3. Plan a release

4. What the Study Guide says… • Plan a release. • identifying a flexibility matrix • identifying releases based on priority items in flexibility matrix and release criteria • resource planning (Scrum team is responsible for allocating team members) • identifying techniques to optimize a team that is geographically distributed • selecting a project methodology • risk management

5. What (the ^&*%#) is a flexibility matrix? • Based on the Iron Triangle – Scope, Resources, Schedule

6. “identifying releases based on priority items in flexibility matrix and release criteria” • No. • Think agile. Think lean. • Think delivering business value in small increments, quickly, with high quality. • Think backlogs, velocity, and forecasting sprints • Then, if all else fails, think of traditional work breakdowns in Project, with predecessors, external dependencies and critical paths.

7. Sprint Capacity Planning

8. Geographically distributed teams • Use electronic tools to share documents and data • SharePoint, TFS, etc • Pay close attention to cultural issues • Use video when possible • Do not post key documents or data only on the wall of the ‘home office’

9. Define project-tracking process

10. What the Study Guide says… • Define a project-tracking process. • identifying a project tracking tool and an associated process (triage process, bug management) • defining how to manage effort • determining team forecast management • defining a prioritization scheme • determining how to validate project health

11. Identifying an appropriate tool for project management • Primary MS tools for tracking software development projects are TFS and Project • TFS is very strong at handling most software development efforts, however it is weak at predecessor/successor relationships, handling efforts outside the development team, and identifying key measures such as the critical path. • MS Project is strong at many of the things TFS is weak at, however it is weak in gathering data through the normal day to day activities of the team, as well as most other software development project tracking needs.

12. Forecasting delivery*

13. Reports – Use them • Remaining Work • Requirements Overview • Requirements Progress • Status on All Iterations • Test Case Readiness • Test Plan Progress • Unplanned Work • Bug Status • Bug Trends • Build Quality Indicators • Build Success Over Time • Build Summary • Burndown and Burn Rate • Reactivations

14. Scope a project

15. What the Study Guide says… • Scope a project. • scoping the effort for a release • defining an architecture design process • defining scope boundaries (is/is not list) • determining the definition of “done” • defining a process when effort estimates are significantly inaccurate

16. Determining effort and release plan

17. Architectural design – Layer Diagrams

18. Architectural design – DGML

19. Architectural design – UML Diagrams

20. Architectural Diagrams • Good for sharing knowledge of the design • Good for collaboration • Layer diagrams can enforce architectural standards by limiting what is allowed/disallowed inside of a layer (done primarily by namespace) • Architecture requirements in a layer diagram can be validated during a build. • DGML diagrams can be extended to include more than just architectural elements.

21. Definition of Done • In Scrum, the team agrees on what it means for a task, user story, bug or other item to be ‘done’ • The Definition of Done is generally beyond the acceptance criteria specified in a user story or product backlog item.

22.  EXAM BEST BETS • Don’t overthink this section. • Many of the ideas here are covered directly by the Scrum and process overviews done earlier today.