1 / 21

Scrum…Buts

Scrum…Buts. Joy Kelsey Agile By Example Warsaw October 16 th and 17 th 2013. Agenda. Introduction Definition and example of a Scrum…But Top 10 Scrum..But scenarios Summary. Scrum...But. Introduction Joy Kelsey

geordi
Télécharger la présentation

Scrum…Buts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Scrum…Buts Joy Kelsey Agile By Example Warsaw October 16th and 17th 2013

  2. Agenda Introduction Definition and example of a Scrum…But Top 10 Scrum..But scenarios Summary

  3. Scrum...But Introduction • Joy Kelsey • Working as Scrum Master and Agile coach at BCA the UK and Europe's leading vehicle remarketing company • Experience • Over 34 years in IT • MSc – Computer Based Learning and Training, • Professional qualifications • Prince 2, • Professional Scrum Master, Certified Scrum Master, • Dynamic Systems Development Method practitioner, • Project Management Institute-Agile Certified Practitioner

  4. Scrum...But • Everyone has a different attitude to Agile

  5. Scrum...But Top 10 of some of the scenarios that I have come across

  6. HELP THEM SEE

  7. Scrum...But A ScrumBut has a particular syntax:  (ScrumBut) (Reason) (Workaround) ScrumBut Example: "(We use Scrum, but) (having a Daily Scrum every day is too much overhead,) (so we only have one per week.)“ Scrum buts usually come around due to not giving Scrum a good chance to bed in for various different reasons • Lack of management support, fearing change, pressure of work etc

  8. 1. Scrum...But We use Scrum but we know what we are doing so we don’t need to communicate until we deliver • I have a supplier who is working for me and he has said he is using Scrum: • They do not give us anything until when they feel they have something to deliver

  9. 2. Scrum...But We use Scrum, but decided on our own scrum definition so that we can just use the best bits! • We don't need documentation or plans we are Agile • We don't need to have lots of meetings we are Agile

  10. 3. Scrum...But We use Scrum but we run our sprints in sequence with test so that we can focus on developing Dev Test Live Dev Test Dev Live

  11. 4. Scrum...But We use Scrum, but we are following our old phases so that we know when we are finished • First sprint Analysis, • Second sprint is design • Third a development sprint • Fourth is a test sprint therefore we are sprinting!

  12. 5. Scrum...But We use Scrum, but we update our burndown chart every day even when we have not completed the story so we can see movement on the chart • Every day we see if we have done any work on our stories – if we have, we burn down the hours spent

  13. 6. Scrum...But We use Scrum, but we do everything ok so we don’t have retrospectives • We are coping with our work load so we must be doing ok why do we need to have a retrospective every sprint

  14. 7. Scrum...But We use Scrum, but don’t like working on anything unless we have completely defined it so we break each story down to one story point so that we can better estimate them • Our sprint planning meetings are taking so long!!!

  15. 8. Scrum...But We use Scrum, but we do not need a product owner, we only have internal customers so we send emails to everyone in the business • Why does the business keep complaining we are not doing very much – and they say that what we are doing is not what they asked for

  16. 9. Scrum...But We use Scrum, but the PO decides to give us new items so that we are adaptive and flexible • If the PO wants something different he will just add it mid sprint and tell us to get on with it

  17. 10. Scrum...But We use Scrum, but we are developers we do not test so we don’t seem to be able to do as much as we plan to do because we don’t have enough testers • Our testers are a bottle neck

  18. Scrum...But Those were 10 areas I have come across – to summarise: • What is important about Scrum? • “Is a framework within which you can employ various processes and techniques” – Scrum guide July 2013

  19. Scrum...But • Willingness to listen and change/adapt Users Scrum Team Stakeholders Customers

  20. Agile Values Focus Courage Openness Commitment Respect 5

  21. Contact I am happy to receive any comments and or feedback from you at this address: joyscrumqueen@outlook.com Agile : References http://www.scrum.org http://www.scrumalliance.org Agile Project Management with Scrum by Ken Schwaber Agile Project Management by Jim Highsmith Agile Estimating and Planning by Mike Cohn User Stories Applied by Mike Cohn Lean Software Development by Mary and Tom Poppendieck Agile Software Development by Robert Martin Agile Product Management with Scrum by Roman Pilcher This presentation was inspired by the works of many people, if you think that anything in this presentation should be changed, added or removed, please contact me at joyscrumqueen@outlook.com

More Related