todo
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
todo [2014/11/18 11:49] djo [Values] |
todo [2014/11/18 11:57] djo |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| * Good for research topics, when there aren't hard deliverables pre-committed by management | * Good for research topics, when there aren't hard deliverables pre-committed by management | ||
| * Good for contractual work, with mature teams who have measured their velocity and management that has built a pad into the schedule to account for unforeseen events | * Good for contractual work, with mature teams who have measured their velocity and management that has built a pad into the schedule to account for unforeseen events | ||
| + | |||
| + | * Ship often! | ||
| + | * Forces the team to remove pain points / automate / create checklists (There's a good reason airplane pilots use checklists) | ||
| + | * The team gets good at it | ||
| + | * Shipping becomes boring rather than exciting (boring ship dates are good ship dates) | ||
| * Milestone builds come with N&N and engage customers in the development process | * Milestone builds come with N&N and engage customers in the development process | ||
| * Eat your own dogfood (use your tools to build themselves as much as possible) | * Eat your own dogfood (use your tools to build themselves as much as possible) | ||
| + | |||
| + | * Additional practices | ||
| + | * Document anything that must be manual--helps and make processes disaster-resilient | ||
todo.txt ยท Last modified: 2017/07/11 22:26 by djo
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
