-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
3
-
False
-
False
-
Undefined
-
-
NetObserv - Sprint 203, NetObserv - Sprint 204, NetObserv - Sprint 205, NetObserv - Sprint 206, NetObserv - Sprint 207, NetObserv - Sprint 208, NetObserv - Sprint 209, NetObserv - Sprint 210, NetObserv - Sprint 211
Description
In 4.9 one of our key deliverables is that we hit the ground running in 4.10 with a vision that can lead us through the next few releases. To that end what I think needs to happen is:
1. Tightening of the market problem outlined by Russell and Marc
2. A definition of the feature set that solves that market problem
3. A prioritization of features for the team to tackle in order to realize the feature set
4. Leading us to a task break down of whatever set of features Joel and the team thinks they can work on in the remaining 4.9 and R&D for 4.10 features
This task is to work with engineering and business stakeholders in order to define the items above.
Acceptance Criteria
1. Market Problem is documented in Jira
2. We have one or more features created in Jira
3. We have epics tied to features in Jira
Out of Scope
It is quite likely that most of our initial epics will be R&D in order to provide enhancement proposals or other task break downs. That is acceptable. This card's scope is limited to the initial road map definition.