Agile brings discipline and structures the innovative way for developing software. Not only does it promote quality code; but it also improves the product. So why do the developers or programmers hate ‘Agile’?
Organizations globally have adapted Agile in some way or the other. Scrum being widely accepted as a framework to implement the principles of agile. This all started in 90’s with the first agile project being C3 (Chrysler Comprehensive Compensation System). When Agile started, it advocated adaptive planning, evolutionary development, early delivery, and continuous improvement to encourage rapid and flexible responses to change. On the other hand Lean adapted from the Toyota Production Company; the focus is aggressively on the below:
1. Eliminate waste
2. Amplify learning
3. Decide as late as possible
4. Deliver as fast as possible
5. Empower the team
6. Build quality in
7. See the whole
Let’s try to weave them together:
Not just logical appeal would let you convince or win hearts of people. You really have to win the emotions of people. We have to tap into the hearts and bellies of the listeners.
We have to align to the values of the listeners. Lets say you have two colleagues, one who pays importance to financial aspects in his life and the other one likes to be the center of attraction to the crowd. If you want both to be aligned for a software that is to be introduced to the organisation then you need to approach with a strategy.
An agile team’s velocity is dependant on how many stories were picked up in a sprint and executed. Scrum framework lays emphasis on committing to work with sustainable pace. Basically, velocity is the speed at which the team moves forward.
Leadership lays a lot of importance on how the agile teams can be made more productive and efficient. That brings down to scrum master ownership, on how he can help the teams to improve the velocity over a period of time.
Some of steps that can be beneficial in improving the velocity are:
Continuous Delivery is a practice that emerged from XP(Xtreme Programming) and is definitely not new. It goes back to the early days when Kent Beck and his team were doing it.
The practice of software delivery is far from perfect today. Implementing Continuous Delivery not only solves technical challenges, but also enhances the development environment. Here are a few reasons why adapting continuous delivery can help businesses seek competitive advantage:
Good leaders don’t just happen overnight and it takes time and experience to rise into leadership roles.
In IT industry we use the word “resource” which in my opinion is a bit harsh. They are just people…
Leadership is a skill and being a leader has nothing to do with a rank. Leadership is a choice which one opt’s for the people.
We human’s are not machines. We have emotions and need to become people centric. Organisations need good leaders to drive inspiration and offer continuous coaching, so that people can follow them in their movement and fulfill the goals of the companies successfully.
“leaders are not responsible for results but are rather responsible for people, who are ultimately responsible for results”.
Agile is a path where you learn and improve continuously. With this statement someone asked “If it is a path then how do you know how much to travel and how much to be left to travel”. This brings in a question in our mind how do we measure the agility of our teams ? Is there a standard matrix or assessment tool ? The answer to this is NO, however you can test your teams against the core values of scrum. You can post some very smart questions against each of these values to identify how effective they are as a team.
Some of the sample effective questions are as follows: