SCRUM (EVENTS :timer_clock:
Time-boxed every scrum event has a…
- Time-boxed every scrum event has a predefined maximum duration.
- These events enable transparency on the project progress to all who are involved in the project.
- “Done”, useable, and potentially releasable product Increment is created.
- Maximum one month time-boxed
- The work to be performed in the Sprint discussing "what" and "how".
- Created by the entire Scrum Team.
- Maximum 8 hour in one month time-boxed sprint
- Optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work.
- Plans of the next 24 hours
- 15-minute time-boxed
- For the Development Team
- Same time, same place
- Inspect people, relationships, process and tools
- Items that went well and potential improvements
- Create an action plan for improvements
- Inspect the İncrement and adapt the Product Backlog if needed
- Revised Product Backlog that defines the probable Product Backlog items for the next Sprint.
- Scrum Team and stakeholders collaborate
- The aim is to get feedback and increase cooperation.
- Maximum 4 hour in one month sprint
The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.
Scrum Team members respect each other to be capable, independent people
EMPRICAL PROCESS THEORY :bulb:
- Make decisions based on what is known
- Knowledge comes from experience
- Ralph Stacey: Complexity Chart
- Significant aspects of the process must be visible to those responsible for the outcome.
- Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen. (DoD)
If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.
Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.
Scrum’s artifacts represent work or value to provide transparency and opportunities for inspection and adaptation.
- Ordered list of everything
- Single source of requirements
- The Product Owner is responsible for it, including its content, availability, and ordering.
- It never completes
- It exists while the product exists
- It changes to identify product needs
- Set of Product Backlog items selected for the Sprint
- A plan for delivering the product Increment
- Realizing the Sprint Goal
- Highly visible, real-time picture of the work that
the Development Team plans to accomplish during the Sprint.
- Sum of all the Product Backlog items completed during a Sprint and the
value of the increments of all previous Sprints.
- New Increment must be in useable condition and meet the Scrum Team’s definition of “Done.”
Agile planning culture
- Agile planning onion
- Continuous planning
- Cone of uncertainty
- Why relative estimation?
- Örn: London Eye, Singapur opera binası,
- Örn2: Köpek türleri
- Poker planning, fibonacci, t-shirt sizing
- Velocity kavramı (PO release planning için ve takıma bir gösterge, KPI değildir) Done olan işlerin toplam size'ıdır.
Size estimation ve velocity üstünden
a. scope targeted release planning
b. date targeted release planning
product backlog burndown chart(görsel) (kalan feature y ekseni, x ekseni sprintler)
SCRUM TEAM :silhouettes:
- Self-organizing and cross-functional.
- Designed to optimize flexibility, creativity, and productivity
- Deliver products iteratively and incrementally, maximizing opportunities for feedback.
Responsible for maximizing the value of the product resulting from work of the Development Team
- Creating and maintaining product backlog
- Ready backlog item for the planning
- Answer and "what" person
- Collabration with stakeholders and representer to the team
- Making decision on releasing.
- Available (min %20-30 of his/her time)
- Only one person!
- Scrum Master cannot be a Product Owner
The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” (DoD) product at the end of each Sprint.
- Self organised (Game)
- Cross-functional (From I-Shaped to T-Shaped)
- 3 to 9 people (communication lines)
- Done increment
- Team stages (Bruce Tuckman's)
- Focused (multitasking game)
- Collective ownership/commitment
- Product transparency
- Almost done is not done
- Technical debt
- The Development Team is accountable for creating releasable Increments.
- The Product Owner is accountable for maximizing the value of the work.
- The Scrum Master is accountable for the understanding and application of Scrum and being sure that the team is productive.
Scrum is a framework for developing, delivering and sustaining complex products