Difference between revisions of "The People Side of CI"
From CitconWiki
Jump to navigationJump to search (add link to blog post w/change slides) |
|||
| Line 14: | Line 14: | ||
Slides on change, importance of status. People won't change w/out pain. | Slides on change, importance of status. People won't change w/out pain. | ||
| + | |||
| + | Change slides: http://blog.jeffreyfredrick.com/2008/07/07/tic-tac-change-slides/ | ||
Including Automated Unit Tests (JUnit, NUnit) | Including Automated Unit Tests (JUnit, NUnit) | ||
* Make tests part of development | * Make tests part of development | ||
* Include tests as part of development estimate | * Include tests as part of development estimate | ||
Latest revision as of 22:47, 7 July 2008
Facilitator: David Smart, Daniel Park
David's story:
- Feedback loops
- Visual control
- Self-organizing teams
View of change:
- Satir Change Model: http://www.stevenmsmith.com/my-articles/article/the-satir-change-model.html
- Team formation: Forming, Storming, Norming, Performing: http://en.wikipedia.org/wiki/Forming-storming-norming-performing
- Technical Adoption Lifecycle: http://en.wikipedia.org/wiki/Image:DiffusionOfInnovation.png
Story: bug database w/field for people to say how to avoid that kind of bug in the future
Slides on change, importance of status. People won't change w/out pain.
Change slides: http://blog.jeffreyfredrick.com/2008/07/07/tic-tac-change-slides/
Including Automated Unit Tests (JUnit, NUnit)
- Make tests part of development
- Include tests as part of development estimate
