Agile: Revolution or evolutioN?
Is Agile really such a revolutionary change to software development?
Many companies are actively considering moving from the traditional ‘waterfall’ application development process to a more fluid Agile approach, but are concerned about the scale of the change and the risks involved.
In this workshop we compare the Agile approach to software development to the traditional waterfall approach (specify > design > code > test > implement), allowing delegates to visualise and evaluate what specific risks will be involved in moving to Agile, and the scale of the change needed in their own organisations.
We will also look at what ‘Agile’ really means. Is it the case that ‘you are either Agile or you are not’? Or is there some best-of-both-worlds, ‘in-between’, Agile-esque state whereby it is possible to achieve (say) 80% of the benefits of Agile – pace of development, flexibility, etc. – without giving up conventional risk-management devices such as defined phase start and end points or fixed-price supplier contracts.
Will implementing Agile be an evolutionary journey or will it be a revolutionary upheaval? This workshop will help you decide.
Why you shoud attend
The workshop looks beyond a theoretical Agile implementation and offers deeper insight in to what makes a project ‘Agile’ rather than ‘waterfall’. ‘Lessons learned’ is at the heart of this workshop, and your workshop leader will invoke a carefully-selected set of real-world examples of organisations moving to an Agile approach; each with differing degrees of success and, in some cases, pain.
By the end of the workshop delegates will have a clear, practical understanding of Agile and be able to answer the following questions:
- What will be the real impact of implementing an Agile approach within my IT department?
- How ready are we to adopt Agile?
- In the real world, what projects are suitable for implementing in an Agile way?
- Should I go ‘fully-Agile’ on my first project or is there a lower risk way to implement Agile?
Synopsis
What is Agile?
- The evolution of Agile
Overview of the most popular current Agile methodologies
Waterfall vs. Agile – similarities and differences
Why go Agile?
Theoretical benefits and risks
Real benefits, and real risks
Impact on the IT department, users, customers, partners and suppliers
Where Agile works
- Culture / ethos of an Agile organisation
Types of project where Agile works well
Projects to avoid
How Agile can you (should you) go?
- Baselining your current position
Setting Agile goals
Valuing benefits, evaluating risks
Team roles on an Agile project
- Stakeholders
Project Manager
Analyst
System Architect / Designer
Developer
Tester
Other roles
Managing the transformation to Agile
- Choosing the correct approach
Planning the transformation
Reducing risk
Who should attend
- CEOs
- Main Board Directors
- Business Sponsors
- CIOs & IT Directors
- Senior IT Managers
- Programme Managers
- Project Managers