Skip to content

Commit c6c5a4b

Browse files
author
Dan Croak
committed
Improve explanations in Trello guide
Based on feedback from @jessieay and @adarshp.
1 parent 7de73b9 commit c6c5a4b

File tree

1 file changed

+16
-4
lines changed

1 file changed

+16
-4
lines changed

product-management/trello/README.md

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,15 @@
11
Product management process with Trello
22
======================================
33

4-
The product management process with [Trello](http://trello.com) spans multiple
4+
A Trello board is a software equivalent of a physical wall with columns of
5+
sticky notes. In Trello terminology, the wall is called a "board." The columns
6+
are called "lists." The sticky notes in columns are called "cards."
7+
8+
No two products are the same, so flexibility in the product management process
9+
is important. Trello responds well to changing the structure of the process
10+
"on the fly."
11+
12+
Our product management process with [Trello](http://trello.com) can span multiple
513
Trello boards:
614

715
* Bugs
@@ -11,6 +19,9 @@ Trello boards:
1119

1220
![Current](http://f.cl.ly/items/3H3i1M0Q1G1s2V3I433S/Screen%20Shot%202013-02-25%20at%209.08.22%20AM.png)
1321

22+
"Current" is an example of a board. "In Progress" is an example of a list. "Set
23+
up Splunk for logging" is an example of a card.
24+
1425
Cards from Product Design, Bugs, Engineering boards are pulled into the Next Up
1526
list on the Current board as described in the "Weekly Product Meeting" section
1627
below.
@@ -43,7 +54,7 @@ lists on this board:
4354
If a bug is labeled Critical, then it is pulled immediately into Next Up. If the
4455
bug is not critical, it stays in Bugs until the next product meeting.
4556

46-
A bug has steps to reproduce the bug and optionally a screencast.
57+
A bug has steps to reproduce the bug and optionally a screenshot or screencast.
4758

4859
Product Design
4960
--------------
@@ -81,6 +92,7 @@ Hangout. They load the product on a screen, focus on recent changes to it, and
8192
use the working app and Trello boards to plan the upcoming week's iteration. The
8293
product manager runs the meeting like this:
8394

95+
* Archive the two-week old "Live (Week of [date])" list.
8496
* Review the Product Design board. Pull what we estimate to be an appropriate
8597
amount for this week into Next Up.
8698
* Re-sort the entire Next Up queue according to priority. Cards that were at the
@@ -139,5 +151,5 @@ on staging and are ready to be deployed (but not necessarily rolled out).
139151

140152
There is no central chokepoint for releasing to production: everyone can do it.
141153

142-
The cards in the Live (Week [date]) lists have been released. Each week has its
143-
own Live list so we can follow what got released when.
154+
The cards in the Live (Week of [date]) lists have been released. Each week has
155+
its own Live list so we can follow what got released when.

0 commit comments

Comments
 (0)