Detailed Planning

Build User Stories

Define Acceptance criteria

Generate Product Backlog

Generate Release Plan

Build and Qualify User Stories

In this stage, the Project team decomposes the Job Requirements that were published by the Customer, builds Epics (or Scenarios) and User Stories (Tasks; Also called Technically Implementable Requirements).

The Project team then qualifies each User Story based on a variety of attributes such as: Criticality of the requirement, Urgency of deployment, Usage levels, Complexity, Dependencies, etc.

The User Stories thus developed will be used to generate the Product Backlog & Contract Release Plan, downstream in the Contract lifecycle. These artifacts will form the detailed basis of project scope going forward.

Define User Story Acceptance criteria

In this stage, the Project team will clearly document the Acceptance criteria for each defined User Story.

The basis for developing the User Story Acceptance criteria for a User Story shall be: The corresponding Job requirement, the Acceptance criteria for that Job Requirement, and the scope of the specified User Story.

This would help to ensure that the Customer team & Service Delivery team are on the same page vis-a-vis what is expected from each User Story, and under what conditions the User Story deliverables would be accepted by the Customer team.

Generate Product Backlog

After the User Stories have been defined & the corresponding User Story Acceptance criteria have been developed, the Project Manager can generate the Product Backlog from GigsBoard.

The Product Backlog is a compilation of all User Stories in a Project, which have been sorted in a pre-defined order based on our built-in algorithm using factors such as the criticality, complexity, etc.

Generate Contract Release Plan

After the Product Backlog has been generated & the Project Manager can declare the average productivity rate of the project team, and then generate the Contract Release Plan for the project.

The Contract Release Plan is a compilation of all User Stories in a Project, which have been assigned to the various Project team members, and allocated to different Contract Sprints/ Cycles, using our built-in Release Plan generation algorithm.

The Contract Release Plan shall serve as a roadmap for the entire project execution, indicating which functionalities will be built and delivered by which team member at what point of time in the project lifecycle, and serves as the basis for the Contract execution going forward.