Succeeding with SCRUM

241 views

Published on

SCRUM refresher

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
241
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Succeeding with SCRUM

  1. 1. Sharique Khan
  2. 2.  Everyone goes home on time…by .. Cutting the confusion Cutting Waste (feature creep) Better Visibility Surfacing the risks and challenges early Protecting the team Delivering software we are proud of Happy Customers & more business
  3. 3.  You dont need any documentation Agile means no plan Agile doesnt need up front architecture & design No managers / leads thank you, we are doing Scrum! You need only three roles: PO, SM and team One can learn Agile from a book Dilution of Responsibility & Accountability
  4. 4.  Establish Product Vision Re Visit Roles / Responsibilities / Accountability Staffing & Resource Planning Trainings – Technology , Scrum Architecture & Design Risk Identification – Technology , Skill, People
  5. 5.  Everyone needs to understand Why are we doing this? How this is going to do cost saving or generatemore profit? How this product will be better than competition? What problems this product solves?
  6. 6.  User stories at times do not reflect the exactrequirement… so for each story we shouldknow : Functionality Ux Performance Security ……
  7. 7.  Installer in every sprint Integration in every sprint System Testing in every sprint
  8. 8.  People Product Owner – only 1 Scrum Master – only 1 Team – (size < 7, co located, motivated) SCRUM Framework Sprint Planning Sprint Review Sprint Retrospective Product Backlog Grooming Daily Stand Up
  9. 9.  Artifacts Release Backlog Product Backlog Sprint Backlog Sprint Burn down
  10. 10.  Scrum Master & Tech lead / Architect shouldbe actively working to remove and obstacles
  11. 11.  Lack of Solid Design is not SCRUM Also too much detailed design upfront is alsonot SCRUM. In Sprint-Zero good architecture & designwhich is scalable should be established.
  12. 12.  It is a list of Prioritized & estimated UserStories and .. Outstanding defects
  13. 13.  Skilled Passionate Willing
  14. 14.  Preparation for the next sprint Identify & Mitigate Risks for next sprint stories Establish design enhancements for next sprint Establish Test Strategy for next sprint
  15. 15. That’s all folks !!..

×