Course Title: Risk Management and Planning for Iterative Projects
Course #: BN06
Everything the BA, backed up by the IT Project Manager, needs to know to work within a project managed with iterative development and use-case technology, with comparisons to other approaches to project management. As a BA working on an iterative IT project, you’ll learn what activities to perform and what artifacts to produce at each iteration of each phase of a project.
Duration: 2 days
Description:
Working in small groups, trainees step through a case study learning when and how to perform BA activities, create deliverables and assist the Project Manager at various phases of the iterative life cycle. The course uses a (generic) non-product-specific step-by-step program for iterative development with an emphasis on the Agile approach. Specific methodologies and frameworks are also discussed, including MSF, RUP, Scrum and Extreme Programming.
Why:
In an effort to shorten time-to-market and to uncover bugs early, IT organizations are increasingly using a style of project management called iterative development. The iterative strategy is to develop software in small cycles of analysis, design and coding – rather than doing all the up-front work before coding begins. To work effectively in this environment, Business Analysts and the Project Managers need to be familiar with the fundamentals of this approach and their roles in producing key deliverables, managing risk and estimating resources for an iterative project.
What makes this course stand out from the competition?
- Experience: Our course is written and delivered by professionals with extensive practical experience in iterative development from a business analysis perspective.
- Scenario-based training: This is not just another “theory” course in project management. Trainees learn how to perform the BA role and support the Project Manager on an iterative project by developing an integrated case study throughout the iterative life cycle and experiencing the roles in real time.
Audience:
- IT Business Analysts
- IT Project Managers
Prerequisites: None
Class Format:
The course content is presented through lectures and mentoring through workshops on an integrated case study.
Objectives:
Upon completion of this course, you will be able to:
- Perform the Business Analyst role on an iterative project.
- Understand the Project Manager role on an iterative project
- Be able to produce key deliverables for an iteratively managed project.
- Perform the BA role in Risk Management.
- Collaborate effectively with other members of the iterative team.
Course Content:
- Project Management State of the Art:
- System Development Life Cycles
- Waterfall Model
- Iterative, Incremental Development
- Why iterative development is key to project success
The role of the Project Manager in Iterative Development
- Key PM deliverables
- PM role in Risk Management
The role of the Business Analyst in Iterative Development
- Why well-defined requirements are key to project success
- Key BA Deliverables
- The BA's Role in Risk Management
- Requirements Based Software Estimation
- The Business Analyst in Collaboration with the team
Use Cases and Iterative Development
PM and BA activities and deliverables required at each phase of iterative development
Current iterative methodologies, including MSF, Agile, Scrum and Extreme Programming
Daily Schedule:
Day 1:
- Lesson 1: Introduction to IT Project Management
- Process Model
- Project Lifecycle
- Waterfall Model
- Iterative phases
- Spiral Model
- MSF
- RUP
- Agile
- BA Role in iterative development
- Lesson 2: Guided Tour of an Iterative Project
- Step-by-step walkthrough of the BA role throughout an end-to-end iterative IT project, using a sample case study.
- Lesson 3: Initiation phase - initial activities
- PM role
- BA role
- Solution Architect role
- Defining stakeholder interests
- Deciding upon the iteration strategy
- Wide and shallow
- Narrow and deep
Lesson 4: Initiation phase - analysis
- Business use-case analysis
- Role Map
- Setting up a process for requirements management
- Characteristic of well-managed and well-documented requirements
- Traceability matrix
- Defining requirements attributes
- The Requirements Management Plan
- CMM (Capability Maturity Model)
Day 2:
- Lesson 5: Initiation phase – Risk Management
- Planning a Risk-Management strategy
- Risk assessment
- Risk analysis
- Prioritizing risks
- Risk Mitigation
- Use Cases and Risk
- Factoring Risk into the determination of iteration length
- Establishing project scope
- Lesson 6: The Analysis Phases
- Non-functional requirements
- Enterprise and Solution Architecture
- Dynamic analysis activities
- Static analysis activities
- Implementing traceability
- Testing activities
- Risk Analysis
- Reviewing the results of an iteration
- Planning for the next iteration
- Lesson 7: Execution, Test and Close-out Phases
- Change management
- Use-case driven testing
- Deployment
- Final Documentation
- Planning for future releases
- Lesson 8: Overview of Software Development Lifecycle Methodologies
- PMBoK (Project Management Book of Knowledge)
- Knowledge Areas
- Process Groups
- Lifecycle
- Process Improvement
- CMM (Capability Maturity Model)
- ISO 9000
- SPICE
- ITIL
- Agile
- XP (Extreme Programming)
- Scrum
- Crystal
On-site requirements:
Room set-up:
Set up tables (e.g., round tables) so that trainees are sitting in groups of 3-5. Each group should have 1 flipchart. Each trainee requires 1 pad or paper + pen + 1 copy of the course material. The course material comes in one binder and contains:
- Detailed course notes (printed PowerPoint presentation)
- Workshop and Job Aids (Word document) with:
- Full workshop solutions
- Job Aids booklet containing:
- Templates
- Examples
- Glossary of technical terms
The trainees perform all the workshops manually. No PCs are required.
For the instructor:
- Whiteboard
- Overhead screen projector or large colour monitor, connected to instructor’s PC
- PC loaded with:
- Windows XP Professional
- PowerPoint
- PowerPoint presentation (.ppt file)
- Workshops and Job Aids file (1 Word doc)