|
Introduction
Welcome to the CORE Infrastructure Scope Planning Index Page. The intent of this page is to provide a single entry to the product release planning process for CORE infrastructure products. This gives end users, stakeholders, developers, analysts, product managers, and project managers a central place on the Wiki to find current and future planning documentation for in-scope features for all CORE products.
The scope document for each product release functions as the central place for an official sign off on all features being requested by users and stakeholders. The Construction Phase for a feature will not begin until such time as official sign-off is in place from the identified end user or stakeholder.
CORE Scope Documents
caCORE Scope Documents
caDSR Scope Documents
Semantic Tools and Projects Scope Documents
EVS Scope Documents
Time Box Strategy & Approach
Please refer to the Glossary and Terms Used page for explanation of terminology used.
The figure below provides a high level overview of the time boxed approach. Essentially each iteration (a piece of functional code pushed to Stage, but not Production) is a 'time bounded' effort to complete a small amount of business functionality, decomposed into requirements that get implemented.
- New requirements can be added at any time before the requirements cut off date for an iteration, or as business needs change.
- Each requirement change presents an opportunity to re-assess and change priorities. Thus when requirements become obsolete or are devalued, they are dropped from the scope of the current iteration.
- The CORE workspace will have a Change Control Support Team (CCS) that will approve or reject each change request for features with cross product line impact based on as assessment of the impact the change request will have on the overall iteration timeline to deliver a particular solution.
Sample Time Box Iteration
The diagram below depicts a typical timeboxed approach to agile development. The length of the iteration itself can vary, However, there are strict dates which, once established, must be adhered to in order to achieve the overall release schedule.
|