M4 Flashcards
Example of 1-4 week sprint
A very short iteration – 1 to 4 weeks
Sprint 1
* Review
* Test
* Build
* Design
* Launch
Sprint 2
* Review
* Test
* Build
* Design
* Launch
Sprint 3
* Review
* Test
* Build
* Design
* Launch
Characteristics of a sprint
- Consistent length and timeboxed
- Has a Sprint Goal
- Creates something of value and the Sprint ends with a shippable product
What meeting are held for each sprint?
- Planning
- Stand ups (Every day, twice on the last day)
- Sprint review (Demo)
- Retrospective
How to prepare for Sprint Planning
- The Product Backlog (PB) has to be up-to-date before the planning meeting by the Product Owner
- The PB includes a prioritized list of Product Backlog Items (PBI’s) in the form of User Stories
- Example of a User Story - “As a call center user, I want to be able to search a client using their email address, so that I can minimize the time I have them on hold ….”
Product Backlog
- Only one Product Backlog – that can be shared across the team
- One Product Owner responsible for the backlog
- The Product Owner has to understand each PBI (Product Backlog Item) in the backlog (story, feature, use case)
- Anyone can theoretically add stories but it is only the Product Owner who prioritizes the stories
- Only the development team adds estimates for the PBI’s, not the PO
*Keep all of the user stories or features at the business level, not “technical” – the what of the story, not the how. Focus on the business goals, the Scrum development team will figure out the “how”.
Examples of a do and don’t for a user story or feature:
Do use the following: “Speed up the search event form in the back office system” (the “what” they want)
Don’t use: “Add indexes to the events table in database” (the “how”)
Sprint Planning Meeting
- A sprint goal
- A list of team members (and their participation commitment – 100%, 50%?)
- A Product Backlog is input, a Sprint Backlog is output
- A Sprint Review (demo) date
- A time and place for the daily stand up meeting
- The Product Owner must attend this meeting
*
Each Product Backlog Item (PBI) has 3 variables. What are they.
- Scope - Selection of scope and
- Importance by the Product Owner
- Estimate of effort
Defining the Sprint Goal
- Written in business terms (plain language)
- Needs to answer the question “Why are we doing this sprint”.
- Anyone off the street would understand what the team is developing for the sprint
What are Ideal hours:?
Time spent exclusively on the task, with no interruptions
What are Actual Hours?
The real amount of time it took to finish that task or project.
When to procure based on the least cost?
**Least cost. **
Procurements of a standard or routine nature
Where well-established practices and standards exist
From which a specific and well-defined outcome is expected
Example Office supplies
When to procure based on the Qualifications only?
Qualifications only.
When value of the procurement is relatively small, time and cost of a full process would not make sense .
Short list and selects bidder with best credibility, qualifications, experience, expertise, areas of specialization, and references.
Example: Painter needed to paint 2 bedrooms
When to procure based on the Quality-based/highest technical proposal score?
**Quality-based/highest technical proposal score. **
The selected firm is asked to submit a proposal with both technical and cost details and is then invited to negotiate the contract if the technical proposal proves acceptable. Using this method, technical proposals are first evaluated based on the quality of the technical solution offered. The seller who submitted the highest-ranked technical proposal is selected if their financial proposal can be negotiated and accepted.
Example: Design wastewater treatment plant for City of London
When to procure based on the **Quality and cost-based. **?
**Quality and cost-based. **
When risk and/or uncertainty are greater for the project, quality should be a key element when compared to cost.
Example: Vaccine for new variation of pandemic virus
