-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathrisesprint2-040111.html
115 lines (91 loc) · 5.47 KB
/
risesprint2-040111.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="prev" href="http://opl-management.rit.edu/rise/node/507">
<link rel="up" href="http://opl-management.rit.edu/rise/node/506">
<link rel="next" href="http://opl-management.rit.edu/rise/node/681">
<link rel="canonical" href="http://opl-management.rit.edu/rise/node/571">
<link rel="shortcut icon" href="http://opl-management.rit.edu/profiles/openatrium/themes/ginkgo/favicon.ico" type="image/x-icon">
<link type="text/css" rel="stylesheet" media="print" href="risesprint2-040111_files/reset.css">
<link type="text/css" rel="stylesheet" media="print" href="risesprint2-040111_files/base.css">
<link type="text/css" rel="stylesheet" media="print" href="risesprint2-040111_files/print.css">
<link type="text/css" rel="stylesheet" media="print" href="risesprint2-040111_files/print-custom.css">
<link type="text/css" rel="stylesheet" media="all" href="risesprint2-040111_files/reset.css">
<link type="text/css" rel="stylesheet" media="all" href="risesprint2-040111_files/base.css">
<link type="text/css" rel="stylesheet" media="all" href="risesprint2-040111_files/print.css">
<link type="text/css" rel="stylesheet" media="all" href="risesprint2-040111_files/print-custom.css">
<title>Sprint 2 Retrospective (2011-04-01) | OPL Open Atrium</title>
</head><body class="print rubik admin-static page">
<div class="limiter clear-block">
<div id="content" class="clear-block">
<div class="print-header">
<h1 class="site-name">OPL Open Atrium</h1>
</div>
<div id="node-571" class="node node-book clear-block node-page">
<div class="node-submitted clear-block">
<div class="picture">
<a href="http://opl-management.rit.edu/rise/user/14" title="View user profile."><img src="risesprint2-040111_files/picture-14.jpg" alt="John Karahalis's picture" title="View user profile." class="imagecache imagecache-user-s" height="30" width="30"></a></div>
<div class="byline"><a href="http://opl-management.rit.edu/rise/user/14" class="username" title="View user profile.">John Karahalis</a></div><div class="date">1:48pm Mon Apr 4</div> </div>
<h2 class="node-title">
<a href="http://opl-management.rit.edu/rise/node/571">Sprint 2 Retrospective (2011-04-01)</a>
</h2>
<div class="node-content clear-block prose">
<div id="diff-inline-571"><h2>What worked well?</h2>
<ul>
<li>Riordan: "Atrium is a godsend!" It is overwhelming (too many emails), but having an "oepn record of everything" is great.</li>
<li>Me: It is a lot to worry about, though, so I think I will ask people to be more concise.</li>
<li>Riordan: Yes.</li>
<li>Ben: When we close a ticket, it would be nice to have an executive summary.</li>
<li>Riordan: Yes, I agree. I think it should be at the bottom of the thread with the comment that closes the ticket.</li>
</ul>
<h2>What could we do better?</h2>
<ul>
<li>Seppi: A quick Mercurial overview would be helpful. I wasn't familiar with addremove, the [decentralized] workflow, etc.</li>
<li>Riordan: Yes, that sounds like a good idea. A quick orientation (5 or 10 minutes) is probably all we need.</li>
<li>Seppi: It might also be good to give a live demo. This week, I asked
about something and you explained how everything worked from your
perspective. What you do isn't important to me, I need to know what I
should do.</li>
</ul>
<h2>Do we want to move to 1-week Sprints?</h2>
<ul>
<li>Riordan: Yes.</li>
</ul>
<h2>How long should the Sprint Planning Meetings last?</h2>
<ul>
<li>Riordan: About 1:00 to 1:15.</li>
</ul>
<h2>Should we decide specific issues (like theme) in smaller meetings rather than trying to decide these things in the big meeting?</h2>
<ul>
<li>Riordan: Yes.</li>
</ul>
<h2>What do we want to do in the big meeting, and what do we want to do in the smaller meetings?</h2>
<ul>
<li>Riordan:
<ul>
<li>In the big meeting, we should talk about the "what" and the "who",
decide what a task needs "To be done...", and decide what smaller groups
should meet.</li>
<li>In the smaller meetings, we will talk about how we will do those
things -- what modules will we use, what the interface will look like,
etc.</li>
</ul></li>
</ul>
<h2>Is there any lack of clarity on the definition of "done"? Is there
something I should be doing better? Am I doing something wrong?</h2>
<ul>
<li>Riordan: We didn't do enough to make it clear what "done" meant early on. The team needs some coaching on what "done" means.</li>
<li>Put a boilerplate in the "To be done..." section of the Atrium
tickets that says something like "Must be committed and shared with the
group."</li>
</ul></div> </div>
<div class="node-links clear-block"><ul class="links inline"><li class="book_add_child first"><a href="http://opl-management.rit.edu/rise/node/add/book?parent=631">Add child page</a></li>
<li class="print active"><a href="http://opl-management.rit.edu/rise/node/571?print" class="active">Print</a></li>
<li class="print_recurse last active"><a href="http://opl-management.rit.edu/rise/node/571?print&book_recurse" class="active">Print entire section</a></li>
</ul></div>
</div>
</div>
<div id="footer" class="clear-block">© 2009 <a href="http://www.developmentseed.org/">Development Seed</a></div>
</div>
</body></html>