... | ... | @@ -21,7 +21,12 @@ For effective parallel development and delivery of domain DMS, data flow and lay |
|
|
|
|
|
The first priority now is to get the R3 codebase populated (see [Initial Steps](R3Initial%7CR3-Initial-Steps) ) and to get the core changes described under here and to keep the Core stable and reliable for further development and delivery of Extension Projects and Domain Projects.
|
|
|
|
|
|
[Most recent Sprint Planning presentation](uploads/e4ecb9a29f9aeafc63afb63f6379076b/Sprint_Planning.pptx)
|
|
|
[May 15 Sprint Planning presentation](uploads/e4ecb9a29f9aeafc63afb63f6379076b/Sprint_Planning.pptx)
|
|
|
|
|
|
* Supercedes table below
|
|
|
* This is a distillation of what is in the backlog "done" page and better reflects the sequence of delivery (priorities) from a capability and continuous delivery perspective than the duration of development.
|
|
|
* Some of the longer duration lines are long because defining what is important often takes more time than defining how to do it. Right now my confidence in Milestone 1 is P80, Milestone 2 is P50, and nothing beyond that has had any analysis - Stephen
|
|
|
|
|
|
|
|
|
> Draft timeline is detailed below:
|
|
|
<details>
|
... | ... | |