The Software Delivery Experts. Agile, DevOps & QA Conference

Transcription

1 The Software Delivery Experts Agile, DevOps & QA Coferece

2 The Software Delivery Experts Settig Agile-Cetric Release Criteria Aka Doe-Ness or Defiitio of Doe (DoD) Bob Gale Director of Agile Practices

3 Outlie Itroductio 1. Agile Goals & Criteria 2. Team Level: Doe-Ness 3. Sprit Level: Story & Acceptace 4. Release Level: Freeze, Etry & Exit Criteria, ad Release Criteria 5. Release Trai / Ifluece Poits 6. Q&A

4 Establishig Goals & Criteria Why They Are Crucial? Agile teams are essetially self-directed, so plas do t drive behavior or success People & Teams do ad Goals drive each Team! The teams the swarm aroud the goals, usig their creativity ad teamwork to figure out: What s most importat How to achieve it Always lookig for simple & creative 20% solutios With focused ad cosistet uality practices & activities

5 Lea Priciples Applied Most importat aspects first KISS priciple; o Gold-platig Small deliverables; worked o serially Deliver Ed-to-Ed behavior I thi Slices UI to Backed DB Drive to doe, ito ivetory as completed compoets, as soo as possible! Avoidig 90% doe sydrome Post-Sprit itegratio collaboratio Rarely re-visited; midset is to ruthlessly miimize rework

6 Notios of Doe-Ness i Developmet Need to defie Doe from team members perspectives If you re a developer, what does I m doe with that story mea? ü Code complete; ü Checked i build successful; ü Itegratio; ü Ru by the Product Ower; siged-off Code reviewed (paired) Uit tests developed passed QA collaboratio Every type of work should have a defiitio of Doe-Ness! How else could you estimate the work?

7 Notios of Doe-Ness i Testig If you re a tester, what does I m doe with that story mea? ü Test cases desiged w/a broad view to test cases (uit, fuctioal, acceptace, regressio) ü Test cases pair-reviewed with developmet & test team members ü Test cases - checked ito repository ü Ra test cases successfully; o issues ü Ra Acceptace Tests with the Product Ower ü Automated the Acceptace Test cases ü Coected the automatio to the Cotiuous Itegratio eviromet ü Validated idepedet executio

8 Doe-ess criteria, circa 2010 Agile Coferece - Example: Salesforce.com User Stories All defied Acceptace Criteria for a user story have bee met. Code Code implemetig the user story fuctioality is checked i ad follows departmet stadards. This icludes QE-reviewed automated tests checked i with all feature code. No ope regressios (you break it, you ow it), with automated tests writte for all regressios, ad reviewed by QE. No ope P1 & P2 bugs for the implemeted fuctioality i the sprit.

9 Doe-ess criteria, circa 2010 Agile Coferece - Example: Salesforce.com Quality 70% of all test cases are automated ad adhere to our automatio coverage priciples ad stadards. Code Coverage of 70% (uless a differet % discussed ad agreed to by team). Test pla, cases ad executio for sprit fuctioality, ad regressio ad cross fuctioal test cases related to sprit fuctioality, eed to be reviewed ad etered ito test repository with 100% of test cases i repository executed, ad all P1/P2 cases passig. All resolved bugs have bee verified ad closed for the sprit fuctioality.

10 Doe-ess criteria, circa 2010 Agile Coferece - Example: Salesforce.com Security Features adhere to security priciples ad stadards with all critical issues resolved. All high risk features have bee Threat Modeled with the Product Security team. I depth security testig scheduled, if ecessary, durig the release. Performace/Scalability Performace/Scalability impact of sprit fuctioality uderstood ad uatified, ad system testig scheduled

11 Doe-ess criteria, circa 2010 Agile Coferece - Example: Salesforce.com User Experiece UE has reviewed ay ew features or sigificat chages i the UI, ad critical feedback has bee icorporated, with all resultig P1 ad P2 UI issues fixed. Usability testig has bee completed (uless deemed uecessary), with all resultig P1 ad P2 UI issues fixed. Code ad the UI have bee reviewed to esure 508 compliace - see the compliace checklist features that caot be made compliat have bee brought to the attetio of the UE team Localizatio All UI compoets have labels ready for localizatio vedors.

