Five Key Numbers to Gauge your Agile Engineering Efforts
Report
Share
•28 likes•18,564 views
![Five Key Numbers to Gauge your Agile Engineering Efforts,[object Object],Jeff Nielsenjeff@jeffnielsen.com,[object Object],Agile Tech DC,[object Object],May 14, 2011,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-1-2048.jpg?cb=1665163603)
![There are many benefits to working incrementally in short cycles . . .,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-2-2048.jpg?cb=1665163603)
![. . . if you can pull it off,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-3-2048.jpg?cb=1665163603)
![Agile engineering practices are supposed to enable a flattened cost-of-change curve,[object Object],TDD,[object Object],refactoring,[object Object],continuous integration,[object Object],pair programming,[object Object],coding standard,[object Object],automated builds,[object Object],automated tests,[object Object],. . .,[object Object],Craig Davidson, http://www.agileadvisor.com/2009/01/yagni-and-cost-of-change-curve.html,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-4-2048.jpg?cb=1665163603)
![But it’s not sufficient simply to do the practices(They’re not binary),[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-5-2048.jpg?cb=1665163603)
![How do we knowhow effectivewe are atflattening the curve?,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-6-2048.jpg?cb=1665163603)
![Five key numbers . . .Not intended to be comprehensive or even very scientific,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-7-2048.jpg?cb=1665163603)
![Seconds,[object Object],20,[object Object],#1How long until you see feedback from a test after writing or changing a line of code?,[object Object],16,[object Object],12,[object Object],8,[object Object],4,[object Object],0,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-8-2048.jpg?cb=1665163603)
![#2How many one-line changes can you commitand push to testin an hour?Following the team’s practices, of course,[object Object],20,[object Object],16,[object Object],12,[object Object],8,[object Object],4,[object Object],0,[object Object],Commits,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-9-2048.jpg?cb=1665163603)
![The speed of the feedback affects the speed at which you can work,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-10-2048.jpg?cb=1665163603)
![5,[object Object],4,[object Object],3,[object Object],2,[object Object],1,[object Object],0,[object Object],#3How many people on your team can explain the details of any particular section of code?,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-11-2048.jpg?cb=1665163603)
![100%,[object Object],#4What percentage of your team members did you pair with in the last two days?,[object Object],80%,[object Object],60%,[object Object],40%,[object Object],20%,[object Object],0%,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-12-2048.jpg?cb=1665163603)
![“Promiscuous” pairing speeds up communication and builds trust,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-13-2048.jpg?cb=1665163603)
![#5How many manual steps does it take to get a build into production?,[object Object],15,[object Object],12,[object Object],9,[object Object],6,[object Object],3,[object Object],0,[object Object],Steps,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-14-2048.jpg?cb=1665163603)
![Higher transaction costs drive longer cycles and bigger batches,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-15-2048.jpg?cb=1665163603)
![To lower the cost-of-change curve, we must lower the transaction costs associated with adding features,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-16-2048.jpg?cb=1665163603)
![Make it cheaper to,[object Object],Change code ,[object Object],Check in code,[object Object],Understand the code,[object Object],Communicate with your teammates,[object Object],Push code to production,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-17-2048.jpg?cb=1665163603)
![If we can make changes cheaply enough . . . ,[object Object],. . . the cost savings from quicker feedback and increased learning outweighthe costs of overhead and rework.,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-18-2048.jpg?cb=1665163603)
![120,[object Object],96,[object Object],72,[object Object],48,[object Object],24,[object Object],0,[object Object],BONUS,[object Object],What’s theaverage typing speed of the programmers on your team?,[object Object]](https://image.slidesharecdn.com/slideshare-five-key-numbers-110516075014-phpapp01/75/five-key-numbers-to-gauge-your-agile-engineering-efforts-19-2048.jpg?cb=1665163603)
Five Key Numbers to Gauge your Agile Engineering Efforts
•28 likes•18,564 views
Report
Share
Talk given at Agile Tech DC, May 14, 2011
More Related Content
What's hot
What's hot(20)
Viewers also liked
Viewers also liked(10)
Similar to Five Key Numbers to Gauge your Agile Engineering Efforts
Similar to Five Key Numbers to Gauge your Agile Engineering Efforts(20)
Recently uploaded
Recently uploaded(20)
Five Key Numbers to Gauge your Agile Engineering Efforts
Editor's Notes
- Speed up feedback loops, know whether you’re building the right thing, whether it’s going to make you money, know if you understood the requirements, be more responsive to your customers, change direction quickly
- What if you could engineering things in such a way so that you could produce a constant stream of new features at a steady rate, regardless of the age and/or size of the system?
- OBJECTIVES Understand how various agile engineering practices help to flatten the cost of change curve See why lowering transaction costs is a key theme of agile engineering practices Be exposed to some ways to evaluate the maturity of their own agile engineering effortsHave ideas about how to improve their implementation of agile engineering practices
- This exposes the limit of how quickly you can work within your team context.
- Collective code ownershipSimple designGroup designTransparency in version controlReduce the WTH’s per minute in a code reviewPAIRING
- You need a shared contextBuild trust through interactionIf you aren’t working regularly side-by-side with your teammates, the team knowledge and cohesion is going to fracture