canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,922
edits
Mobile/Projects/Kinderfox/Status/22-Jul-2015: Difference between revisions
Jump to navigation
Jump to search
Mobile/Projects/Kinderfox/Status/22-Jul-2015 (view source)
Revision as of 18:55, 24 July 2015
, 24 July 2015→Exec Summary/Hot Topics
| Line 24: | Line 24: | ||
<!--Should explain WHY for the health/status reported above. Items covered here may be covered in more detail further down in the report. If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.--> | <!--Should explain WHY for the health/status reported above. Items covered here may be covered in more detail further down in the report. If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.--> | ||
* A fixed backlog has been created for the V1 release, and sizing estimates applied. | * A fixed backlog has been created for the V1 release, and sizing estimates applied. | ||
* Approximately 40% of the scoped work is assigned and in progress, while 57% is not yet started. | * Approximately 40% of the scoped work is assigned and in progress, while 57% is not yet started. | ||
* V1 scope was defined to produce a minimum viable product. Stance from Product Management at kick-off: If any features are determined to not be possible for the 42 release, this means the V1 as a whole is not viable for 42. Is this statement still true? If not, what can be removed. If so, do we slip to 43 delivery? To be discussed at Tuesday AM meeting with Product Management. | |||
== Risks & Issues == | == Risks & Issues == | ||