12 Doe-ess criteria, circa 2010 Agile Coferece - Example: Salesforce.com Documetatio User documetatio that describes all aspects of the sprit fuctioality is complete ad checked i. Product Metrics Metrics to cocretely measure customer usage (value delivery) of the sprit fuctioality have bee defied.

13 Impact of Doe-Ness Elsewhere It s ot just a exit criteria! It s a heuristic for teams to check themselves as they collaborate i performig acceptable work A cosistetly aliged bar for professioal egieerig work It s also icredibly importat i sizig the Product Backlog elemets ad i determiig Release & Sprit plas Icludig architecture & desig ad i workig research spikes

14 Story Acceptace Each User Story should have acceptace criteria as part of the card They should focus o the verifiable behavior, core busiess logic, key reuiremets for the story Typically, they are crafted by the Product Ower Leveragig skills of Busiess Aalysts ad Testers Story acceptace tests are ormally automated ad ru as part of feature acceptace AND regressio FitNesse ad Cucumber are amog the Ope Source tools eablig this

15 User Story Examples As a dog ower, I wat to sig-up for a keel reservatio over Christmas so that I get a cofirmed spot Verify idividual as a registered pet ower Verify that preferred members get 15% discout o basic service Verify that preferred members get 25% discout o exteded services ad reservatio priority over other members Verify that past Christmas customers get reservatio priority Verify that declies get with discout coupo for future services

16 Story Sprit (Executio) Readiess Prevets teams from takig o stories that are ill groomed or defied Icreases sprit success ü The story is well-writte; ad has a miimum of 5 Acceptace Tests defied ü The story has bee sized to fit the teams velocity & sprit legth: 1-13 poits ü The team has vetted the story i several groomig sessios it s scope & ature is well uderstood ü If reuired, the story had a research-spike to explore (ad refie) it s architecture ad desig implicatios ü The team uderstads how to approach the testig of the stories fuctioal ad o-fuctioal aspects ü Ay depedecies to other stories ad/or teams have bee coected so that the story is sychroized ad deliverable ü The story aligs with the Sprits Goal ad is demostrable

17 Defiitio of Ready Kaba Board blog/user-storiesdefiitio-readykaba-board/

18 Iteratio / Goal Acceptace Each Scrum Sprit has a Product Ower determied goal Usually sprit success is ot determied by the exact umber of completed stories or tasks Istead, what most importat is meetig the spirit of the goal Deliver a 6 miute demostratio of the software that demostrates our most compellig value features ad achieves veture capital ivestmet iterest

19 Release Criteria Goals ad objectives for the etire project release Usually they are multi-faceted, defiig a broad set of coditios Reuired artifacts & levels of detail Testig activities or coverage levels Quality or allowed defect levels Results or performace metrics achievemet levels Collaboratio with other groups depedecy maagemet Compliace levels That IF MET would mea the release could occur.

20 Release Trai Maagemet Iterative model with a release target Product cetric Focused o a productio push/release Sychroized Sprits across teams Some teams are u-sychroized, but leads to less efficiet cross-team (product) iteractios Cotiuous Itegratio is the glue Icludig automated uit ad feature tests; partial regressio Notio of a Hardeig Sprit Focused more o Itegratio & Regressio testig Assumptio that it s mostly automated Eviromet promotio Defie a fial Hardeig Sprit where the product is readied for release Documetatio, Support, Compliace, UAT, Traiig

21 Release Trai Maagemet Iteral Drivig Forces Customer s ability to accept the release Value beig delivered i the release purely scope Hardeig Sprit reality Time, Complexity, Automatio, Size, Compliace, ad Idustry Iteral team readiess Customer support Sales & Marketig readiess Overall documetatio & traiig

