Scrum intro conscires


Published on

Introduction to Scrum Methodology

Published in: Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Scrum intro conscires

  1. 1. Prepared byBachan Anand & David Weir
  2. 2.  Introductions Overview of Agile and Scrum Scrum: Vision and Product Scrum: Sprint Scrum: Release Final Thoughts Appendix 2
  3. 3.  As a customer , I want ◦ The ability to go to market faster ◦ Faster return on investment As a Project Manager, I want ◦ To measure the progress of my project in terms of real progress made and product ready to be shipped. As a team member, I want ◦ A sustainable pace ◦ Satisfaction of quality product delivered 3
  4. 4.  Agile is a set of values: ◦ Individuals and interactions over processes and tools ◦ Working software(Products) over comprehensive documentation ◦ Customer collaboration over contract negotiation ◦ Responding to change over following a plan 5
  5. 5.  Highest priority is to satisfy the customer through early and continuous delivery of valuable software Welcome changing requirements Deliver working software(Product) frequently Business people and developers must work together daily throughout the project 6
  6. 6.  Build projects around motivated individuals Most efficient and effective method of conveying information is face-to-face conversation Working software(product) is the primary measure of progress Agile processes promote sustainable development (maintain a constant pace indefinitely) 7
  7. 7.  Continuous attention to technical excellence and good design enhances agility Simplicity (art of maximizing amount of work not done) is essential Best architectures, requirements, and designs emerge from self-organizing teams At regular intervals, team reflects on how to become more effective, then tunes and adjusts 8
  8. 8.  Scrum is an Agile framework that supports lightweight processes that emphasize: ◦ Incremental deliveries ◦ Quality of Product ◦ Continuous improvement ◦ Discovery of people’s potential Scrum is simple to understand, but requires discipline in order to be successful Scrum is not a methodology 9
  9. 9.  Empiricism ◦ Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles Self-Organization ◦ Small teams manage their own workload and organize themselves around clear goals and constraints Prioritization ◦ Do the next right thing Rhythm ◦ Allows teams to avoid daily noise and focus on delivery Collaboration ◦ Leaders and customers work with the Team, rather than directing them 10
  10. 10.  Transparency ◦ Everything about a project is visible to everyone Commitment ◦ Be willing to commit to a goal Courage ◦ Have the courage to commit, to act, to be open and to expect respect Focus ◦ Focus all of your efforts and skills on doing the work that you have committed to doing Respect ◦ Respect and trust the different people who comprise a team 11
  11. 11.  A goal to aspire to Can be summarized in a short statement of intent Communicate it to the team 13
  12. 12.  Thought Leader and Visionary Drives the Product Vision (for example, with Story Mapping) Prioritizes the User Stories Maintains the Product Backlog with the team Accepts the Working Product (on behalf of the customer) 14
  13. 13.  Product requirements formulated as one or more sentences in the everyday or business language of the user ◦ As a <user>, I would like <function> so that I get <value> Each User Story has an associated Acceptance Criteria that is used to determine if the Story is completed 15
  14. 14.  Independent ◦ Not overlap in concept and be able to schedule and implement them in any order Negotiable ◦ Not an explicit contract for features; rather, details will be co-created by Product Owner and Team Valuable ◦ Add business value Estimated ◦ Just enough to help the Product Owner rank and schedule the storys implementation Sized Appropriately ◦ Need to be small, such as a few person-days Testable ◦ A characteristic of good requirements 16
  15. 15.  A living list of requirements captured in the form of User Stories Represents the WHAT of the system Prioritization with respect to business value is essential! Each story has estimated Story Points, which represent relative size, and is determined by those actually doing the work Higher priority items are decomposed and lower priority items are left as larger stories (epics) 17
  16. 16.  Servant Leader Facilitates the Process Supports the Team Removes Organizational Impediments Socializes Scrum to Management Enable close collaboration across all roles and functions 19
  17. 17.  Cross-Functional 5-8 Members Self-Organizing Focused on meeting Commitments 20
  18. 18. 21
  19. 19. 22
  20. 20.  Sprint Planning meeting held at beginning of each Sprint Time and Resources are fixed in any given Sprint Goal is to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit to During planning, Team commits to scope that can be completed in the Sprint, taking into account the definition of Done Story points may be refined 23
  21. 21.  List of stories, broken down into tasks, that is committed for any particular Sprint Owned and managed by the Team Any team member can add, delete or change the sprint backlog with additional tasks 24
  22. 22.  Team creates its own definition of Done in the interest of creating quality software Definition can evolve over sprints Example checklist (not exhaustive): ◦ Unit tests pass (ideally automated) ◦ Customer Acceptance tests pass ◦ User docs written ◦ UI design approved by PO ◦ Integrated into existing system ◦ Regression test/s pass (ideally automated) ◦ Deployed on staging server ◦ Performance tests pass 25
  23. 23.  Meetings held in same location, same time, every day Timeboxed at 15 minutes Encourages self-organization, rhythm, and collaboration Not a status meeting Each Team member speaks to: ◦ What did I accomplish in the last 24 hours ◦ What do I plan to accomplish in the next 24 hours ◦ Any impediments getting in the way of my work 26
  24. 24.  Active visual indicator of flow of work Should be visible to team members at all times Should be kept current Encourages self- organization, and collaboration 27
  25. 25.  Shows daily progress in the Sprint X-axis is the number of days in the Sprint Y-axis is the number of remaining stories 28
  26. 26.  Occurs at the end of each Sprint Inspect and Adapt the product (Empiricism) The team meets with the Product Owner (and Stakeholders) to demonstrate the working software from the Sprint This is a hands-on software demo (not a PowerPoint) that usually requires some prep beforehand 29
  27. 27.  Occurs at the end of each Sprint Inspect and Adapt the process (Empiricism) Team and ScrumMaster meet to reflect on what went well and what can be improved Tone of the meeting is that everyone did their best and now look to how can we improve Retrospectives must conclude with team commitments to action 30
  28. 28.  Total number of story points completed by a team in a Sprint Can be used by the team as a reference during Sprint Planning Used by Product Owner to plan out the releases 32
  29. 29.  Product Owner, in conjunction with the team, formulates Release Plans by applying the team Velocity to the Product Backlog Release Plans are revisited after every Sprint Two ways to approach ◦ Fix scope and determine how many sprints are needed ◦ Fix time and determine how much scope can be completed 33
  30. 30.  Shows progress across Sprints X-axis is the number of Sprints Y-axis is the total number of stories 34
  31. 31.  Scrum is a lightweight framework with a simple set of rules, built on foundations and values Scrum enables teams to discover their true potential and deliver quality software that adds business value 36
  32. 32.  Product Owner ◦ Thought Leader and Visionary, who drives the Product Vision, maintains the Product Backlog, prioritizes the User Stories, and accepts the Working Software (on behalf of the customer) ScrumMaster ◦ Servant Leader, who facilitates the process, supports the Team, removes organizational impediments, and socializes Scrum to Management Team ◦ Cross-Functional group of 5-8 Members that is self- organizing and focused on meeting Commitments 38
  33. 33.  Product Backlog ◦ A living list of requirements captured in the form of User Stories, prioritized according to business value Sprint Backlog ◦ List of stories, broken down into tasks, that is committed for any particular Sprint; owned and managed by the Team Taskboard ◦ Active visual indicator of flow of work Sprint Burndown Chart ◦ Shows daily progress in the Sprint Release Burndown Chart ◦ Shows progress across Sprints 39
  34. 34.  Sprint Planning ◦ Held at beginning of each Sprint, with the goal to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit to Daily Standup ◦ Meetings held in same location, same time, every day, with the goal of ensuring that team members are in synch (not a status meeting) Sprint Review ◦ Occurs at the end of each Sprint, with the goal of inspecting and adapting the Product Retrospective ◦ Occurs at the end of each Sprint, with the goal of inspecting and adapting the process 40