Risks for Sprint 3 - Risks and Plans
Risk 1: Integration points for Workbench, SPS, ERS and Reactions not identified in Sprint 3 planning could setback completion of working prototype.
Plan: A goal of our in-person sprint on 7/26 is to discuss all integration points to ensure all have been planned for and tasked appropriately for Sprint 3. We will review all the module integration points for workflow (jec006 and fmitchell), front end integrations (jec006), some refactoring of the framework specifically reactions (e2thex) and cleaning up collections (indytechcook).
Risk 2: Work/hours allocation and leveling out the work appropriately and efficiently to achieve the prototype on-time.
Plan: Sprint 3 tickets will continue to be organized and distributed along existing components. However, in order to level off work and distribute evenly against remaining efforts, developers ticket queues will begin to crossover into other components that their own component work was naturally converging with. This creates continuity while maintaining velocity to reach the goal of a working prototype.
Risk 3: A continuing risk is the weekly hours surplus. While it’s okay to come in under estimate we have been significantly under the total estimated hours each week of the project.
Plan: We have plans to increase resourcing in Sprint 3. We will be bringing on additional resources for UX and QA in the middle and end of Sprint 3. While it’s clear the project has thus far been running an hours surplus, this will likely not continue at the level seen currently as we maintain project velocity and add additional resources.
Risk 4: Does the solution we’re crafting meet expectations and real needs for content staging?
Plan: We will conduct demos of current work on staging for LSD members and create avenues for collecting feedback on how the solution in its early stages are aligning with needs. Also we will solicit feedback and involvement on Drupal.org.
QA and documentation will overlap with our efforts to finish a working prototype by August 12th.
On August 1st we will have a critical status check-in. We'll have a rough QA plan created and to be finalized by August 9th. We will create a checklist to review and assure all deliverables are on target.