Agile scrum foundation tutorial.pptx
- 1. Agile Scrum Foundation Tutorial By Mohamed Fouad El Nawawy, M.Sc.
- 2. Agile Principles • Self Organizing teams: determine how best to accomplish their work, rather than being directed by others outside the team • Cross Functional teams: There is no single team member owner of a task • Adaptive Planning: Respects customer satisfaction over change • Continuous Improvement: Each iteration ends with an increment which is an available release (with minimal bugs) • Transparency: Sharing product features among the team • Streamlining: Less documentation, fewer meetings, reduced e- mail, less coding • Test Driven development: Test your success before you claim progress
- 3. Scrum Team • Product Owner: Optimizes value of work-Orders product backlog in sprint planning meeting based on business and cost saving parameters • Scrum Master: Facilitates team decisions and removes impediments, Makes sure Daily Scrum meeting is 15 minutes, Reports to Higher Management when requested, Convinces Customer of Agile approach through implementing it • Development team: 3 to 9 members, Pulls sprint backlog from product backlog items which is owned by the team and nobody tells the development team in what order or how to do the task level work in the sprint backlog. • Development Team member can be changed as needed taking into account productivity
- 4. Development Team • Cross Functional: There are no specific titles or roles for individual team members • Self Organizing: They pull work for themselves, arrange their own team, manage the way they do their work together which results in accountability, creativity.
- 5. Meetings • Sprint Review (max. 4 hours): (For product increment evaluation). Includes Scrum Team, Stakeholders, Sponsors, Customers • Sprint Retrospective (max. 3 hours): (For Process Evaluation) Includes Scrum Team only • Daily Scrum: 15 minutes in the same place to discuss what have been done and what to do next
- 6. Sprint • Typically 1 to 4 weeks taking into consideration maintaining business and technology values • Development team works on backlog items as much as told by Product Owner and conforming with done • Done means that each feature in the iteration is fully developed, tested, styled, and accepted by the product owner however it doesn’t mean that a releasable product has been reached • TimeBox: In which the team finishes the sprint before maximum time. • Each sprint starts directly after the end of previous sprint
- 7. DEEP (For Product Backlog) • Detailed appropriately (If to be worked on soon should be detailed) • Emergent (To adapt to changes while product is developed) • Estimated (in either story points or ideal days) • Priotirized • Where story points combine complexity & physical size into one relative size measure and ideal days are days for which only work is being performed with no interruption and all resources available
- 8. Product Backlog •Product Owner orders product backlog according to business value, risk, cost to develop, dependencies, stories which increase the team knowledge about the project •Product Owner continues with backlog grooming or refinement keeping the backlog relevant, detailed, and estimated
- 9. Sprint Backlog •During the sprint planning meeting, the team selects a number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story. •The team decides the number of product backlog items it selects and in what order and how to do tasks in sprint backlog
- 10. INVEST (For Good User Stories) • User story describes in a sentence what needs to be done as part of a job function. • Independent (For Prioritization) • Negotiable (Collaborate in order to understand details of a feature in time) • Valuable (To customers or technical stories & therefore worth investing from PO) • Estimatable (Size hence cost for PO to determine priority) • Sized appropriately or small (Epics to themes and themes to stories) • Testable ( Conditions of satisfaction e.g. file size valid)
- 11. Velocity • Velocity=size estimates (e.g. story points) of every item completed during a sprint • Total duration/velocity=no. of required sprints for a release
- 12. Miscellaneous • Burndown Chart: A burn down chart is a graphical representation of work left to do (vertical axis) versus time (horizontal axis). • Scrum of Scrum: Ambassadors from each scrum team to collaborate • If separate teams work on the same project they work on the same product backlog • Pair Programming: (One strategic and other tactical) • Kanban Board: Shows items needed to be produced next • Planning Poker: To estimate size of tasks (Both business and technical participate in planning) • Refactoring: (Improving code while preserving its external behavior)