理想的Agile工作環境
The Ideal Agile Workspace
http://blog.mountaingoatsoftware.com/the-ideal-agile-workspace
March 5th, 2009
Posted by Mike Cohn
Published in Mike Cohn's BLog
作者認為一個理想的Agile 工作環境, 需要具備以下狀況
1. 引人注目的大型圖表 (Big Visible Charts)
- Agile teams like to hang the charts on their walls.
- Charts like these provide a strong visual reminder of the current state of the project.
- What is shown on these charts will get the attention of team members so display charts showing the most important information for that sprint.
- There are some items could on the charts
* sprint burndown chart, showing the number of hours remaining as of each day of the current sprint.
* the number of passing customer acceptance tests
* the pass/fail status of tests by day
* print and release burndown charts
* number of new stories introduced to the product backlog per sprint, and more.
2. 額外回饋的機制 (Additional feedback devices)
- For example:
* A lava lamp that is turned on whenever the automated build is broken.
* Use flashing red traffic lights to indicate exceptional conditions such as an issue on a production server.
* Ambient orbs and Nabaztag rabbits, which are wireless programmable devices that can also be configured to change colors, speak messages, or wiggle their ears as a team desires.
- Devices like these make a workspace more dynamic, unobtrusively bringing into it information the team may find helpful.
3. 每個人都在同一工作場所 (Everyone on your team)
- Each person on the team should ideally be able to see each other person on the team.
- This absolutely includes the ScrumMaster and ideally includes the product owner.
- I do understand, however, that product owners often have responsibilities to other groups outside the development team and so may sit near them instead.
- Still, in an ideal world the product owner would be visible to everyone in the team workspace.
4. 在這Spint中的工作清單 (The sprint backlog)
- One of the best ways to ensure that everything necessary is completed in the sprint is to make the sprint backlog visible.
- The best way to do that is by displaying the sprint backlog on a wall, ideally in the form of a task board.
- A task board is usually oriented in rows and columns with each row containing a particular user story and one index card or sticky note for each task involved in that story.
- Task cards are organized in columns, minimally including “To Do” “In Process,” and “Done.”
- In this way, team members are able to see work progressing across the task board during the sprint and all work to be done is visible at all times.
5. 整個專案的工作清單 (The product backlog)
- One problem with running an endless series of sprints is that each can feel disconnected or isolated from the whole of a planned released or related set of new capabilities.
- A good way to reduce the impact of this problem is by displaying the product backlog somewhere clearly visible.
- This can be as simple as keeping the shoebox full of user stories written on index cards on a table in the middle of the team’s space.
- Even better, tack the index cards with those upcoming user stories on a wall where all can see them.
- This allows team members to see how the user stories they are working on in the current sprint relate to others that are coming soon.
6. 至少要有一個大白板 (At least one big white board)
- Every team needs at least one big whiteboard.
- Locating this in the team’s common workspace encourages spontaneous meetings.
- One developer may start using the board to think through a problem; others may notice and offer to help.
7. 要有私人和寧靜的空間 (Someplace quiet and private)
- As important as open communication is, there are times when someone needs some peace and quiet.
- Sometimes this is for something as simple as a private phone call.
- Other times it can be to think through a particularly challenging problem without being interrupted.
8. 食物和飲料 (Food and drink)
- It’s always a good idea to have food and drink available.
- These don’t need to be fancy, and they don’t even need to be provided by the organization.
- It could buy a small under-desk refrigerator and share the expense of buying water bottles or soda for it.
- Other teams buy a coffee machine, depending on team preferences.
- Some teams rotate bringing in snacks, both healthful and not.
9. 對外的窗戶 (A window)
- One of the nice things about an open workspace is that windows are shared.
- Even if the view is only of our parking lot and can only be seen across three messy desks, at least I can see the window and some natural light.
The Ideal Agile Workspace
http://blog.mountaingoatsoftware.com/the-ideal-agile-workspace
March 5th, 2009
Posted by Mike Cohn
Published in Mike Cohn's BLog
作者認為一個理想的Agile 工作環境, 需要具備以下狀況
1. 引人注目的大型圖表 (Big Visible Charts)
- Agile teams like to hang the charts on their walls.
- Charts like these provide a strong visual reminder of the current state of the project.
- What is shown on these charts will get the attention of team members so display charts showing the most important information for that sprint.
- There are some items could on the charts
* sprint burndown chart, showing the number of hours remaining as of each day of the current sprint.
* the number of passing customer acceptance tests
* the pass/fail status of tests by day
* print and release burndown charts
* number of new stories introduced to the product backlog per sprint, and more.
2. 額外回饋的機制 (Additional feedback devices)
- For example:
* A lava lamp that is turned on whenever the automated build is broken.
* Use flashing red traffic lights to indicate exceptional conditions such as an issue on a production server.
* Ambient orbs and Nabaztag rabbits, which are wireless programmable devices that can also be configured to change colors, speak messages, or wiggle their ears as a team desires.
- Devices like these make a workspace more dynamic, unobtrusively bringing into it information the team may find helpful.
3. 每個人都在同一工作場所 (Everyone on your team)
- Each person on the team should ideally be able to see each other person on the team.
- This absolutely includes the ScrumMaster and ideally includes the product owner.
- I do understand, however, that product owners often have responsibilities to other groups outside the development team and so may sit near them instead.
- Still, in an ideal world the product owner would be visible to everyone in the team workspace.
4. 在這Spint中的工作清單 (The sprint backlog)
- One of the best ways to ensure that everything necessary is completed in the sprint is to make the sprint backlog visible.
- The best way to do that is by displaying the sprint backlog on a wall, ideally in the form of a task board.
- A task board is usually oriented in rows and columns with each row containing a particular user story and one index card or sticky note for each task involved in that story.
- Task cards are organized in columns, minimally including “To Do” “In Process,” and “Done.”
- In this way, team members are able to see work progressing across the task board during the sprint and all work to be done is visible at all times.
5. 整個專案的工作清單 (The product backlog)
- One problem with running an endless series of sprints is that each can feel disconnected or isolated from the whole of a planned released or related set of new capabilities.
- A good way to reduce the impact of this problem is by displaying the product backlog somewhere clearly visible.
- This can be as simple as keeping the shoebox full of user stories written on index cards on a table in the middle of the team’s space.
- Even better, tack the index cards with those upcoming user stories on a wall where all can see them.
- This allows team members to see how the user stories they are working on in the current sprint relate to others that are coming soon.
6. 至少要有一個大白板 (At least one big white board)
- Every team needs at least one big whiteboard.
- Locating this in the team’s common workspace encourages spontaneous meetings.
- One developer may start using the board to think through a problem; others may notice and offer to help.
7. 要有私人和寧靜的空間 (Someplace quiet and private)
- As important as open communication is, there are times when someone needs some peace and quiet.
- Sometimes this is for something as simple as a private phone call.
- Other times it can be to think through a particularly challenging problem without being interrupted.
8. 食物和飲料 (Food and drink)
- It’s always a good idea to have food and drink available.
- These don’t need to be fancy, and they don’t even need to be provided by the organization.
- It could buy a small under-desk refrigerator and share the expense of buying water bottles or soda for it.
- Other teams buy a coffee machine, depending on team preferences.
- Some teams rotate bringing in snacks, both healthful and not.
9. 對外的窗戶 (A window)
- One of the nice things about an open workspace is that windows are shared.
- Even if the view is only of our parking lot and can only be seen across three messy desks, at least I can see the window and some natural light.
全站熱搜
留言列表
