Agile Methodology Kaushik Chokshi CTO Contact Kaushik Chokshi / - PowerPoint PPT Presentation

Agile Methodology Kaushik Chokshi CTO

Contact Kaushik Chokshi / Chief Technology Officer Cohealo, Inc. – Collaborative Healthcare Logistics 6111 Broken Sound Pkwy NW Suite 360 / Boca Raton, FL 33487 Mobile – 404-558-5153 Office – 855-692-6432 x703 Skype - KaushikChokshi Presentation Title 8/17/2013 2

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/17/2013 3

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/17/2013 4

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

• http://www.youtube.com/watch?v=rva3wRvpS_4 • http://www.youtube.com/watch?v=kYajjGi5-qM Presentation Title 8/17/2013 6

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/17/2013 7

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

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.

Putting it all together Image available at www.mountaingoatsoftware.com/scrum

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

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!

Tools Presentation Title 8/17/2013 13

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

Tools Backlog summary Ready (Multiple Items) Row Labels Count of Category Sum of Estimate dev d Differentiator 5 105 Quality 1 5 Required to do busin 4 18 Scalability 13 169 Usability 36 243 Compliance 1 5 Grand Total 60 545 Presentation Title 8/17/2013 15

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

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

Burn 8/17/2013 18

QA questions • Are our processes adequate and sufficient? – Yes • Is our infrastructure adequate and sufficient? – No, we need sys admin training, an assessment report, and a best practices guide, reliable backup and recovery, and reliable source control for multiple remote developers • Do we have sufficient resources? • No. We need a senior developer at market salary and 2 mid-level developers and AWS consulting. • Can we reliably and repeatedly compile on a development computer and upload executables to AWS dev and production? – Yes. • Is production system safe? – Yes and No. See AWS. • Is the source code safe? – Yes, but it’s a manual process of backups. Need TFS. • Can we perform an emergency update? How much time does it take? – Yes, one hour. • Can we reliably and repeatedly perform regression testing? – Yes, but automated testing will save time. • Is production backed up? Restorable? – Yes, but it’s a manual process. • Do we have a single point of failure in people or technology? – Yes, we have single point of failure at Amazon (recoverable), in the database (recoverable), and in three people (non-recoverable). • Is CSP properly architected? – Align database to business processes. • Can we update the database and execute scripts to reconcile existing database contents with new structure? – Not tested • Are we ready to begin development per product direction? – No, we have to answer yes to above questions first. • Is the database safe from the top n hacking threats? Which ones? – Yes • Are we meeting SLA? Notification of completion? 4-hour response on red tickets? – Not tested 8/17/2013 19

2013-Q2-R3 post mortem (retrospective) • Feeling of lack of control • Slow and erratic cadence • Too many unknowns, untested • Communication is week 8/17/2013 20

2013-Q2-R3 post mortem (retrospective) • One week sprints • Follow the process – Select tasks (MS, KC, SS) – Two notifications – Backup all source, stored proc, etc for QA and production releases – Daily backups – Sprint review, code review, paired review • Alternate focus on releases: foundational, impacting – 2013-Q2-R1, 2013-Q2-R2 infrastructure – 2013-Q2-R3 – database – 2013-Q3-R1 – impact on sales, ops, customers • Focus: – KC on hiring developers and consultant – MS QA – SS develop 8/17/2013 21