Feature Development Process

Get Started. It's Free
or sign up with your email address
Rocket clouds
Feature Development Process by Mind Map: Feature Development Process

1. Story Grooming and Planning

1.1. Clarify requirements

1.1.1. How?

1.1.1.1. Front-End (UI, UX)

1.1.1.2. Back-End (APIs)

1.1.1.3. Dependencies

1.1.1.4. Design and engineering drive this discussion

1.1.2. When?

1.1.2.1. Prioritize

1.1.2.2. Assign story points

1.1.2.2.1. Delivery

1.2. People

1.2.1. Owner: Delivery (Design + Engineering)

1.2.2. Moderator: BA

1.2.3. CC: PO, Tech Team, BMO

1.3. Up to 3 sessions, 15 minutes per story

2. Feature Creation

2.1. Document elements of feature

2.1.1. Why?

2.1.1.1. Business Value Justification

2.1.2. What?

2.1.2.1. Workflow

2.1.2.2. User Permissions / Business Logic

2.1.3. Initial BMO Sign-off

2.2. Create stories with hierarchy

2.3. People

2.3.1. Owner: BA

2.3.2. CC: PO, BMO

2.4. Toolset

2.4.1. VersionOne

2.5. Up to 8 hours

3. Delivery

4. Need Emerges

4.1. Hazy, continuous

4.1.1. Ideation

4.1.1.1. Gather Ideas

4.1.1.1.1. Brainstorm

4.1.1.2. People

4.1.1.2.1. Owner: PO

4.1.1.2.2. CC: BA, Delivery (Design + Engineering)

4.1.1.3. Up to 3 sessions 3 hours each

4.2. Concrete, in response to a specific event

4.2.1. Requirement Gathering

4.2.1.1. Gather requirements from business

4.2.1.1.1. Align with overall product strategy

4.2.1.2. People

4.2.1.2.1. Owner: BA

4.2.1.2.2. CC: PO, BMO (SME)

4.2.1.3. Up to 3 sessions 1 hour each

4.3. Toolset

4.3.1. VersionOne

4.3.2. Design

4.3.2.1. Dirty Wireframes

4.3.2.2. Paper Prototypes

4.3.2.3. Whiteboard Sketches

4.3.3. Collaboration tools

4.3.4. Technical POC

4.3.5. Customer / market research

4.3.6. Stakeholder interview