SCRUM Framework
Definition of Done Checklist
1. Design Reviewed 2. Code Completed 3. End-User Documentation Updated 4. Tested 5. No known defects 6. Acceptance Tested 7. Live on Production Servers
What is SCRUM and when is it effective?
A framework for developing, delivering, and sustaining complex products Effective in iterative and incremental knowledge transfer Scrum is an Agile process framework
SCRUM
A lightweight process framework for agile development
Lightweight
A particular set of practices that must be followed in order for a process to be consistent. (Scrum - sprints)
Adaptation
Ability to make adjustments quickly to minimize further deviation
Acceptance Criteria
As a user I want to pay for items in the cart with credit so it can be shipped right away On the back of the story card, this can be created: Test with Visa, MasterCard and American Express (pass) Test with Diner's Club (fail) Test with good, bad and missing card ID numbers from the back of the card •Test with expired cards •Test with different purchase amounts (including one over the card's limit)
Sprint Planning Meeting
At the beginning of each sprint Negotiate which product backlog items will be converted to a working product during the sprint The Product Owner will declare which items are most important The Dev Team will select the amount of work they feel they can implement The Dev Team pulls work from the Product Backlog into the Sprint Backlog If the top of the PB hasn't been refined, it could be done during this meeting
Sprint Retrospective
At the end of every Sprint; after the sprint review The team Inspects their behavior and Takes action to Adopt the process for future sprints Periodically take a look at what is and is not working Typically 15-30 minutes Whole team participates Scrum Master, Product owner, Development team Possibly customers and others are there
User Story's Three C's
Conversations, Cards, Confirmation Shifts focus from writing to talking
Describe what the SCRUM team is and does
Deliver incremental products of 'Done' to ensure a useful version of the working product is always available - are self-organizing by choosing how to accomplish work - are cross-functional by having all competencies needed to accomplish the work
When was SCRUM created and by who?
Developed by Ken Schwaber and Jeff Sutherland in the early 1990's
What can the Product Backlog contain?
Features - something the user wants Bugs - issues Technical work - "upgrade to Windows10" Knowledge acquisition - "researching JavaScript libraries"
SCRUM Values
Focus, Openness, Respect, Commitment, Courage (FORCC)
Inspection
Frequently looking at the artifacts so the team can progress towards their goal
Managing the Sprint Backlog
Individuals sign up for work of their own choosing - work is not assigned Estimated work remaining is updated daily Any team member can add, delete or change it If work is unclear, define it's item with a larger amount of time and break it down later Update work remaining as more becomes known
Why is rugby compared to SCRUM?
It is a metaphor to reflect the degree of cooperation from each member needed to succeed
Backlog Refinement Meeting
Not a required event, but is a required activity Done during the sprint to prepare for the upcoming sprint planning meeting Most PBI's need to be refined (too large or vague) May start with the PO and stakeholders before involving the team PBI's can be written in User Story Form Agility requires splitting large Epics into user stories representing very small product features
Pros of Sprint Retrospective
Not the fearful meetings of the past It should be an environment of psychological safety No blaming or hostility Scrum Master uses a variety of techniques to facilitate Helps develop actions to take the team to the next level
Product Backlog
Prioritized list of desired functionality Visible to all stakeholders Any stakeholder (including the Team) can add items Constantly re-prioritized by the Product Owner Constantly refined by the Scrum Team Items at top should be smaller than items at bottom It is dynamic and never complete (it evolves)
Minimum Viable Product (MVP)
Producing a small product that can be offered to the customers. Allows observation of customer with product instead of asking what they would do.
SCRUM Artifacts
Product Backlog Sprint Backlog Increment
SCRUM Team
Product Owner Scrum Master Development Team
Sprint Backlog
Selected product backlog items are negotiated between the team and the Product Owner during the Sprint Planning Meeting to complete in the next Sprint... No changes are made during the Sprint that would endanger the Sprint Goal Initial tasks are identified by the team during Sprint Planning Meeting Team will find more tasks needed to meet the Sprint Goal during Sprint execution Visible to the team Referenced during the Daily Scrum Meeting
User Story
Short, simple descriptions of a feature Told from the perspective of the person who desires the new capability As a < type of user >, I want < some goal > so that < some reason > Can be written on index cards or sticky notes or arranged on walls or tables They strongly shift the focus from writing about features to discussing them In fact, these discussions are more important than whatever text is written
Describe SCRUM teams
Small, highly flexible and adaptive
SCRUM Events
Sprint Planning Spring Review Sprint Retrospective Daily Scrum Sprint
Daily Scrum
Standup Meeting (same time & place) for 15-minutes for the Dev team Not for problem solving Daily inspect (their progress) and Adapt to help the team Scrum Master facilitates The Team answers questions Intended to disrupt old habits of working separately
Burndown Chart
Summation of total team work remaining within one Sprint Updated daily Intended to facilitate team self-organization Seemed like a good idea in the early days of Scrum, but in practice has often been misused as a management report, inviting intervention. The Scrum Master should discontinue use of this chart if it becomes an impediment to team self-organization.
Sprint Planning
Team selects items from the product backlog they can commit to completing Sprint backlog is created Team determines how tasks are identified and each is estimated
Product Backlog Items
The 'what' more than the 'how' of a feature Has a product definition of Done May have acceptance criteria Effort is estimated by the Dev Team usually in points Usually written in a User Story
Differences between Sprint Review and Sprint Retro
The Sprint Review is about demoing the work that was just completed but the Sprint Retro is about identifying areas of improvement to make the next Sprint better
Process Framework
The overhead of the process is kept as small as possible, to maximize the amount of productive time available for getting work done.
Increment
The sum of all PBI's completed during a Sprint and its value from previous Sprints
3 Pillars Theory
Transparency, Inspection, Adaptation
Transparency
Visibility to those responsible for the outcome
Product Owner
one person responsible for... ordering items in product backlog ensuring the pb is visible, transparent, and clear shows what the team will work on next
Scrum Master
one person who... -supports and promotes scrum -ensures that goals and scope are understood by everyone on the Scrum team -helps the Scrum Team understand the Product Backlog -coaches the development team in self-organizing and cross-functionality -coaches the organization in adapting to Scrum -removes impediments to the development team's progress
Development Team
three to nine people delivering increments of done at the end of each sprint... organize and manage themselves and their work to make the pb functional
Sprint Review
time-boxed event of 4 hours, or less, to conclude the development work of a Sprint. It serves for the Scrum Team and the stakeholders to inspect the Increment of product resulting from the Sprint, assess the impact of the work performed on overall progress and update the Product backlog in order to maximize the value of the next period. -Whole team participates -Incomplete items are returned to the Product Backlog
