In this article, we will help you to understand the Product Development templates and the menus related to them.

Skip Ahead to:

Overview

Hybrid

Kanban

Scrum

Scrumban

Waterfall

Video Reference

Overview

Template selection allows you to select a suitable template from a set of pre-defined standard templates in different categories. The Product Development category displays a variety of project templates to help you put a clear plan into motion quickly by creating projects tailored to use. You can always modify your project template at the personal level and can convert it to a custom template for other managers to use.

To learn more about other domain templates and related menus, read more.

Product Development templates

Product Development Templates

Hybrid

The Hybrid template allows teams to combine Waterfall and Agile methods, all within one project. You will see a wide set of capabilities.

The template module groups and constituent modules are represented in the following table structure where each module name has a link. Clicking the link will redirect you to the detailed description of the module.

Modules Menus
Plan
Agile Planning
Execute
Manage
Dashboard
Configure

* License-Driven Features

Benefits of using a Hybrid template

  • Use Scrum, Kanban, and Waterfall development template approaches within the same project.
  • For the scope of work that is fixed, build Task Plans using Simple or Advanced Scheduling types that have a linear execution and minimal changes during development.
  • For a scope of work that is flexible, build a backlog, plan time-boxes, and execute using Agile techniques so that value is delivered at regular intervals.
  • Use a variety of Scrum, Kanban, and Waterfall analytics for different types of work that are being executed inside the project.

Card Type List

  • Theme: Track main objectives and help to maintain alignment when you create Epics, Features, and User Stories as child workitems.
  • Epic: Track different goals of the product that need to be fulfilled.
  • Feature: Epics are meant to track specific areas that provide tangible value to the customer.
  • User Story: Provide value to a user that can be delivered in a single sprint.
  • Technical Story: Meant to overcome challenges or to do a technical spike to improve underlying technology.
  • Defects: Also known as bugs that are meant to track errors or flaws in the Product that do not meet the requirements or block the user from using the Product to derive the intended value.
  • User Requirements: Track functional requirements that are elaborated in a document containing purpose, functionality, business rules, impact areas, etc.
  • Change Requests: Track enhancements to the original requirements that are elaborated in a document containing purpose, audience, use cases, etc.
  • Tasks: Track the work that needs to be completed in order to deliver the requirement.
  • Adhoc Work: Track any unplanned work that needs to be done by the team while working on a Release or Sprint that doesn’t fit the intent of a Story Change Request or Defect but needs to be part of the Release or Sprint scope.
  • Action Items: Track any planned work that needs to be done by the team while working on a Release or Sprint that is needed to deliver the Story/ Defect resolution.
  • Issues: Track any problems faced by the end-user to gain value from the product.
  • Risks: Track any possible risks that may threaten the development of the working Product.

Kanban

The Kanban template is based on the Kanban Method. It’s a visual system to manage work and visualize progress. It includes metrics to support continuous improvement.

The template module groups and constituent modules are represented in the following table structure where each module name has a link. Clicking the link will redirect you to the detailed description of the module.

 

Modules Menus
Plan
Agile Planning
Execute
Manage
Dashboard
Configure

* License-Driven Features

Benefits of using the Kanban template

  • Visualize your value stream by configuring the Execution Board with lanes, columns, and sub-columns as per your need.
  • Limit work-in-progress by setting WIP limits against the columns on the Execution Board.
  • Track card progress by the movement of cards from left to right and view the position of cards at a glance using higher zoom levels of the board.
  • Find ways for continuous improvement by using Flow and Cycle Time analytics such as Cumulative Flow Diagrams, Flow Efficiency, Cycle Time Distribution, and many more.

Card Types List

  • Theme: Track main objectives and help to maintain alignment when you create Epics, Features, and User Stories as child workitems.
  • Epic: Track different goals of the product that need to be fulfilled.
  • Feature: Epics are meant to track specific areas that provide tangible value to the customer.
  • User Story: Provide value to a user that can be delivered in a single sprint.
  • Technical Story: Meant to overcome challenges or to do a technical spike to improve underlying technology.
  • Defects: Also known as bugs that are meant to track errors or flaws in the Product that do not meet the requirements or block the user from using the Product to derive the intended value.
  • Adhoc Work: Track any unplanned work that needs to be done by the team while working on a Release or Sprint that doesn’t fit the intent of a Story Change Request or Defect but needs to be part of the Release or Sprint scope.
  • Action Items: Track any planned work that needs to be done by the team while working on a Release or Sprint that is needed to deliver the Story/ Defect resolution.
  • Issues: Track any problems faced by the end-user to gain value from the product.
  • Risks: Track any possible risks that may threaten the development of the working Product.

Scrum

The Scrum plans work in time-boxed sprints and tracks progress with Burndown charts. It includes popular Scrum metrics with Task Boards.

The template module groups and constituent modules are represented in the following table structure where each module name has a link. Clicking the link will redirect you to the detailed description of the module.

 

Modules Menus
Plan
Agile Planning
Execute
Manage
Dashboard
Configure

* License-Driven Features