22 The Agile Release Trai Sychroized Iteral Release Exteral Release Team 1 Iterate Iterate Harde Iterate Iterate Iterate Cotiuous Itegratio Team 2 Team 3 Iterate Iterate Harde Cotiuous Iterate Iterate Harde Iterate Iterate Itegratio Iterate Iterate Iterate Iterate X-team Harde Docs, Traiig, Support, UAT, Comp. Cotiuous Itegratio Team 4 Iterate Iterate Harde Iterate Iterate Iterate Cotiuous Itegratio Team

23 The Agile Release Trai Example: ecommerce / SaaS Model 10 days 10 days days Exteral Release Team 1 Team 2 Team 3 Team 4 Team 8 Eviromet Evolutio Iterate Iterate Iterate Iterate Iterate Cotiuous Itegratio Iterate Cotiuous Itegratio Iterate Cotiuous Itegratio Iterate Cotiuous Itegratio Harde Harde Harde Harde X-team Harde Docs, Traiig Rise & Repeat Dev + QA Dev + QA QA -> Stagig Productio

24 Release Trai Maagemet Motivatioal Drivig Forces Visio Schedule for delivery Feature set(s); Miimal Marketable Features (MMF s) Goals for each team Themes Which teams will be workig o what compoets? Packages of User Stories Prioritized by busiess value & eed Ed-to-Ed Use Cases Itegratio focused executio

25 Release Goal Settig A Key for Coordiatio As you scale, each plaig level should create criteria (Sprit Goals) that are Iterrelated ad cohesive Focused towards the ed product release ad ot simply o each teams deliverables Idetify depedecies ad overall workflow The traditioal otio of Charterig also applies at the higher levels, with Charters defied as: Goals, Objectives & Scope Clearly measurable view to Doe Release Criteria Multi-faceted view towards uality (defects, coverage, o-fuctioal reuiremets) Allowig for team scope trade-offs

26 Levels of Criteria Activity Criteria Example Basic Team Work Products User Story or Theme Level Sprit or Iteratio Level Release Level Doe ess criteria Acceptace Tests Doe ess criteria Release criteria Pairig or pair ispectios of code prior to check-i; or developmet, executio ad passig of uit tests. Developmet of FitNesse based acceptace tests with the customer AND their successful executio ad passig. Developed toward idividual stories ad/or themes for sets of stories. Defiig a Sprit Goal that clarifies the feature developmet ad all exteral depedecies associcated with a sprit. Defiig a broad set of coditios (artifacts, testig activities or coverage levels, results/metrics, collaboratio with other groups, meetig compliace levels, etc.) that IF MET would mea the release could occur.

27 DoD aother view Task: Implemeted Uit Tested Code commeted Code peer reviewed I source truk I CI build Coverage met Stadards met Tracked Other metrics? Story: AC met All agreed tasks doe Fuctioally tested / auto test built All kow bugs fixed CI success, icludig DB / cofig updates Smoke-tested Itegratio tested Tracked Documeted for user view Sprit: Ed date met Stories demo d UAT complete Retro held ad documeted Product backlog updated Exploratory testig doe Performace (etc.) tested Regressio suite updated ad verified All bugs closed or postpoed Istallatio works Documeted for tech. view Release: All agreed sprits doe Itegratio tested / hardeed Documetatio tested Istall packages complete Release otes Marketig collateral Regressio test suite complete Security testig PO sig-off

28 Exercise Gather i small groups; better that you are from the same compay/ orgaizatio OR those with similar characteristics I this sectio, we discussed the various levels of criteria that are importat withi agile teams. 1) Amogst your team, discuss how you ve established goals & criteria i your Agile (or o-agile) teams What levels are the most importat? What levels do t matter as much? 2) What part does the team play i defiitio? Should play? 3) Does defiig what doe meas really matter? How? 4) If you had oly oe to pick, which would it be? Ad why?

29 Wrap-up Self-directed Agile teams are directed by their Goals. There are 4 Levels: 1. Professioal / Doe-ess 2. Feature / Story 3. Iteratio / Sprit 4. Release Criteria of goals drivig Excellece i ay agile team. I Waterfall you get what you Pla for I Agile, you get what your Goals drive you towards

30 Questios? Ø Fial uestios or discussio? Thak you!

31 Cotact Ifo Zeergy Techologies Zeergytechologies.com Bob