Feature Development Process

马上开始. 它是免费的哦
注册 使用您的电邮地址
Feature Development Process 作者: Mind Map: Feature Development Process

1. Need Emerges

1.1. Hazy, continuous

1.1.1. Ideation

1.1.1.1. Gather Ideas

1.1.1.1.1. Brainstorm

1.1.1.2. People

1.1.1.2.1. Owner: PO

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

1.1.1.3. Up to 3 sessions 3 hours each

1.2. Concrete, in response to a specific event

1.2.1. Requirement Gathering

1.2.1.1. Gather requirements from business

1.2.1.1.1. Align with overall product strategy

1.2.1.2. People

1.2.1.2.1. Owner: BA

1.2.1.2.2. CC: PO, BMO (SME)

1.2.1.3. Up to 3 sessions 1 hour each

1.3. Toolset

1.3.1. VersionOne

1.3.2. Design

1.3.2.1. Dirty Wireframes

1.3.2.2. Paper Prototypes

1.3.2.3. Whiteboard Sketches

1.3.3. Collaboration tools

1.3.4. Technical POC

1.3.5. Customer / market research

1.3.6. Stakeholder interview

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. Story Grooming and Planning

3.1. Clarify requirements

3.1.1. How?

3.1.1.1. Front-End (UI, UX)

3.1.1.2. Back-End (APIs)

3.1.1.3. Dependencies

3.1.1.4. Design and engineering drive this discussion

3.1.2. When?

3.1.2.1. Prioritize

3.1.2.2. Assign story points

3.1.2.2.1. Delivery

3.2. People

3.2.1. Owner: Delivery (Design + Engineering)

3.2.2. Moderator: BA

3.2.3. CC: PO, Tech Team, BMO

3.3. Up to 3 sessions, 15 minutes per story

4. Delivery