Agile mindset over Agile framework
When I had the first contact with some agile framework (2010), I was taught about Scrum. Start with Scrum is like the “entrance door” of agile world. But today, I make a little different when I need teach some group about agile methodology. I start talking about the agile mindset.
Before learning Scrum or other agile methodology, is important understand it concepts. Agile mindset is based in human flexibility, in make simple, in think simple and aggregate business value. Agile mindset is more adaptability and less officialism.
How can I change my mindset?
Think, practice and live the agile manifesto.
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
What’s the problem of starting with Scrum?
There is no problem. But Is normal think about Scrum practices during the projects. Is most important to respect the agile manifesto. Is indifferent if you using Scrum, XP, Kanban or a mix. Learning Scrum is easier, but practice agile manifesto is hardest.
Ok. So, what’s the best way? Is Simple!!
Follow the principles behind the agile manifesto:
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals.
- Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development.
- The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity–the art of maximizing the amount of work not done–is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
To finalize, why am I writing this article?
Cause a lot of moments i saw groups focused in board, burndown chart, post-it, pencil, colors, following the routines and practices and in the sprint final, the fourth sprint, the fourth failure. My job, in this case, was understand the reason.
The main reason? No agile mindset. Just Scrum mindset.
That’s all folks! seeya 😉