Background/Goal
As part of T319686: Define technical requirements for remaining scope of AQS 2.0, we need to document the remaining scope of work to get AQS 2.0 to a public launch so we can plan resourcing and capacity accordingly and set realistic expectations and goals
User stories
- As an AQS 2.0 working group member, I need to clearly understand the remaining scope of work, so I can gauge where we are in the process and see how close we are to completion.
- As an end user of AQS 2.0, I need to be able to follow AQS 2.0 progress and definition, so I can help ensure it will meet my needs and can plan ahead for its estimated completion.
- As a stakeholder, I need to have accurate progress updates, so I understand the health of the initiative.
Considerations
- What capabilities are critical vs nice-to-have?
- What capabilities have the biggest impact?
- What capabilities have the most dependencies?
- Are there patterns in the processes we can use to facilitate the work? -Are there workflow improvements we can make?
- What can we learn in this process that we can apply to future API Guidelines?
Tasks
- Bucket work into phases
- Bucket work into milestones
- Break milestones into epics
- Break epics into stories
- Break stories into story points
- Label known status
- Assign level of complexity
- Collate or Create phab tasks to correspond
- Label phab ticket assignment, if known
Acceptance criteria
- Impact can be delivered incrementally, what is currently known and unknown is captured
- Done is clearly defined to the best of our current limits of knowledge
- We she a clear path ahead and can effectively use this to plan resourcing accordingly
links
AQS 2.0 Work breakdown: Milestones, Epics & Stories
AQS 2.0 Product Requirements Document