Joel Semeniuk discusses ways of making better project estimates excluding guessing as much as possible.
Russ Miles discusses the importance of having values at the foundation of one’s beliefs which in turn influence the behaviors resulting in actions.
Anne Thomas Manes discusses SOA goals and objectives used to measure a system’s success, measuring the business value, SOA project metrics, and recommendations on proving the business value of SOA.
It is possible to measure certain properties of code, and on the one hand, correlate them with project factors known to have economic merit and on the other, with programmer-pleasing practices. This session surveys emerging evidence that we can measure the effect of the technical practices of Agile development, and explores what we might be able to do about it to our benefit.
In this presentation filmed during ThoughtWorks’ Quarterly Technology Briefing, Dave Robertson and John Johnston explain what the Agile and User Centered Design’s (UCD) common denominators are, common values being the most important one in their opinion.
Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD). The presentation intends to be a primer for managers who want to understand the value of TDD, and of Agile in general, in software development.
In this presentation filmed during Agile 2008, Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He measures the development productivity and effectiveness and compares the results with industry averages. He also presents the factors which contributed to the success of BMC's Agile adoption.
In this 90-minute talk from the Agile2007 conference, Lean software thought leader Mary Poppendieck reviewed 20th century management theories, including Toyota and Deming, and went on to talk about "the matrix problem", alignment, waste cutting, planning and standards. She closed by addressing the role of measurement: "cash flow thinking" over "balance sheet thinking".
Agile methods are empirical: plan, do, evaluate how it went, plan the next thing. When these cycles are very short, learning happens quickly and teams can move into high-performance mode. But discipline is necessary - planning must happen continuously to feed the fast-moving team. For 80 minutes David Hussman looks at the Agile practices around planning a project, a release, and an iteration.