Andrea Provaglio
I'm an independent professional with almost twenty years of experience in
the field of Information Technology.
I assist clients from many different domains, which can range from large
organizations such as the European Commission in Brussels, or large
multinational banks, to small and dynamic IT companies.
My mission is to help my clients to develop better software and to create
better development teams; and to help the individuals to improve technically
and relationally.
I assist my clients primarily in these areas:
- Adoption of Agile methodologies, such as Extreme Programming (XP) and Scrum
- Development of soft skills for teams and organizations
- Coaching and training on software development for the Java/J2EE platform
- Software design, Best Practices and Design Patterns
- Design and development of Web/Enterprise applications
- Architectural assessments
- Skill assessments
- Team building
Track abstract - Agile in the organisation
Systemic Software Development for Agile Teams
We know that the success of a software development project (delivered on time, on budget, with the most
valuable features for the users and without major defects), plus the short-term and long-term quality of the
technical artifacts, are hardly just a technical matter. Instead, it’s the way all the people involved in the
project – inside and outside the team – are able to communicate and collaborate that makes the difference.
After all, software is created by people for the people.
In a systemic approach, all the individuals inside and outside the team are interconnected by a web of
relations and are part or the same system, that has its own history, structure, dynamics and rules for being
healthy. Understanding how the system works as a whole and how individuals interact according to those
rules is therefore essential to build effective and efficient teams.
In this session we’ll consider organizations and teams from a systemic perspective; we’ll talk about
leadership and guidance as a fundamental cohesive force, about how guidance may become dysfunctional,
about what happens when it does and which countermeasures can be taken; we’ll proceed with discussing
the systemic characteristics of most popular Agile and Lean methods, and with applying this understanding
to choose the method that may better suit a given team and/or project. In brief, we’ll learn how
incorporating organizational systemic, guidance, collaboration and communication in an industrial software
development process may turn out to be a critical success factor.
