Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Standalone project development use case

Log in to subscribe to topics and get notified when content changes.

Standalone project development use case

An example of a standalone project development and delivery model is explained.

In this case, request (demand) for a new product or feature or system is raised. Demand managers capture the requirements in terms of stories. They also capture the other details for the demand such as resources required, cost, risks, and strategic direction. Such demands upon approval are converted into projects. Project managers can choose pure agile or hybrid mode of project execution. In hybrid mode, the initial phases such as planning, and analysis are taken up as waterfall tasks, and then the execution is done as agile phase. The agile phase is assigned to an agile group. The agile group then completes the work by sprint execution.

The following illustration provides a high-level overview of the workflow for executing a standalone project development.
Figure 1. Project based agile development workflow example
Concept picture for Standalone development workflow

How to use Agile Development 2.0 for standalone hybrid project development

Steps to execute a standalone hybrid project:
  1. Create demand: Capture requirements at demand state in terms of user stories. Use Stories related list on demand form to create stories.
  2. Demand to Project conversion: When the demand is converted to a project, the stories in demand move to the project so that the project team (assignment group) can execute them. During the conversion, an Agile phase is also created, and the stories are assigned to the agile phase.
  3. Sprint planning: The agile group members along with project manager, and scrum master perform sprint planning. Navigate to Agile Development > Agile Board > Sprint Planning to plan sprints.