|
Method Fragment: Daily Meeting |
|
|
|
|
|
|
|
|
|
|
|
|
Originating Method: Scrum, XP |
|
|
|
|
|
|
|
|
|
|
|
Contributes to |
|
|
|
|
Major Softgoal |
sub softgoal |
Cont.
Value from Fragment |
Study |
Situation |
|
|
|
|
Enhanced Communication |
|
++ |
|
|
|
|
|
|
Improved
awareness (of what others are doing, better information passing ) |
++ |
|
|
|
|
|
|
|
- |
|
Large
projects, as they may need extensive number of meetings |
|
|
|
|
Real-time knowledge transfer |
+ |
|
|
|
|
|
|
- |
|
Distributed
Development: use of email and wiki pages for comm. |
|
|
|
|
Enhanced
Communication with business people / project leader |
++ |
|
Existence
of multi-level Scrum in case of many scrum teams |
|
|
|
|
Better
understanding of customer needs (thus prevention of rework or elimination of
redundant tasks) |
+ |
|
|
|
|
|
|
Improved Effectiveness |
Elimination
of redundant tasks |
++ |
|
|
|
|
|
|
Earlier
Detection of Development issues |
++ |
|
|
|
|
|
|
Enhanced Collaboration and Coordination |
|
++ |
|
|
|
|
|
|
|
- |
|
Existence
of non-agile teams; synchronization problem |
|
|
|
|
|
- |
|
Bounded
Collaboration - Team members (including product owner) do not collaborate
together, except during formal daily meeting |
|
|
|
|
|
- |
|
Balkanization
- Existence of multiple teams, each team having a good local collaboration,
but poor collaboration with others |
|
|
|
|
Elimination
of redundant tasks |
++ |
|
|
|
|
|
|
Earlier
Detection of Development issues |
++ |
|
|
|
|
|
|
Improved Job Satisfaction |
|
++ |
|
|
|
|
|
|
|
-- |
|
sense
of micromanagement, when developers perceive that they are supposed to
present progress report daily to their managers. |
|
|
|
|
Improved
sense of being visible (outcome of each team members will become visible in
daily meetings) |
++ |
|
|
|
|
|
|
self-organizing
capability of teams gets improved (thus reduced dependency to scrum master) |
|
++ |
|
Distributed
Development: meeting via web-conferencing, and communicating through Twiki
(an off-shoot to wiki, is a collaboration tool used for multi-site
development which can store information in the form of web pages and
attachments) |
|
|
|
|
|
Enhanced
self-resource management |
++ |
|
|
|
|
|
|
|
Enhanced
self-time management |
++ |
|
|
|
|
|
|
Higher
Commitment of team members (due to daily face-to-face meeting) |
|
++ |
|
Distributed
Development: meeting via web-conferencing, and communicating through Twiki |
|
|
|
|
Better focus of
team on its tasks (as team obstacles will be brought up during meetings, and
this is the responsibility of scrum master to resolve them) |
|
++ |
|
|
|
|
|
|
|
preventing
teams from focusing on items with lower priority |
++ |
|
new
team members with lower experience |
|
|
|
|
Enhanced Project
Visibility |
|
++ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
