Tag Archives: transformation
When it comes to implementing Agile, managers who are used to a “Command and Control” environment are going to be very uncomfortable. Now, let’s be honest, Command and Control managers are not all bad. They typically feel a high degree of accountability and that is a great thing. They feel like their neck is on the line so they want actions to be done as they command so that they can deliver. But what they fail to benefit from is the wisdom of the team.
The Power of the Team
Think about your team or colleagues. Who has long tenure and has ‘been there, done that’? Who is a relative new hire who may have relevant experiences from a previous employer? Who has worked in several different departments? Who has worked in several different roles? Each of these unique traits means that an employee might bring a unique perspective that the manager would benefit from, if they were willing to listen. Albert Einstein has famously said “we cannot solve our problems with the same thinking that we used when we created them.” Our employees have great ideas and many welcome the opportunity to creatively solve the problems of the business.
Members of management – manager, director, VP, whatever – should present the team with the problem or opportunity and let them ‘self organize’ to determine how they will solve the problem with teamwork.
Moving to Agile or Scrum introduces a lot of change and that can lead to conflicts in an organization. There are a number of key factors to consider when managing those conflicts so that they are resolved quickly and collaboratively.
1. Level Set on the Goals
Here is a common scenario that we see in Agile. The development team is frustrated because the Product Owner doesn’t have all of the answers and the Product Owner is frustrated that the developers ask for everything before they will work on anything. Does this sound familiar? In this scenario, we need to get back to basics and remember our main goal. We want to deliver working software that adds business value as quickly as possible. Both the development teams and the Product Owner share this goal and we need to remember that. No product owner is knowingly going to withhold information about the marketplace or the product and no development team ever plans to write crummy code. We all want the same thing, we just have different roles in how to achieve that. So if you find yourself at a stalemate, think back to the original goal and realign on that. It can really help to get everyone back on the same page.