811672018 Motorola Solutons Mail - WEEKENO READ - Ale Cheat Sheet ® Samia Surv amin suve1@moteclasluon.com> WEEKEND READ - Agile Cheat Sheet 1 message Andrew Sinclair Fri, Mar 23, 2018 at 9:10 PM Reply-To: DynaList Reply ‘To: Distribution List Agile Cheat Sheet Agile development has become increasingly popular because it reduces risk and, over time, increases velocity, There are a number of Agile frameworks and maturity models, and it's easy to get carried away with how sexy some of these seem are, As with most things in life, itis important to master the basics before getting distracted or carried away with the cool things you could do, Let's learn “wax o” wax of" first. It's important to understand why agile is so important. Working from a benefits mindset changes the approach to project planning and makes us more successful throughout the leaming process. The main benefit Agile offers is reducing risk by breaking the work into smaller chunks and getting feedback, earlier, To do this well, you have to follow a few basic non-negotiable rules, There are also a few good behaviors that I, and others, have observed over the years (and through lots of failure). You can debate additional behaviors or non-negotiables, but don't get carried away by adding too much process. Remember, the key to Agile is reducing risk and it's a learning process focused on the team driving their own improvement. To provide clarity on the Agile lifecycle, the non-negotiables, and desired behaviors we are striving for, here are the guideposts for the Software Enterprise Agile Framework. peer eer) it co Mv PRODUCT BACKLOG = ‘THE NON-NEGOTIABLES - 1. There can be exactly one person that can order the backlog. In Agile development, this is a role referred to as the product owner (for us, this will ypically mean our Product Managers). 2 Each scrum team has their own backlog. 3, Sprints are a fixed duration, This is super important because you need to measure throughput. 4. Ascrum team should be no more than 6-12 people. All members of the scrum team should be able to work on any item taken into the sprint (resources are fungible and there is no ‘specialization. hitpssimail google. comimallu0/?u=28K=76351 be 4cBjever=hSuRSIZCWY.en.Scbl-gmall fe 180812.12_pSBView=pr&qrcheatBsearch=query&ih=1... 1/3811672018 Motorola Solitons Mall - WEEKEND READ - Agile Cheat Sheet 5. There must be a sprint kick off meeting, and at that time, the team (not the PO) agrees to take the items from the top of the backlog into the sprint. 6. There must be a sprint retrospective after every sprint at which time the team discusses how they can improve the process. 7. Items on the backlog are not done until they are coded, refactoring is done, testing is done with automation (with all bugs fixed), and everything is documented. This is “done, done” 8. At the end of the sprint, the product must be releasable. You don't have to release to ‘customers, but you should be able to. You could release to she fit does not meet the Minimum, Viable Product (MVP) criteria, 9, One or more scrum teams make up a release vehicle (RV), where an RV is a well-defined and independently shippable component, like an application or a service library, that can ship without breaking the things that are dependent on it 10, Never extend the sprint. Ifthe team fails to complete the iterns they took into the sprint by the time the sprint ends, they should fail the sprint, learn, and start again with the missing work at the top of the backlog. ays up, Even coe. Version inert or == Poscanta spite ia peien Oboe PO! chat beac, ie yu weno Ship wht eng te tng al re osteo wth wa ere sprtha saree | amore ny po th rms epenteten ‘THE BEHAVIORS - 1. Sprint failure is not team failure. Sprint failure is a learning moment. Don't fear falling a sprint. Expect about 50% to fail in the boginning and 10% once you have a well-run team. 2. Ifthe team completes the work before the end of the sprint, they should either take some time off (goto the beach) or spend time refactoring and writing more automation. In the retrospective, decide if you want to increase the number of story points you take into a sprint. 3. Product owners take input from many sources. These include customer input, business input, engineering input, and so on. Anyone can put something on the backlog. The PO decides ifit ever gets prioritized. 4, Sprints should be short, typically two wel better optimize, Release often and get feedback. 5. Use story points rather than time to size backlog items. You don't have to, but trust me, it works better because people naturally try to schedule time. 6. If the PO discovers there is a problem with the work in the sprint, for example, a requirement change, she can fail the sprint 7. For RVs to be truly independently shippable, they must version interfaces and ensure backwards compatiilly between components and RVS. This is to reduce the risk of failure, and let you hitpssimail google. conimallu0/?u!=28K=76351 be 4cBjever=hSuRSIZCWY.en.cbl-gmall fe 180812.12_p3BVieW=pr&q-cheatBsearch=queryBIh=1... 2/3sriz0%8 Morte SoluionsMall- WEEKEND READ - Agile Cheat Sheet 8. Always update Jira (or whatever you use) as you complete work so that you can measure progress. 8. Don't lot the PO interfere with the team or the work in the sprint once the sprint has started. 10. if something is unclear about a work item, ask the PO. 11. Be fanatical about decomposing work into the smallest possible chunks. 12 Involve everyone in sprint planning and costing, if you want to get buy in. Don't leave this to the dev lead. 13, Everyone on the sprint team codes. Dev managers and architects that don't code, don't add value. 14, Add spikes to the backlog to pay down technical debt and to do investigations. A spike is, a timeboxed work item. You are reducing your capacity by taking out a chunk of time. : an vf Lp 9 2 2s ? vf ti ES ha Loads Only ONE oe Esch team has thelr. RV ica wel defned, Product Owner or ‘own backog indopondenty Sprint Kicko ‘shippabie component (Orders the backog Day oral Fungi. ro that shins wihout specialization breaking tings its paneer Sprint Retrospective i problems) dented ‘pendant ont Additional reading: Don't read lots of books until you have the basics or you will get enamored with advanced ideas that don't work. If you must read, read this: Commitment: A novel about Managing Project Risk. Graphics can be found here. tpssmail google. commalluO/?u=28 gmal_fo_180812.12_pS8view=pt&q-cheat&search=query&th=1... 3/3