At a glance
Iterative Project Management
Overview
This course is designed to enable you to learn how to use the iterative and incremental life-cycle style of project management.
Iterative Project Management is a course that shows its participants how to manage projects using an approach that produces a product through incremental evolution and delivery of product components throughout a product development cycle. As well as being influenced by Steve McConnell's book "Rapid Development" and the CxOne method, it is also influenced by the Unified Development Process espoused by Booch, Jacobson, and Rumbaugh.
The approach emphasises:
1. Early recognition and reduction of risk
2. Early proof of business benefit and technical architecture
3. Management of change to requirements
4. Configuration management of delivered components
5. Process refinement from iteration to iteration
6. Incremental knowledge and skill refinement
7. Use of appropriate metrics
8. Well-planned and controlled activity
Intended For
This course is aimed mainly, but not necessarily exclusively, at experienced team leaders and project managers who have realised that the traditional waterfall method does not always work.
Prerequisites
Mandatory prerequisites:
- Must have a working knowledge of the complete software lifecycle (from initial feasibility through to post implementation maintenance).
- Must have a thorough understanding of project management principles (for example, as described in the Project Management Body of Knowledge).
Additional recommended prerequisites:
- One year or more experience as a software project manager or software project team leader.
- Have attended Software Education's "Managing Software Projects" course or equivalent.
Content
Course overview and objectives
Contrasting approaches to project management:
- Waterfall
- RAD-RIP-"Spiral"
- Controlled Iterative and Incremental
- Agile methods
The Big Picture - The product development cycle and the component iterations:
- The Inception Phase
- The Elaboration Phase
- The Construction Phase
- The Transition Phase
How to manage risk - the different types of risk to identify and manage and why this approach is better.
The role of Architecture and the Architect
Reusability
- Abstraction
- Patterns
- Frameworks
- The Principle of Interchangeability
Managing requirements changes
Configuration management
Why metrics and which metrics to use?
The team roles
Use of tools
What documentation, why and when?
Method Used
Lectures, discussions and group work
