bca.co.uk 01BMW Tender Inspect & Collect bca.co.uk Scrum…Buts Joy Kelsey Agile By Example Warsaw October 16 th and 17 th 2013

bca.co.uk 02 Why BCA Agenda Introduction Definition and example of a Scrum…But Top 10 Scrum..But scenarios Summary

bca.co.uk 03 Why BCA 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

bca.co.uk 04 Why BCA Scrum...But  Everyone has a different attitude to Agile

bca.co.uk 05 Why BCA Scrum...But Top 10 of some of the scenarios that I have come across

bca.co.uk 06 Why BCA SEE

bca.co.uk 07 Why BCA 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

bca.co.uk 08 Why BCA 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

bca.co.uk 09 Why BCA Scrum...But We use Scrum, but we know what we are doing so we don’t 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 me anything until when they feel they have something to deliver  Ask them to give high level estimates on requirements  Ask for a release plan  Ask to have regular input into the Product Backlog  Acceptance criteria, priorities etc  Frequent communications to give frequent feedback  Attending Sprint Reviews (minimum)

bca.co.uk 010 Why BCA 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

bca.co.uk 011 Why BCA 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 we are Agile  We don't need to plan we are Agile  Working software OVER comprehensive documentation – does not mean no documentation just documentation that is going to be needed and will be read i.e burndowns, product backlogs, training documentation etc  Responding to change OVER following a plan – does not mean you do not have to plan “ Plans are useless, planning is indispensable” - Eisenhower  High level plans are a base so that you know which route you are planning to take

bca.co.uk 012 Why BCA 3. Scrum...But We use Scrum but we run our sprints in sequence with test so that we can focus on developing DevTest Dev Live Test DevLive

bca.co.uk 013 Why BCA Scrum...But We use Scrum but we run our sprints in sequence with test so that we can focus on developing  Dev and testing are to be carried out in one sprint  Ensure the Story can be completely “Done” and finished, allowing the burndown to be updated  Measure by completed work not %’s  Having overhanging work gives an unclear picture on the work remaining on the project

bca.co.uk 014 Why BCA 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!

bca.co.uk 015 Why BCA 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 then we start a development sprint then we test – therefore we are sprinting!!  Try taking one small feature and in one sprint do the analysis, design, development and test  Sprint Review – demonstrate a completed feature

bca.co.uk 016 Why BCA 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

bca.co.uk 017 Why BCA Scrum...But We use Scrum, but we update our burndown chart every day even when we have not completed the task 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  Working software over comprehensive documentation  Working software is the principle measure of success  Remember to track completed items not %’s- this enables a clearer picture of what work is left in the sprint

bca.co.uk 018 Why BCA 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

bca.co.uk 019 Why BCA Scrum...But We use Scrum, but we do everything ok so we don’t have retrospectives to spend more time developing  We are coping with our work load so we must be doing ok why do we need to have a retrospective every sprint  Retrospectives are there to enable the team to discuss what went well and if they can improve on what they have completed – Inspection and adaptation. There are always ways in which we could still improve – more quality, working smarter etc

bca.co.uk 020 Why BCA 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!!!

bca.co.uk 021 Why BCA 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 each so that we can better estimate them  Our sprint planning meetings are taking so long!!!  It is not necessary to know everything about the requirement just enough to know what is required and how to start (Adaptation)  Do not take too many items into the Sprint planning session  Ensure the stories are detailed enough from the Product Backlog Refinement sessions  Ensure your Product Backlog Refinement sessions are in place, routinely and timely (at least 10% of sprint)

bca.co.uk 022 Why BCA 8. Scrum...But We use Scrum, but we do not need a product owner, we only have internal customers so we send s 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

bca.co.uk 023 Why BCA Scrum...But We use Scrum, but we do not need a product owner, we only have internal customer so we send s 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  Nominate one person as a central point of contact – this will allow a more cohesive product backlog and give focus to the information circulated  A product owner does more than just update people  they negotiate the priorities,  give a vision to the team,  protect the team from the vagaries of customer/business politics  The PO also ensures the business value of the work carried out in the sprint

bca.co.uk 024 Why BCA 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

bca.co.uk 025 Why BCA 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  Being flexible does not mean anything new can be added at any time, the team must have some kind of focus or goal to enable them to know what they have to do and that they have achieved what they forecasted to do.  The team decide on the Sprint backlog together – this is their focus and what they forecast to complete  Tell the PO that he/she has to wait for the sprint end or to abandon the sprint with all the complications that entails

bca.co.uk 026 Why BCA 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

bca.co.uk 027 Why BCA Scrum...But We use Scrum, but we are developers we do not test so 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  Function as a team  Team should be cross skilled  Anyone can test  Reducing bottlenecks when they arise  Nobody needs to be an expert in everything just have the basics to assist the team to complete the sprint

bca.co.uk 028 Why BCA 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

bca.co.uk 029 Why BCA Scrum...But  Willingness to listen and change/adapt Stakeholders UsersScrum Team Customers

bca.co.uk 030 Why BCA 5 Agile Values FocusCourageOpennessCommitmentRespect

bca.co.uk 031 Why BCA Contact I am happy to receive any comments and or feedback from you at this address: Agile : References 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