Agile for Developers
Transitioning to Agile - what developers really need to know
Implementing an Agile approach exposes the day-to-day activities of a software developer to project managers and peers; progress becomes
more visible, and the way developers work becomes highly influential to project outcome. To ensure success, a somewhat different mindset is needed. Developers are arguably the key members of any Agile development team, and it is essential that Agile developers are fully aware of the scope of their responsibility and highly competent in developing software using Agile methods and techniques
During the day the workshop leader will bring to bear real-world experience and take a realistic and pragmatic view of how Agile projects are executed, to help developers understand how Agile methods will impact them and can help them deliver high-quality code. The workshop also allows time to cover the interaction between developers and other players in an Agile project team.
Why you should attend
This full, one-day workshop looks at Agile from a Developer’s perspective.
Throughout the day the workshop leader will look beyond the theory of Agile and explore with delegates what actually happens on an Agile project. Using real-life case studies, the workshop outlines what a developer should expect on an Agile project, describes the development techniques and tools used by developers on Agile projects and explain how these techniques can be applied and tools used to best effect.
At the end of the day delegates will be able to answer the following questions
- What is the role of a developer on an Agile project?
- What will be expected of a developer on an Agile project?
- What makes a good developer on an Agile project?
- What techniques and tools are useful on an Agile project and how and when should they be applied?
This workshop is not designed as a programming course – it is expected that delegates will already be reasonably competent developers. The workshop will however be invaluable for both relatively new and more experienced developers who are about to work on an Agile project and wish to gain a clear understanding of how ‘going Agile’ will change and impact their role.
Synopsis
What is Agile?
- Evolution of Agile
Agile principles
Most popular current Agile methodologies
Waterfall vs. Agile – similarities and differences
Where does Agile work well?
- Project type / size / criticality
Corporate culture and ethos
People considerations
The Project Team
- Roles and responsibilities
The role of a Developer
Being managed vs. self organising
Team dynamics
Understanding the Quality needs
- How is quality defined
When is ‘complete’ really ’complete’.
What should a Developer actually test?
Requirements
- Understanding the requirements
Prioritisation
How much documentation is sufficient?
Estimating
- What should a Developer be expected to estimate?
Estimating techniques
Expectation setting
Architecture
- The importance of architecture
How much design is needed
Proving the design
Refactoring
Using frameworks
Development Iterations
- Determining the content of iterations
Reviewing estimates
Measuring progress
Development Principles
- Allocating work
Ensuring quality
Coding and testing practices
Test driven development
Test automation
Continuous integration
The need for documentation?
Transitioning to Agile
- Preparing for change
The first Agile project
Common issues
An Agile project in a non-Agile programme
Waterfall vs. Part Agile vs. Completely Agile
Who should attend
- Developers
- Architects
- Development Managers
- Project Managers