Watch the Recording
Everybody wants to be agile – but how do you demonstrate that the new agile projects are actually more effective than their non-agile predecessors? In particular, how can you measure the performance of all your projects in a way that allows their achievements to be compared independently of the practices that they are using, and in a way that is accessible to your business partners?
In the first seminar in our series, Ian Spence reviewed best practices for setting up an agile framework for organizational measures based around the improvement goals of Better, Faster, Cheaper and Happier.
In the second seminar in our series, Succeeding with Measurements in a Large Software Development Organization, Ian will present how these practices were applied to establish a set of pragmatic key performance indicators to drive improvement in a major telecoms out-sourcer.
Watch the Recording
Agile methods are empirical and encourage each and every project to measure its velocity and performance. Agile methods also encourage teams to inspect and adapt; changing their method and practices on the fly.
A large European organization saw the need to undergo major changes in their software development organization and processes. It was critical that everything was accurately measured. Better, Faster, Cheaper, Happier has become their framework for measuring success.
In this presentation, Ian Spence will review how this client set up the program, what's worked, and what needs further review and enhancement.
Who Should Attend:
• Project and Program Managers
• IT Directors and Managers responsible for project delivery
• Anyone who needs to improve their measurement criteria and further understand best practices in this area
What Attendees will Learn from this Case Study:
• How accessible measures can drive change
• What works and what needs careful consideration
• How to get started, quickly and easily
• How to frame their own objectives and set targets
• The benefits that accessible, intuitive measures can bring
Missed the first seminar in this series? View the recording.
Mark your Calendar for Seminar #3: June 29, 2010: Creating an Iterative Dashboard: Making sense of burn-downs, burn-ups and other practical project measures