With new value-driven planning, Copado aligns IT with corporate strategy. Copado now supports application and feature based planning, as well as the ability to prioritize projects using any objectives and prioritize features by value and impact.
In Agile & Scrum, features can be described as a large piece of work that delivers some type of business value. Features represent a single unit of value to users. Features are often made up of smaller units of functionality that are represented by user stories. Features are typically managed by product managers, business analysts, customers, or program managers. Features should include the following information: estimated business value, complexity, thorough description of what the feature is and acceptance criteria. Once a feature is defined, it should be broken down into smaller user stories.
Features vs. Epics
Epics typically define the details of an MVP (Minimum Viable Product) and have a limited scope which could span across multiple sprints but are confined to a single release. Epics have no defined start or end date but do have defined scope. Epics can be written as larger user stories and should include the Who, What , and Why. Features are much smaller than epics and can live forever as features may evolve with the product’s lifecycle. Features capture the business value and impact. Features should be developed within a single release, but can live beyond releases and sprints.
Copado Feature Object
In Copado, the Feature object enables you to store relevant information about your features and link them to sub-applications and applications.
Let’s take a look at the Feature record page.
The Feature record displays a path at the top of the page that shows the different phases your feature will go through as part of the software development lifecycle This allows you to quickly see what the current status of a feature is:
In the Information section you can find useful information about a feature such as the application it belongs to or the related epic. The Status field helps you define the current stage of your feature. The available options in this picklist are the the following:
The path wizard is based on the status values.
Copado enables you to utilize the Feature object to do value-based planning. By tracking the complexity, estimated value, and value type of your features, you are equipped with enough information to truly prioritize your features based on all of these factors. Estimated value and value type may impact your prioritization of the feature. Utilize standard list views with in-line editing capabilities to prioritize your features!
The Priority field allows you to determine the business priority. The lower the number, the higher the priority. Estimated Value enables you to track the estimated value for your feature in the currency of your choice. In the Value Type field you can specify whether the feature is Time Savings or New Revenue. In the Complexity and # Users fields you can define the level of difficulty the feature has and the number of users your feature is being built for. This can help assess impact and change management for the release of the feature.
The description of the feature should include the definition of the acceptance criteria for your feature. This should also include any functional specifications, images of the design, and include details about the business value. The technical assumptions should include information about the technical design of the feature. This may indicate whether the feature will utilize declarative functionality or code. It should highlight any integration assumptions or other systems that may be involved in the development of the feature.
In the Owners section you can see who the product owner and the architect of the feature are.
The Feature record also includes a User Stories related list, where you can see the related user stories linked: