https://wiki.opensourceecology.org/index.php?action=history&feed=atom&title=XM_Status_BriefXM Status Brief - Revision history2026-04-24T17:27:44ZRevision history for this page on the wikiMediaWiki 1.39.13https://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=59542&oldid=prevMarcin at 20:52, 12 April 20122012-04-12T20:52:26Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 20:52, 12 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet. Status Briefs from all projects should feed automatically into the XM Status Log.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet. Status Briefs from all projects should feed automatically into the XM Status Log<ins style="font-weight: bold; text-decoration: none;">. All the individual project status briefs (50 projects) should be summarized and fed into the single [[Status Brief]] page on the wiki</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58653&oldid=prevMarcin at 21:38, 1 April 20122012-04-01T21:38:15Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:38, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet. Status Briefs from all projects should feed automatically into the <del style="font-weight: bold; text-decoration: none;">[[</del>XM Status Log<del style="font-weight: bold; text-decoration: none;">]]</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet. Status Briefs from all projects should feed automatically into the XM Status Log.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58649&oldid=prevMarcin at 21:27, 1 April 20122012-04-01T21:27:56Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:27, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet. Status Briefs from all projects should feed automatically into the <del style="font-weight: bold; text-decoration: none;">[</del>[[XM Status Log]].</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet. Status Briefs from all projects should feed automatically into the [[XM Status Log]].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58648&oldid=prevMarcin at 21:27, 1 April 20122012-04-01T21:27:48Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:27, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet. Status Briefs from all projects should feed automatically into the [[[XM Status Log]].</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet.</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>'''Additional Information:''' 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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58647&oldid=prevMarcin at 21:25, 1 April 20122012-04-01T21:25:58Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:25, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet.</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">'''About:''' 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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, or in component sheets if noted on the overall Product sheet.</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">'''Additional Information:''' </ins>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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58581&oldid=prevMarcin at 03:07, 1 April 20122012-04-01T03:07:45Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 03:07, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, <del style="font-weight: bold; text-decoration: none;">not </del>in component sheets.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful. The Status brief should be updated in the overall Product sheet, <ins style="font-weight: bold; text-decoration: none;">or </ins>in component sheets <ins style="font-weight: bold; text-decoration: none;">if noted on the overall Product sheet</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58576&oldid=prevMarcin at 02:56, 1 April 20122012-04-01T02:56:36Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:56, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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, needs, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful<ins style="font-weight: bold; text-decoration: none;">. The Status brief should be updated in the overall Product sheet, not in component sheets</ins>.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet. Note that the Control Panel displays both the entire product, and its components. Some of these steps may not apply at the level of the components. Clicking on the component sheets should reveal the Work Product there. Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list can be sorted at a future time. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58575&oldid=prevMarcin at 02:55, 1 April 20122012-04-01T02:55:17Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:55, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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<ins style="font-weight: bold; text-decoration: none;">, needs</ins>, and future directions. This should be documented by the Scrum Master on a daily basis, so a spreadsheet format is useful.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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. <del style="font-weight: bold; text-decoration: none;">More general perspective </del>can be <del style="font-weight: bold; text-decoration: none;">obtained from the overall product sheet</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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<ins style="font-weight: bold; text-decoration: none;">. Note that the Master List of Steps shows all the different steps for a product. More general perspective can be obtained from the overall product sheet</ins>. Note that the Control Panel displays both the entire product, and its <ins style="font-weight: bold; text-decoration: none;">components. Some of these steps may not apply at the level of the </ins>components. Clicking on the component sheets should reveal the Work Product there. <ins style="font-weight: bold; text-decoration: none;">Since any development may be taken at any time in the Scrum methodology, results on the Product and Components sheets should be numbered as in the Master List of Steps. The steps should be numbered and filled in the uppermost rows, regardless of order of completion. This is fine, as the spreadsheet allows sorting by number - so as long the number of the step is written down, the list </ins>can be <ins style="font-weight: bold; text-decoration: none;">sorted at a future time</ins>. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58574&oldid=prevMarcin at 02:47, 1 April 20122012-04-01T02:47:35Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:47, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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 <del style="font-weight: bold; text-decoration: none;">of status should be maintained in the form of a spreadsheet</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">format is useful</ins>.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">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 tej </del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">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.</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[[Category:XM]]</div></td></tr>
</table>Marcinhttps://wiki.opensourceecology.org/index.php?title=XM_Status_Brief&diff=58573&oldid=prevMarcin at 02:39, 1 April 20122012-04-01T02:39:00Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:39, 1 April 2012</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 of status should be maintained in the form of a spreadsheet.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 of status should be maintained in the form of a spreadsheet.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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. Note that the Control Panel displays both the entire product, and its components. Clicking on the <del style="font-weight: bold; text-decoration: none;">components </del>should reveal the Work Product there. More general perspective</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">window</ins>. Note that the Control Panel displays both the entire product, and its components. Clicking on the <ins style="font-weight: bold; text-decoration: none;">component sheets </ins>should reveal the Work Product there. More general perspective <ins style="font-weight: bold; text-decoration: none;">can be obtained from tej </ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">[[Category:XM]]</ins></div></td></tr>
</table>Marcin