|
 |
 |
| |
 |
Project Planning and Risk Management for Development Teams |
| |
|
 |
3 days
|
 |
|
 |
Consider this scenario: Your project missed its scheduled release date, and your customers did not find that it met their needs when it finally was released. How can you plan a project that does a better job of meeting customer requirements and does it while making life better for your development team? It is not impossible, even though it may still be challenging.
This course builds on the two-day course, Project Management: A Team Approach for Accountability and Results , by adding information on customer requirements, engineering specifications, requirements risks, a task-responsibility matrix, and other techniques that assist development teams with the specific needs that their projects present.
Using a mix of presentation, group interaction, experiential exercises, and applying all the steps to your own projects, this 3-day course gives you and your team the common framework, skills, methodology, and language to generate the accountability and results you know are possible. It gives you access to real data – not just opinions or “gut feelings” – that you can use in your interactions with project sponsors and customers to negotiate and set expectations for achievable results.
Objectives
Establish a common language and set of processes that can be applied to all your projects.
learn how to more successfully manage your projects.
Learn how to define customer requirements and determine how to convert them into engineering specifications.
Understand Project Processes – the methods and tools that make a difference in achieving project objectives.
Apply the principles of project management to a real project – one you bring into the course.
Learn how to use the course workbook and other materials as a reference for your projects.
|
 |
Day 1 – Define and Organize the Project
- Introduction - Project Team Simulation Exercise
- Project Initiation and Team Definition
- Project Sponsorship
- Operating Across Multiple Organizations
- Project Team Planning Meeting
- Project Objective, Requirements Definition, Engineering Specifications, and Priority Matrix
- Project Infrastructure Checklist
- Validation Meeting with Sponsor
Day 2 – Plan the Project
- Work Breakdown Structure (WBS)
- Dependency Diagram and Critical Path Method (CPM)
- Optimization Plans
- Risk Analysis and Management Plans
- Validation Meeting with Sponsor
- Set the Project Baseline
- Begin Change Management Process
Day 3 – Manage Progress to Plan
- Collect Status Information
- Identify and Analyze Variances
- Identify a Re-planning Event / Diagnostic Metrics
- Reports on Progress to Plan / Communicate regularly
- Close Out the Project
- Project Retrospective and Team Meeting
- Force-field Analysis – a tool to improve organizational learning
|
|
|
|
