invest

Define a clear product vision

Identify product features

Features represent high-level business needs and are at coarse-grained state ( without having enough detail on its implementations). Implementing a product vision starts with identifying features necessary for vision. The success of a product depends on identifying all those product features and its demand to go to market which holds a high ROI. Features are planned across release. So a release plan gives a better understanding of product features over releases.

Write down features using epics

Now it’s imperative to write those high-value product features and plan for its early to market. This smallest unit of product features called as epics. In other words, epics are comparatively bigger stories which enable focusing on adding to product features. These are essentially written in simple languages and need to split further into stories.

Steps in Vision-Theme-Epic-Story-Task

mvp-feature-epic-story1

Pull stories from epics

Stories are the measurable unit of epics which adds up to deliver business values and are considered as the basis of agile development. Stories are potentially shippable work products which integrated with the main product. This provides a way to estimate, develop and test it. Stories enable conversation and provide just enough detail to go ahead at that time.

Validate granularity & Clarity of stories

 Stories should be granular enough which can be completed within  1-2 days of a 2-week sprint. This requires a story should small enough with enough clarity to go ahead. Stories are usually independent in nature to avoid any delay due to dependencies. An effective story accepts INVEST model attributes.

  • I: Independent
  • N: Negotiable
  • V: Valuable
  • E: Estimable
  • S: Small enough
  • T: Testable

Map all stories, Affinity estimation

This method organizes stories in an order of high business value. Large stories or epics are difficult to estimate. So mapping will help the team for an effective estimation, identifying issues and risks. This map usually starts with creating groups and then rearranging stories within the group. All mapped stories are done physically using post-it notes or story cards.

Break stories into tasks

Tasks are a list of works needed to complete a user story.  During this step, a user story is broken down into a highest granular level called as story tasks.

Define the order of task

Contact Us

We're not around right now. But you can send us an email and we'll get back to you, asap.

0

Start typing and press Enter to search