Agile Methodology. Kaushik Chokshi CTO

Transcription

1 Agile Methodology Kaushik Chokshi CTO

2 Contact Kaushik Chokshi / Chief Technology Officer Cohealo, Inc. Collaborative Healthcare Logistics 6111 Broken Sound Pkwy NW Suite 360 / Boca Raton, FL Mobile Office x703 Skype - KaushikChokshi Presentation Title 8/21/2013 2

3 A game rules Create a process to give and receive the ball You cannot pass the ball to the person next to you The ball must travel through the air The ball must return to the person who started Each person must receive and pass Presentation Title 8/21/2013 3

4 A game create products When the ball travels successfully through following the rules three times, that s one product Introspect for one minute Give estimate Create a product and time it Continue for 4 sprints Presentation Title 8/21/2013 4

5 Metrics Round 1 Round 2 Round 3 Round 4 Round 5 Estimate Actual comment Presentation Title 8/21/2013 5

6 Presentation Title 8/21/2013 6

7 What I like about Agile Work in short bursts Evaluate and improve Ask the team (self-organizing) Define doneness Best estimation tool Excellent metrics Empowers developers Eliminates unnecessary unplanning and interruptions Presentation Title 8/21/2013 7

8 What I don t like about Agile Emphasizes speed over other criteria Technical debt Everything is a Phillips screw Presentation Title 8/21/2013 8

9 Scrum in 100 words Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

10 Putting it all together Image available at

11 Scrum framework Roles Product owner ScrumMaster Team Ceremonies Sprint planning Sprint review Sprint retrospective Daily stand ups Artifacts Daily scrum meeting Product backlog Sprint backlog Burndown charts

12 Introducing Agile to your team Resistance from developers If possible, get training or Start with the standups then burst-and-evaluate cycle, ask the team!

13 Tools Presentation Title 8/21/

14 Tools User stories / Product Backlog / Requirements / Specifications Code Ready Requirem ent Applicatio n Descriptio n Category Estimate dev days Priority - Priority - Projected $ Benefit Proposed Release Other costs Actual dev days Actual $ benefit Notes off shore CSP00001 yes Improve Dashboard CSP See notes Usability 10 3 yes CSP00002 yes Improve Schedule CSP See notes Usability 15 3 CSP00003 yes Improve Contacts CSP see notes Usability 5 4 yes CSP00004 no scheduler CSP00005 no Digital Signature CSP CSP00006 no webmethods API CSP CSP00007 yes Improve Support screen; integrate with support systems Infrastru cture Provide service (in CSP or SharePoint or similar) to send scheduled, templated s to customers Usability for onboarding, equipment maintenance schedule, 10 4 reports, and other processes Faciliate the process of capturing signatures in the field for deliveries and pickups provide open API and webmethods so that other applications can effectively use the entire operational flow of CohealoShare programmatically Usability 15 4 yes Scalability 20 6 CSP see notes file Usability 10 4 yes CSP00009 no Equipment maintenance schedule CSP Send user alerts on maintenance schedule; allow changes to equipment profile Usability 5 5 Presentation Title 8/21/

15 Tools Backlog summary Ready (Multiple Items) Row Labels Count of Category Sum of Estimate dev Differentiator Quality 1 5 Required to do bus 4 18 Scalability Usability Compliance 1 5 Grand Total Presentation Title 8/21/

16 Tools Stand ups Date Release Task Member Hours 5/20/ Q2-R3 Assess and document AWS set up SS 6 5/20/ Q2-R3 Establish source control SS 2 5/20/ Q2-R3 Activity log SS 2 5/20/ Q2-R3 Compatible with IE 8 MS 2 5/20/ Q2-R3 Training MS 8 5/20/ Q2-R3 Plan and design 2013-Q2-R3 release MS 1 5/20/ Q2-R3 Plan and design 2013-Q2-R3 release KC 8 5/21/ Q2-R3 PTO SS 8 5/21/ Q2-R3 Plan and design 2013-Q2-R3 release KC 8 5/21/ Q2-R3 Certify general QA MS 2 5/21/ Q2-R3 Compatible with IE 8 MS 2 5/21/ Q2-R3 Compatible with IE 8 SS 2 5/21/ Q2-R3 Configure SS 6 5/21/ Q2-R3 Develop Cohealo.com MS 3 5/22/ Q2-R3 Plan and design 2013-Q2-R3 release KC 8 5/22/ Q2-R3 Certify general QA MS 2 5/22/ Q2-R3 Compatible with IE 8 MS 2 5/22/ Q2-R3 Compatible with IE 8 SS 2 5/22/ Q2-R3 Configure SS 6 5/22/ Q2-R3 Develop Cohealo.com MS 3 5/23/ Q2-R3 Plan and design 2013-Q2-R3 release KC 8 5/23/ Q2-R3 Certify general QA MS 2 5/23/ Q2-R3 Compatible with IE 8 MS 2 5/23/ Q2-R3 Compatible with IE 8 SS 2 5/23/ Q2-R3 Configure SS 6 5/23/ Q2-R3 Develop Cohealo.com MS 3 5/24/ Q2-R3 Develop Cohealo.com MS 3 Presentation Title 8/21/

17 2013-Q3-R1 status Priority Title 2013-Q3-R1 KC % 24% Q3-R1 Development KC % 1 Plan and design 2013-Q3-R1 release KC Assess and document AWS set up KC Deploy 2013-Q3-R1 KC Compatible with IE 8 MS Improve errors SS Activity log SS Capture number of cases covered by request SS Case Count report SS Establish source control SS Automated testing tools KC Develop Cohealo.com MS Configure SS Develop Service Line SS Develop Equipment DB MS Q3-R1 Maintenance KC % 2 Work on tickets Q3-R1 QA KC % Certify general QA Research QA automation Q3-R1 Unplanned Activity KC % Do general unplanned KC Q3-R1 Other Activity KC % PTO KC Training MS Do admin KC Do IT: mail, sharepoint, etc MS Do recruiting KC Owner Estimate Done To Do Done/Estimate Done / (To Do + Done) Days Days Elapsed Days Remaining Days Burned Relative Allocation Comment Release Start Release End Deploy 20-May 28-Jun 6-Jul 8/21/

18 Burn 8/21/

19 QA questions Are our processes adequate and sufficient? Is our infrastructure adequate and sufficient? Do we have sufficient resources? Can we reliably and repeatedly compile on a development computer and upload executables to AWS dev and production? Is production system safe? Is the source code safe? Can we perform an emergency update? How much time does it take? Can we reliably and repeatedly perform regression testing? Is production backed up? Restorable? Do we have a single point of failure in people or technology? Is CSP properly architected? etc 8/21/

20 Retrospective sample Be honest Be respectful Don t miss your chance to say what you want to say How could it have gone better? QA was not responsive quickly enough What did it feel like? cadence was erratic 8/21/

21 Allocation Trend over releases Allocation Trend over Releases 5/20/2013 Release Calendar days Development Activity Maintenance Activity QA Activity Unplanned Activity Other Activity Open Tickets 2013-Q2-R % 0% 4% 0% 3% Q2-R % 0% 18% 0% 0% Q2-R3 (to date) 39 72% 0% 0% 0% 28% 5 8/21/

22 Backlog summary Projected Allocation for backlog 5/20/2013 Projects Benefit To Do Comment Development (Backlog items) per item % Maintenance Required to do business % QA Required to do business % Unplanned Activity Required to do business 55 5% Other 55 5% Total Work days 1090 Developer work days in a year 250 Number of developers to complete backlog in one year: 4.4 8/21/

23 Ready done Proposed Release (Multiple Items) Vertiglo Completed / Benefits Tracking Sum of Actual $ benefit Sum of Projected $ Sum of Other Row Labels Count of Category Benefit costs Sum of Actual dev days Quality 1 20 Required to do bus Grand Total Ready done Proposed Release 2013-Q2-R1 Sum of Sum of Projected $ Sum of Other Actual $ Row Labels Count of Category Benefit costs Sum of Actual dev days benefit Differentiator 1 4 Required to do bus 1 9 Scalability Grand Total Ready done Proposed Release 2013-Q2-R2 Sum of Sum of Projected $ Sum of Other Actual $ Row Labels Count of Category Benefit costs Sum of Actual dev days benefit Quality 1 7 Required to do bus 1 7 Grand Total 2 14 Ready done Proposed Release 2013-Q2-R3 Row Labels Grand Total Count of Category Sum of Projected $ Benefit Sum of Other costs Sum of Actual dev days Sum of Actual $ benefit 8/21/

24 Yodiz 8/21/

25 User Story - Consumer Story: Consumer As a Consumer I want to consume a shareable asset for definite periods of time For the reasons: that I will make more money than it costs, and I do not need to purchase the asset Communication: I can be part of the community of producers, consumers and enablers Discovery: In using the platform, I can discover better, more efficient, and more enjoyable ways to produce and consume I can discover an entire equipment network which is indexed by price, equipment type, service line, and location. Engagement: In using the platform, I can do my work much more efficiently and more enjoyably I can shop by price, both with device owners and logistics service. After renting devices, Cohealo Share Platform makes recommendations for me which can expend my existing service lines, or approach me with affordable options to expand my service line offering. Acceptance criteria: Presentation Title 8/21/

26 Other stuff Version One, Rally, Yodiz, others Agile Long requirements (Epic stories) might require project management Focus on particular metrics will shift Presentation Title 8/21/

27 Ask the team! 8/21/