Lesson 2: Start the Project Flashcards
Salience Model
The salience model is a method used to classify stakeholders and decide who matters more by assessing their power, legitimacy, and urgency. The model allows the project manager to decide the relative salience of a given stakeholder (PMBOK 7th edition, page 171).
Scrum Meeting
Scrum meeting is time-boxed at 15 minutes; it does not change depending on the length of a sprint or size of a team.
Backlog Refinement
During backlog refinement, the team helps the product owner create or review emergent product backlog items as well as progressively refine larger ones. The team also estimates the size of product backlog items and helps the product owner prioritize them. As a general rule, the development team should allocate up to 10% of its time in each sprint to assisting the product owner with refinement activities (Essential Scrum by Rubin, Kenneth S, page 106).
Interation/sprint backlog
Expected to burn down during duration; the work does not carry over. 1-4 weeks (typically 2 weeks) (most common)
Backlog refers to agile.
Product/ Project Backlog
Overall backlog - anything that has not been done. Prioritized and organized based on the value that each item brings to the product and project.
Backlog refers to agile.
Directions of Influence
Classifies stakeholders according to their type of influence on the project: upward, downward, outward, sideward.
Integration Management
Team members determine how plans and components should be integrated in order to deliver the final work. pg. 91
Scrum Activities
Inspect progress toward the spring= Sprint Execution
Presents the projects performance to the stakeholders= Sprint review
Discusses the improvements that can be applied in the upcoming sprint- Sprint Planning
Provers estimates of the required efforts to complete user stories- sprint planning
On-Demand( Kanban/ Lean-based)
Does not work well in projects with complex dependency relationships.
The main aspects of the Kanban method are: visualizing the workflow, limiting work in progress, managing flow, making process policies explicit, implementing feedback loops, and improving collaboratively. Close or osmotic communication is one of the crystal methodology’s characteristics (Agile Practice guide, pages 104, 107).
Rough Order of Magnitude
(-25 to+75%)