| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-zqsjK1qfcSGuOsNO5K7UhA" |
| name="new_guideline,_251UMCmREdyy6Oss2-0s1g" guid="-zqsjK1qfcSGuOsNO5K7UhA" changeDate="2008-07-11T09:35:04.705-0700" |
| version="7.2.0"> |
| <mainDescription><h3>
 |
| Practices
 |
| </h3>
 |
| <p> Daily meetings are also known as<i> scrum</i> meetings <a class="elementLinkWithUserText" href="./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#SCH04" guid="_JlTPUM6aEdyuBO4ZIzcyig">[SCH04]</a>. 
 |
| These meetings help check the&nbsp;heartbeat of the project. All team members 
 |
| are required to attend. The meetings are held in the same place at the same 
 |
| time every work day and should&nbsp;not last for more than 15 minutes. Usually, 
 |
| teams conduct the meetings with everyone standing up to keep them short (thus 
 |
| some call them &quot;standup&quot; meetings). Anyone who is directly involved&nbsp;can 
 |
| also attend the meeting as an observer, but care should be taken because too 
 |
| many people in the meeting may cause disruption or cause people to be uncomfortable 
 |
| in sharing information. Typical daily meetings should have 10 people at most. 
 |
| </p>
 |
| During the daily meeting, each team member updates peers with answers to the following 
 |
| three questions <a class="elementLinkWithUserText" href="./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#SCH04" guid="_JlTPUM6aEdyuBO4ZIzcyig">[SCH04]</a>: 
 |
| <ol>
 |
| 
 |
| <li> What did I do yesterday?</li>
 |
| <li>
 |
| What will I do today?
 |
| </li>
 |
| <li>
 |
| What is impeding my work?
 |
| </li>
 |
| </ol>
 |
| <p> These three questions have a specific purpose [<a class="elementLinkWithUserText" href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html#SUT06" guid="_9ToeIB83Edqsvps02rpOOg">SUT06</a>]: 
 |
| </p>
 |
| <ul>
 |
| 
 |
| <li> The first question tests the focus of the team. Anything done that was 
 |
| not work planned for the iteration is questioned. </li>
 |
| 
 |
| <li> Answering the second question revises project strategy daily by reorienting 
 |
| the team according to dependency changes that were revealed by the response 
 |
| to the previous question. </li>
 |
| 
 |
| <li> The third question will create issues that may result in new tasks in the 
 |
| Work Items list. The most important effect of this question is to create a 
 |
| list of issues that are assigned to the team or to managers.&nbsp;The team 
 |
| should expect management to help eliminate bottlenecks.&nbsp; </li>
 |
| </ul>
 |
| <p> These are the minimum number of questions that satisfy the goals of daily 
 |
| meetings. Experienced practitioners tend to add an additional question for improving 
 |
| collaboration among team members: "What have I learned or decided that is of 
 |
| relevance to the team?" [<a class="elementLinkWithUserText" href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html#LAR03" guid="_9ToeIB83Edqsvps02rpOOg">LAR03</a>].&nbsp;"What 
 |
| might help or hinder others in meeting their commitments?" [<a class="elementLinkWithUserText" href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html#YIP" guid="_9ToeIB83Edqsvps02rpOOg">YIP</a>]. 
 |
| Other topics of discussion (design discussions, chat, and such) should be deferred 
 |
| until after the meeting. </p>
 |
| <h4>
 |
| Value
 |
| </h4>
 |
| <p> For self-directed teams, the daily meeting is a mechanism to quickly inform 
 |
| the team about the state of the project and people. It supports openness and 
 |
| enables resolution of dependencies and conflicts in real time. It builds a team; 
 |
| effective teams are built by regularly communicating, sharing commitments, and 
 |
| helping each other. [<a class="elementLinkWithUserText" href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html#LAR03" guid="_9ToeIB83Edqsvps02rpOOg">LAR03</a>]</p>
 |
| <h3>
 |
| What a daily meeting is not </h3>
 |
| <p>
 |
| The daily meeting is not a status update meeting in which the project manager is collecting information about who is
 |
| behind schedule. Rather, it is a meeting in which team members make commitments to each other.<br />
 |
| <br />
 |
| Neither is it a problem-solving nor issue resolution meeting. Issues that are 
 |
| raised are registered and usually dealt with by the relevant team members immediately 
 |
| afterward. It is the project manager's responsibility to resolve them as quickly 
 |
| as possible or to make sure that someone on the team does. </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