Benefits of using Scrum template

  • Build and refine your Backlog using popular Agile techniques such as Story Mapping, Relative Sizing, and time-boxing their delivery in Sprints.
  • Boost transparency and the self-organizing principle of teams by tracking work as cards on a common Execution Board and using the Standup Wizard daily.
  • Inspect and adapt regularly using the Burndown Chart, Sprint Velocity, Release Burnup, Value VS Non-Value Added Trend, and many more.
  • Visualize progress in different ways by using the % Progress column on the Execution Board, Timeline View, or multi-dimensional Project Health analytics.

Card Types List

  • Theme: Track main objectives and help to maintain alignment when you create Epics, Features, and User Stories as child workitems.
  • Epic: Track different goals of the product that need to be fulfilled.
  • Feature: Epics are meant to track specific areas that provide tangible value to the customer.
  • User Story: Provide value to a user that can be delivered in a single sprint.
  • Technical Story: Meant to overcome challenges or to do a technical spike to improve underlying technology.
  • Defects: Also known as bugs that are meant to track errors or flaws in the Product that do not meet the requirements or block the user from using the Product to derive the intended value.
  • Adhoc Work: Track any unplanned work that needs to be done by the team while working on a Release or Sprint that doesn’t fit the intent of a Story Change Request or Defect but needs to be part of the Release or Sprint scope.
  • Action Items: Track any planned work that needs to be done by the team while working on a Release or Sprint that is needed to deliver the Story/ Defect resolution.
  • Issues: Track any problems faced by the end-user to gain value from the product.
  • Risks: Track any possible risks that may threaten the development of the working Product.

Scrumban

The Scrumban combines Scrum and Kanban templates. Together, they enable time-boxed Sprints with Kanban’s Lean and flow-based execution model.

The template module groups and constituent modules are represented in the following table structure where each module name has a link. Clicking the link will redirect you to the detailed description of the module.

 

Modules Menus
Plan
Agile Planning
Execute
Manage
Dashboard
Configure

* License-Driven Features

Benefits of using the Scrumban template

  • Provides a structure of Scrum with the flexibility of the Kanban approach to managing your work effectively.
  • Track progress with your team members by using the Standup Wizard and check the overall progress at a glance based on the card’s position on the value stream.
  • Use a combination of Scrum and Lean Analytics to assess progress at a Release, Sprint level, and overall execution using Cycle Time and Flow Analytics.

Card Types List

  • Theme: Track main objectives and help to maintain alignment when you create Epics, Features, and User Stories as child workitems.
  • Epic: Track different goals of the product that need to be fulfilled.
  • Feature: Epics are meant to track specific areas that provide tangible value to the customer.
  • User Story: Provide value to a user that can be delivered in a single sprint.
  • Technical Story: Meant to overcome challenges or to do a technical spike to improve underlying technology.
  • Defects: Also known as bugs that are meant to track errors or flaws in the Product that do not meet the requirements or block the user from using the Product to derive the intended value.
  • Adhoc Work: Track any unplanned work that needs to be done by the team while working on a Release or Sprint that doesn’t fit the intent of a Story Change Request or Defect but needs to be part of the Release or Sprint scope.
  • Action Items: Track any planned work that needs to be done by the team while working on a Release or Sprint that is needed to deliver the Story/ Defect resolution.
  • Issues: Track any problems faced by the end-user to gain value from the product.
  • Risks: Track any possible risks that may threaten the development of the working Product.

Waterfall

The waterfall template allows you to plan, schedule, and eye-sequentially execute work that supports a variety of metrics like EV analysis.

When you create a project with the Waterfall template, the landing page will be Tasks. Learn more about the Tasks here and the default widgets in the Analytics here. The template module groups and constituent modules are represented in the following table structure where each module name has a link. Clicking the link will redirect you to the detailed description of the module.

Modules Menus
Plan
Execute
Manage
Dashboard
Configure
* License-Driven Features

Benefits of using Waterfall Template

  • Visualize your value stream by configuring the Execution Board with lanes, columns, and sub-columns as per your need.
  • Limit work-in-progress by setting WIP limits against the columns on the Execution Board.
  • Track card progress by the movement of cards from left to right and view the position of cards at a glance using higher zoom levels of the board.
  • Find ways for continuous improvement by using Flow and Cycle Time analytics such as Cumulative Flow Diagrams, Flow Efficiency, Cycle Time Distribution, and many more.

Card Types List

  • Theme: Track main objectives and help to maintain alignment when you create Epics, Features, and User Stories as child workitems.
  • Epic: Track different goals of the product that need to be fulfilled.
  • Feature: Epics are meant to track specific areas that provide tangible value to the customer.
  • User Story: Provide value to a user that can be delivered in a single sprint.
  • Technical Story: Meant to overcome challenges or to do a technical spike to improve underlying technology.
  • Defects: Also known as bugs that are meant to track errors or flaws in the Product that do not meet the requirements or block the user from using the Product to derive the intended value.
  • Adhoc Work: Track any unplanned work that needs to be done by the team while working on a Release or Sprint that doesn’t fit the intent of a Story Change Request or Defect but needs to be part of the Release or Sprint scope.
  • Action Items: Track any planned work that needs to be done by the team while working on a Release or Sprint that is needed to deliver the Story/ Defect resolution.
  • Issues: Track any problems faced by the end-user to gain value from the product.
  • Risks: Track any possible risks that may threaten the development of the working Product.

Video Reference

To dive deeper into the topic, we recommend watching the reference video available here.

  • Was this helpful?
  • Yes   No