XM Status Brief: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
A Status Brief should provide a quick summary of the existing state of the project. A Status Brief shall update the latest developments, issues encountered, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet | A Status Brief should provide a quick summary of the existing state of the project. A Status Brief shall update the latest developments, issues encountered, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. | ||
In addition to the Status Brief - one should in general be able to assess the general state of the project by viewing all the Work Product for the overall product sheet in the Control Panel window. Note that the Control Panel displays both the entire product, and its components. Clicking on the component sheets should reveal the Work Product there. More general perspective can be obtained from the overall product sheet. | |||
[[Category:XM]] | [[Category:XM]] |
Revision as of 02:47, 1 April 2012
A Status Brief should provide a quick summary of the existing state of the project. A Status Brief shall update the latest developments, issues encountered, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful.
In addition to the Status Brief - one should in general be able to assess the general state of the project by viewing all the Work Product for the overall product sheet in the Control Panel window. Note that the Control Panel displays both the entire product, and its components. Clicking on the component sheets should reveal the Work Product there. More general perspective can be obtained from the overall product sheet.