Agile Adria conference is behind us. We’ve been enjoying great lectures, well organized and interesting with a variety of themes – how to sort business processes, how to prepare the organization for agile development and how to agile-develop applications.
Agile is a methodology for software development with four basic principles:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
SCRUM methodology was the conference’s buzzword. The great scrum master should be a remover of blocks, unbreakable buffer, champion of agile, chief connector, king of feedback but NOT a team leader. Making the great product backlog requires a prioritized list of all the features and functionalities needed to complete a project. Don’t forget, it is a living document, constantly changing and evolving to reflect the current realities of the project.
Other good methodologies were also mentioned: XP (Extreme programming ) and TDD (Test driven development). Besides efficient project management there is one thing that is becoming more and more important: UX (User experience) – encompasses all aspects of the end-user’s interaction with the company, its services, and its products.
One of the best lectures at the conference was the one by Andrea Provaglio, The beating heart of agile which addresses the issue of preparing the team for agile development and what mental techniques to use during the preparation period.
The common conclusion is that the new times are coming, that agile methodologies will become more popular, but for that to be possible it is necessary to change the way of thinking throughout the hierarchy, from developers to managers to users.
Agile methodology is a collection of innovative, user-centered approaches to system development. It tries to define an overall system plan quickly, develop and release software quickly, and then continuously revise the software to add additional features. After the downsides of the traditional software development approaches were identified (too many documentations, all requirements must be known at the beginning of a project,…) it became obvious that we needed another approach. And that’s how Agile was created.Read more ›