" Agile values "
Agile software development works quite different than traditional software development. Instead of "freezing requirements", changes are always expected, accepted and handled - even when they show up late in the development. Change is the only thing that is taken for granted.
Agile methods value individuals and interaction high and recognizes that successful software development includes a strong element of communication between people. An important key to success is frequent feedback on all levels - from code level up to business level.
This session will introduce agile values and principles and explain how adopting them makes a difference for your team, your company and your customer.
" Agile practices "
When the agile values are adopted, agile practices come into play (or often vice versa). Some agile methodologies requires certain practices, but most methodologies treat them as a smorgasbord, where the trick is to figure out which ones are useful for your team in your specific situation. A lot of agile practices will be explained, e.g. test-driven development, refactoring, pair-programming, continuous integration, agile modeling, simple design, small and frequent releases, automated acceptance testing and more.
After this session, you will have a good overview of the agile practices, and how you figure out which ones that works for you.
|
|
" Agile planning "
Like any other project, agile projects need to be planned. Planning methods differ substantially though, and they need to be planned in a different way. By only using traditional planning, a lot of the advantages of agile development are lost.
This session will introduce a number of different agile planning techniques and tools that helps you keep track of how the project is doing and help you plan even when the software is both changed and released frequently. You will also learn how to create useful measurements that give early feedback about the real progress (not the usual "80% done" kind of progress), the quality and other important things that helps both the team and the decisions makers to quickly adapt to the reality.
" Getting started "
So where do you start? Everything at once? Some pieces at a time, and if so - which ones should you start with? How do you introduce the values and the practices in an ongoing project? And what decisions do you make if it is a new project? How will the path to agile development differ depending on the composition of the team?
Niclas will give his views and recommendations of these issues, but this session will also allow for extra time for interaction, discussions and questions to help you decide which steps to take to get a good start in your own project or organization.
|
