Dean Stevens proposes a way of integrating the business value concept into everyday Agile activity in order to achieve a higher value for an enterprise.
This presentation addresses a key business-technology alignment principal: understanding priorities in terms of business value. Traditional ROI type measurements of business value are expensive, inflexible and boring. A Perception Index (and a necessary "square peg adapter") offers is a lean, appropriate and fun alternative, for a fast changing business.
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 held during Agile 2008, Alan Shalloway, CEO and founder of Net Objectives, presents the Lean software development principles and practices and how they can benefit to Agile practitioners.
Choosing the right features can make the difference between the success and failure of a software product. Mike Cohn presented 'Prioritizing your Project Backlog' at Agile 2008 on how a project backlog should be organized and prioritized and non-financial techniques for prioritization such as kano analysis, theme screening/scoring, relative weighting and analytic hierarchy process.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile does not stand in just having a practice, but in finding ways to implement the principles contained by the Agile Manifesto.
Here is a story about Agile's use in a governmental organisation: at the 2006 APLN Leadership Summit Mark Salamango and John Cunningham looked at the problems and opportunities of introducing Agile in Army environments. True Agile practices cannot be 'commanded' or 'directed’ but frequent delivery offers Agile leaders a "soft" kind of power that is, in fact, very effective.
Last year Agile coach Alexia Bowers walked a mile in a project customer's shoes, and told us how it felt in this Agile2006 Leadership Summit presentation. She stressed the need to strive for creative solutions instead of simply cutting scope.
Scrum co-creator Ken Schwaber spoke at Agile2006 on code quality as a corporate asset. InfoQ presents video of his talk, The Canary in the Coalmine. Schwaber discussed how a degrading core codebase paralyses a team and negates any Agility gained through process improvement. He proposed strategies for management to identify, track and stop this downward spiral.
In a 60-minute JAOO 2005 talk, Scrum creator Dr. Jeff Sutherland covers the history of Scrum from its inception thru his participation with Ken Schwaber in rolling out Scrum to industry, to its impact at Easel, Fuji-Xerox, Honda, WildCard, Lexus, Google. He looks at Scrum types A, B and "all at once" type C, and confirms the humorous rumour that Kent Beck "stole" Scrum practices when creating XP.
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.