Chapter 17: Starting up a project Flashcards
Starting Up a Project
Ensures prerequisites for initiation are in place. Determines project viability and allocates resources.
Starting Up a Project Process
Lighter than initiating a project, aims to decide if the project is worthwhile before initiation.
Initiating a Project
Establishes solid foundations, clarifies what the project needs to achieve and why, with defined responsibilities.
Initiating a Project Process
Lays down foundations to ensure clear commitment and understanding before significant spend.
Initiating vs. Starting Up
Starting Up ensures readiness; Initiating finalizes detailed plans and project controls.
Agile Approaches Pre-Work
Agile often skips upfront formal planning, but agile methods like Sprint Zero or project chartering address this need.
Project Chartering in Agile
Used for basic understanding of the project, typically involves simple documentation (bullet points, visualization).
Sprint Zero
Agile term for early phase of planning and discovery, though not always used in Scrum.
PRINCE2 Agile’s Approach to Start-Up
PRINCE2 provides structure for upfront work ensuring project viability, including business case justification.
Upfront Work in Agile
Agile sees upfront work as unnecessary but PRINCE2 ensures it is justified and essential for project viability.
Disruptive Projects
Projects with high uncertainty, often involving new technologies or innovations (e.g., 3D printing).
Agile Tools for Uncertainty
Tools like Lean Startup and prototypes are used for managing high uncertainty in disruptive projects.
Assessing Agile Suitability
PRINCE2 assesses if agile methods align with project needs, ensuring agile is appropriate to the project’s context.
Agile and PRINCE2 Alignment
Agile methods (e.g., Scrum, DSDM) may need adaptation for a more structured PRINCE2 framework.
Agile Roles in PRINCE2
PRINCE2 needs to map agile roles (e.g., Scrum Master, Product Owner) to PRINCE2 roles for clarity.
Assessing Complexity with Cynefin
Use the Cynefin framework to assess project complexity, guiding agile or PRINCE2 approaches based on environment.
Cynefin Domains
Five domains: Obvious, Complicated, Complex, Chaotic, Disorder, determining how to handle project uncertainty.
Complexity in Projects
Cynefin helps to categorize product or project complexity, aiding decision-making on method selection.
Cynefin and PRINCE2 Agile
PRINCE2 Agile adapts based on the complexity of the project, using appropriate levels of planning or flexibility.
Examples of Complexity
Highly innovative projects (chaotic) may use Lean Startup methods; stable projects (complicated) follow PRINCE2 processes.
Changing Complexity in Projects
Projects may evolve through different complexity domains, requiring adjustments in approach (e.g., more agile techniques).
PRINCE2 Agile and Cynefin Evolution
Agile techniques evolve as projects change, with PRINCE2 adapting to the emerging needs through the Cynefin framework.
PRINCE2 and Uncertainty
PRINCE2 should be adapted based on project complexity (e.g., timeboxes, customer demos).
Agile Techniques for Uncertainty
In uncertain or volatile environments, agile techniques like prototyping or spikes are effective.
