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

▶
agile methodology
SMART_READER_LITE
LIVE PREVIEW

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

Feb 17, 2024 9 likes •295 views

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

slide-1
SLIDE 1

Agile Methodology

Kaushik Chokshi CTO

slide-2
SLIDE 2

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

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

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

slide-5
SLIDE 5

Metrics

Presentation Title

8/17/2013 5

Estimate Actual comment Round 1 Round 2 Round 3 Round 4 Round 5

slide-6
SLIDE 6
  • http://www.youtube.com/watch?v=rva3wRvpS_4
  • http://www.youtube.com/watch?v=kYajjGi5-qM

Presentation Title

8/17/2013 6

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

slide-8
SLIDE 8

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

slide-9
SLIDE 9
  • 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.

Scrum in 100 words

slide-10
SLIDE 10

Putting it all together

Image available at www.mountaingoatsoftware.com/scrum

slide-11
SLIDE 11

Scrum framework

  • Product owner
  • ScrumMaster
  • Team

Roles

  • Sprint planning
  • Sprint review
  • Sprint retrospective
  • Daily stand ups
  • Daily scrum meeting

Ceremonies

  • Product backlog
  • Sprint backlog
  • Burndown charts

Artifacts

slide-12
SLIDE 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!
slide-13
SLIDE 13

Tools

Presentation Title

8/17/2013 13

slide-14
SLIDE 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

  • ff 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 Email scheduler Infrastru cture Provide service (in CSP or SharePoint or similar) to send scheduled, templated emails to customers for onboarding, equipment maintenance schedule, reports, and other processes Usability 10 4 CSP00005 no Digital Signature CSP Faciliate the process of capturing signatures in the field for deliveries and pickups Usability 15 4 yes CSP00006 no webmethods API CSP provide open API and webmethods so that other applications can effectively use the entire

  • perational flow of CohealoShare

programmatically Scalability 20 6 CSP00007 yes Improve Support screen; integrate with support systems 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/17/2013 14

slide-15
SLIDE 15

Tools

Backlog summary

Presentation Title

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

slide-16
SLIDE 16

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

slide-17
SLIDE 17

2013-Q3-R1 status

8/17/2013 17 Priority Title Owner Estimate Done To Do Done/Estimate Done / (To Do + Done) Days Days Elapsed Days Remaining Days Burned Relative Allocation Comment 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 10 1 Assess and document AWS set up KC 10 1 10 1 Deploy 2013-Q3-R1 KC 1 1 1 Compatible with IE 8 MS 5 2 5 2 Improve errors SS 5 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 5 3 Establish source control SS 5 5 3 Automated testing tools KC 10 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% Do general unplanned KC 2013-Q3-R1 Other Activity KC 8 14 9 39% PTO KC 4 11 4 Training MS 3 1 Do admin KC 4 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

slide-18
SLIDE 18

Burn

8/17/2013 18

slide-19
SLIDE 19

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

slide-20
SLIDE 20

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

slide-21
SLIDE 21

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

slide-22
SLIDE 22

Allocation Trend over releases

8/17/2013 22 Allocation Trend over Releases 5/20/2013 Release Calendar days Development Activity Maintenance Activity QA Activity Unplanned Activity Other Activity Open Tickets 2013-Q2-R1 30 94% 0% 4% 0% 3% 4 2013-Q2-R2 14 82% 0% 18% 0% 0% 5 2013-Q2-R3 (to date) 39 72% 0% 0% 0% 28% 5

slide-23
SLIDE 23

Backlog summary

8/17/2013 23 Projected Allocation for backlog 5/20/2013 Projects Benefit To Do Comment Development (Backlog items) per item 545 50% Maintenance Required to do business 218 20% QA Required to do business 218 20% 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

slide-24
SLIDE 24

Completed / Benefits Tracking

8/17/2013 24 Ready done Proposed Release (Multiple Items) Vertiglo Row Labels Count of Category Sum of Projected $ Benefit Sum of Other costs Sum of Actual dev days Sum of Actual $ benefit Quality 1 20 Required to do busin 3 1055000 50000 376 1055000 Grand Total 4 1055000 50000 396 1055000 Ready done Proposed Release 2013-Q2-R1 Row Labels Count of Category Sum of Projected $ Benefit Sum of Other costs Sum of Actual dev days Sum of Actual $ benefit Differentiator 1 4 Required to do busin 1 9 Scalability 3 25 Grand Total 5 38 Ready done Proposed Release 2013-Q2-R2 Row Labels Count of Category Sum of Projected $ Benefit Sum of Other costs Sum of Actual dev days Sum of Actual $ benefit Quality 1 7 Required to do busin 1 7 Grand Total 2 14 Ready done Proposed Release 2013-Q2-R3 Row Labels Count of Category Sum of Projected $ Benefit Sum of Other costs Sum of Actual dev days Sum of Actual $ benefit Grand Total

slide-25
SLIDE 25

Yodiz

8/17/2013 25

slide-26
SLIDE 26

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

  • ffering.

Acceptance criteria:

Presentation Title

8/17/2013 26

slide-27
SLIDE 27

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

slide-28
SLIDE 28

8/17/2013 28

Ask the team!