Agile Software Development - Scrum

Sprint Burndown Chart

A graphical representation of work left to do versus time. Purpose: Monitoring the project scope creep Keeping the team running on schedule Comparing the planned work against the team progression

estimate relative size - story point

A point value is assigned to each item Size = Effort + Complexity + Uncertainty. Estimates are done together and owned by the Development Team Scrum Master will facilitate . Product Owner will clarify and answer any questions Can re-estimate the item if the Dev Team get new information.

Scrum Role Development Team

A team of 5 to 9 professionals who is responsible for the working product at the end of each Sprint Flat structure: no titles other than developer, no sub-team. Owns Sprint backlog and decides how much is realistic for each Sprint Produces thoroughly tested, defect-free "Done" Product Increment in each Sprint.

Scrum Events sprint

A time-box event of 2 to 4 weeks when a Scrum Team works to complete a set amount of work in which a "Done" product increment is created time-box is never extended. Sprint ends when time box expires each sprint has a sprint goal of what is to be built which does not change during sprint At every sprint, the Scrum Team will inspect and adapt the Product and the Process.

how will the chosen work get done

Development Team decides how it will build this functionality into a "Done" Product Increment during the Sprint Development Team does planning and design to make sure that they will achieve the Sprint Goal May invite other people to provide technical or domain advice. Scrum Master helps the team in case any arrangements need to be done for achieving the Sprint Goal.

estimate technique - planning poker

Everyone reads the details of the Product Backlog item Each member will mentally formulate an estimate. then holds up a card with the value that reflects their estimate. The high and low estimators give a brief explanation first, then the in-between estimators to share their reasons. After further discussion, each estimator reselects an estimate card, and everyone will shows their cards at the same time. The process is repeated up to 3 times Pick a single number to represent the overall range of estimates on the item.

Scrum Roles Product Owner

Product Owner 1.Represents interests of customers/stakeholders. 2. Responsible for maximizing the value of the Product 3. Owns Product Backlog ,Creation, Management ,Prioritization Development Team

what work to get done in sprint

Product Owner presents the ordered PBI to Development team. Scrum Master facilitates, gives advice, asks question and helps identify risks The PBIs are broken down to tasks and tasks are estimated jointly in hours Only the Development Team can assess how much can be accomplished in the Sprint.

Scrum Roles Scrum Master

Scrum Master A servant-leader - focus is on the needs of the team members and the customer with the goal of achieving results in line with the organization's values, principles and business objectives Teaches and coaches the organization and team in adopting and using Scrum process Facilitates Scrum events. Helps team to remove and prevent impediments

definition of done

Specifies what it means for an item to be considered "Done team needs to agree on the definition before the first Sprint.

3 ways to estimate velocity

Use a Proxy Project use a similar recent project to estimate the size of items in PB and the velocity Best Case/Worst Case Simulate the no of sprints required based on best and worst case scenario to get estimated velocity Simulate 3 Sprints (capacity-based sprint planning) Simulate 2-3 sprints to understand the realistic capacity of the team to get estimated velocity

Scrum Team

a self-organizing and cross-functional team where Everyone is responsible for hitting the Sprint Goal and a definition of "Done" that is clear and understood by everyone.

velocity

average size of PB items, in number of points, that the team can deliver during a Sprint. Measures the amount of work done during a Sprint and .Evaluated only as an average Tasks are estimated in real units using hours or quarter-days Points cannot be converted to hours.

Scrum

best-known framework for Agile Development. used to manage complex product development

Scrum Artifacts product increment

end of each Sprint, Done" items will be integrated and tested with the increments of all previous Sprints. -> Potentially Shippable Product The Product Increment is in a potentially releasable state Product Owner could release it they wanted to do with the collection of completed features

Scrum theory empirical control

inspection and subsequent adaptation to optimise predictability and control risk Transparency is required for inspection and adaption

Scrum Artifacts product backlog

ordered list of everything that is known to be needed in or for the Product to achieved maximum value. single source of requirements for any changes to be made to the product. Product Owner is responsible for it User Stories are a way of expressing Features on the Product Backlog.

Scrum Artifacts sprint backlog

set of (PBIs) selected for the Sprint, which is broken down into tasks each 1-16 hours is > 16 hrs it will be broken down Team members sign up for task. They are not assigned. Estimated remaining work is updated daily sprint backlog is unchanged during the period of the Sprint Items not "Done" by end of the Sprint -will be added back to the PB and done during in next Sprint

Scrum Events daily scrum

stand-up meeting between the Scrum Team. It's a 15-minute time-box daily event generally held at the same place and the same time 3 questions - "What did I do yesterday?", "What will I do today?" & "Are there any issues or Impediments?"

Scrum Events scrum review

time-box event of 1 hr x num. of weeks of a Sprint held at the end of each Sprint. active discussion of : What is the current state of the Product? What should be added to the Product or improved in future Sprints to deliver maximum value?

Scrum Events sprint planning

time-box event of 2 hrs x num. of weeks of a Sprint between the Scrum Team. 2 basic questions: What work can get done in this sprint and how will the chosen work get done?

Scrum Events Scrum retrospective

time-box event of 45 mins x num. of weeks of a Sprint between the Scrum Team at the end of the sprint after Sprint Review Active discussion of: Inspect how the sprint went with regard to process, tool, and people. Identify items that went well and potential improvements. Create an action plan to implement improvements in the Scrum Team