Course Outline

Day 1 - Managing Software Projects in a Waterfall Context

1. Introduction to Waterfall

a. Historical Context
  1. Winston Royce
  2. Background in manufacturing processes
b. Waterfall stages
  1. Requirements gathering
  2. Design
  3. Implementation
  4. Verification
  5. Maintenance
c. Waterfall challenges
  1. Handling change
  2. Distance between business knowledge and implementation
  3. Storing risk to late in the lifecycle
  4. Prioritisation of scope
d. Summary of reactions to Waterfall model
  1. Embrace – Waterfall approaches, eg SSADM
  2. Cope – V-Model
  3. Adapt – Incremental
  4. Reject – Agile
  5. Enhance – Lean

2. V-Model coping strategies for Waterfall delivery

a. Early verification and validation
  1. Cost of finding late
  2. Reviews and inspections
  3. Static analysis
b. V-Model test stages
  1. Unit/Unit integration
  2. System
  3. System Integration
  4. Acceptance
c. V-Model benefits
  1. Increased end-user involvement in verification
  2. Early risk mitigation

3. Adapting Waterfall with Incremental approaches

a. Types of Incremental approaches
  1. Pre-planned 
  2. Parallel, RAD
  3. Evolutionary, RUP
b. Incremental delivery principles
  1. Product increments
  2. Proto-typing
  3. Timeboxing
c. Benefits of incremental delivery
  1. Increased user involvement in decision making
  2. Early return on investment
  3. Reacts to change 

4. Rejecting the Waterfall model in favour of Agile

a. Agile Essentials
  1. Agile Manifesto
  2. Agile Principles
b. Introduction to Scrum, the most popular Agile framework
  1. Iterative delivery
  2. Collaborative working
  3. Just in time documentation
  4. Adaptive planning
c. Benefits of Agile
  1. Increased user involvement throughout process
  2. Empowered development team
  3. Rapid return on investment
  4. Greater ability to react to change
  5. Reduce nugatory development

5. Enhancing Waterfall with Kanban delivery

a. Lean and Kanban 
  1. History of Lean delivery 
  2. History of Kanban
  3. Principle of reducing waste
b. Introduction to Kanban
  1. The Kanban board
  2. Managing work-in-progress
c. Benefits of Kanban
  1. Greater ability to react to change
  2. Rapid return on investment
  3. Reduce nugatory development

Day 2 - Agile Project Management Techniques

1. Empirical Process Control

a. Inspect
  1. Demonstration
  2. Retrospection
b. Adapt
  1. Adaptive planning
  2. Continuous improvement
c. Transparency
  1. Stakeholder involvement
  2. Contract negotiation
  3. Just in time documentation

2. Managing requirements

a. Backlogs
  1. Product
  2. Release
  3. Sprint
b. Backlog Items
  1. User Stories
  2. Defects
  3. Requirements specifications
c. Risk
  1. Adjusting Backlog for risk
  2. Risk burndown

3. Estimation and control

a. Timebox planning
  1. Release planning
  2. Iteration planning
  3. Daily communication
b. Prioritisation techniques
  1. MoSCow
  2. Value based
  3. Other techniques
c. Estimation techniques
  1. User story grooming
  2. Planning Poker

4. Delivery management

a. Iterative delivery
  1. Team velocity
  2. Rapid return on investment
b. Information radiators
  1. Scrum wall
  2. Burn-down chart

5. Team management

a. Associative leadership
  1. ScrumMaster as facilitator
  2. Role of the traditional project manager
b. End-user involvement
  1. The single decision maker - the Product Owner
  2. Communicating with stakeholders (Pigs and Chickens)
c. Empowered team
  1. Self-managing teams
  2. The role of the specialist within the team
  3. Managing split teams
 14 Hours

Testimonials (5)

Related Categories