Friday, June 2, 2017

The Watersports Method of Software Delivery

The Watersports Method of Software Delivery

Step 1

Task: Interactive workshop to build out 90% of the client-side functionality and design it in HTML5 using placeholder images/text so that it looks and works to a consensus agreement of the requirements. Programming to be done in real-time as much as possible. For more complex UI tasks an overnight deliverable from DevOps.
Participants:  DevOps, Customer
Time: Approximately 1 week for each 5 screens
Output: Working mock-up of the client-side UX published to a secured/accessible website for all current or future stakeholders

Step 2

Tasks: Reach a consensus on the frameworks and libraries to be used & build a POC of 3 screens based on the consensus
Particpants: DevOps
Time: Approximately 2 weeks
Output: End-to-end design POC of the code and a consensus on how to build the application

Step 3

Task: Assign coding tasks
Particpants: DevOps
Time: 2 days
Output: Do coding assignments and a reach a consensus on who will do what and how long it will take for the go-live (give or take 4 weeks)

Step 4

Tasks: Provide automated tests of all code in green
Participants: DevOps
Time: As long as needed to pass unit tests
Output: Automated Tests at 95%

Step 5

Tasks: QA and/or UAT validation that everything is working per the design. Debug & remediate as needed
Participants: DevOps, Customer
Time: As long as needed for the customers to be happy
Output: Formal sign-off to DevOps from customers via email or IM

Step 6

Tasks: Release to production and validate
Participants: DevOps, Customer
Time: Agreed upon timeline for communications and prod release
Output: Formal sign-off via email that the production release is to spec



No comments:

Post a Comment