Questions & explanations
1. Explain how you would value a simple option to defer a project using a decision tree.
First, list the possible outcomes: for example, market demand could be high or low. Estimate the project's net present value (NPV) in each outcome if you invest now. Then, consider the alternative: wait one year to see which outcome occurs. If you wait, you only invest when demand is high. The decision tree has a node now: invest now or wait. If you invest now, you get the expected NPV across both outcomes (perhaps negative). If you wait, you get the better outcome (high demand) minus some cost of delay. You compare the two strategies. The value of the option to defer is the difference between the 'wait' value and the 'invest now' value. This shows how flexibility adds value.
2. Compare the role of stakeholder communication in PMBOK versus PRINCE2.
In PMBOK, communication management is a separate knowledge area that works closely with stakeholder management. It involves planning, managing, and monitoring communications. PRINCE2, on the other hand, includes communication management as part of its 'progress' theme and uses a communication management strategy. PMBOK gives more freedom to decide how to communicate, while PRINCE2 has a specific document for it. Both standards stress that communication should be two-way and tailored to stakeholders. However, PMBOK treats it as a continuous process, whereas PRINCE2 links it to stage boundaries and reporting. The core goal is the same: keep stakeholders informed and engaged.
3. What is capability-based planning in program management?
Capability-based planning is a way to organize programs around the abilities an organization needs to achieve its goals, not around individual projects. A capability is a lasting ability to perform a function, like 'customer relationship management' or 'rapid product development'. Instead of listing projects first, you identify the capabilities your organization must build or improve. Then you create programs that develop those capabilities over time. For example, a company might decide it needs 'advanced data analytics' and start a multi-year program with training, tools, and processes. This approach ensures programs directly support strategic needs.
4. What is the IPMA approach to stakeholder management?
IPMA (International Project Management Association) focuses on competencies rather than fixed processes. It sees stakeholder management as a key competence for project managers. IPMA recommends understanding stakeholder needs through structured interviews and mapping their power and interest. It also stresses the importance of negotiation and conflict resolution skills. Unlike PMBOK or PRINCE2, IPMA does not prescribe a single method but encourages adapting to the situation. The approach is people-centered, emphasizing relationship building and continuous communication. IPMA’s four-level certification system tests these competencies in practice.
5. What is stakeholder engagement software?
Stakeholder engagement software is a digital tool that helps you manage all interactions with stakeholders. It usually has a database to store stakeholder details, a communication log, and a way to send updates. Many tools also include features for surveys, feedback collection, and reporting. This software makes it easy to track who you have contacted and what they said. Instead of using separate spreadsheets and emails, everything is in one place. Some popular types are project management platforms with stakeholder modules and dedicated customer relationship management (CRM) systems. The goal is to keep stakeholders informed and involved.
6. Explain how MCDA can be used to select a portfolio of projects, not just a single project.
For a portfolio, you need to pick several projects that together meet goals under a budget or resource limit. MCDA can score each project individually, but you also have to consider dependencies and balance. For example, you might want a mix of high-risk, high-reward and safe projects. You could first use MCDA to rank projects, then apply constraints like 'no more than 2 high-risk projects' and 'total budget under $1M'. Then you select the top-ranked projects that fit the rules. Some advanced MCDA methods include mathematical optimization to find the best set. This ensures the portfolio as a whole is valuable, not just each project alone.
7. How does PRINCE2 handle stakeholder management compared to PMBOK?
PRINCE2 (Projects IN Controlled Environments) treats stakeholder management as part of its 'organization' theme. It focuses on defining roles and responsibilities for stakeholders, especially the project board. Unlike PMBOK’s separate knowledge area, PRINCE2 integrates stakeholder involvement into every stage. PRINCE2 uses a business case to ensure stakeholders see value, and it has regular stage assessments to check stakeholder satisfaction. The method also emphasizes communication management, with a specific management product for it. Overall, PRINCE2 is more process-driven with defined roles, while PMBOK offers more general guidance.
8. Compare living documentation with traditional documentation.
Traditional documentation is written separately from the code, usually in a word processor or wiki. It often becomes outdated quickly because developers forget to update it. Living documentation is generated from the code and tests, so it stays accurate. Traditional docs require manual effort to create and maintain. Living docs are automatically produced and always match the software behavior. However, living docs may be less readable for non-technical stakeholders because they contain technical details. The best approach often combines both: living docs for technical specs and a small set of traditional docs for high-level overviews.
9. How does the APM (Association for Project Management) body of knowledge cover stakeholder management?
APM’s body of knowledge (APM BoK) includes stakeholder management in its 'people' and 'communications' sections. It defines stakeholders as anyone with an interest in the project and stresses early identification. APM recommends creating a stakeholder map to show influence and interest, similar to other standards. It also highlights the need to manage expectations and handle conflicts. APM focuses on soft skills like active listening and empathy. The standard is used mainly in the UK and is similar to PMBOK but with a stronger emphasis on behavioral competencies. It is practical and aligned with project management best practices.
10. Give an example of living documentation using an executable specification.
Suppose a team is building a login feature. They write an executable specification in Gherkin: 'Given a registered user, When they enter correct username and password, Then they see the dashboard'. This scenario is run as an automated test. The test results become part of living documentation: a report shows that the login works. If the login code changes, the test will either pass or fail. If it fails, the team knows the documentation no longer matches reality. They fix the code or update the scenario. The living documentation always shows the current behavior. It replaces a separate login document that would likely be outdated.
11. Why is it important to align stakeholder management practices across different standards?
Many projects use multiple standards, like PMBOK for planning and PRINCE2 for governance. If stakeholder management is not aligned, stakeholders may get mixed messages or feel neglected. Aligned practices ensure consistent identification, analysis, and engagement. It also helps team members trained in different standards work together smoothly. For global projects, a unified approach avoids confusion from varying terminology. Aligning practices reduces duplication of effort, like creating separate communication plans. Ultimately, it improves stakeholder satisfaction and project success by providing a clear, coordinated strategy.
12. What is a hybrid XP approach in project management?
Hybrid XP means using extreme programming (XP) engineering practices inside a more traditional project structure, like Waterfall phases. XP practices include pair programming (two people coding together), test-driven development (writing tests before code), and continuous integration (merging code often). In a hybrid, you might plan the whole project in phases (like Waterfall) but use pair programming during the coding phase. For example, a team first writes requirements in a plan, then codes using TDD and pair programming. This gives the quality of XP while keeping the clear stages of Waterfall for reporting to managers.