Skip to main content

How Microsoft Vanquished Bureaucracy With Agile by Steve Denning

Microsoft has rapidly rising revenues and today is the most valuable firm on the planet—worth more than a trillion dollars.
In 2004, I would never have predicted this. At the time, I was visiting Microsoft for a short consultancy. I was shocked to find how bureaucratic it was. After working for several decades in another notorious bureaucracy, I knew the problems bureaucracy caused. But Microsoft was worse: it was impossible to get decisions from within a labyrinth of silos and layers that called to mind Kafka’s The Castle.
What can other big old firms learn from Microsoft’s escape from bureaucratic strangulation?
According to The Economist, the reason for Microsoft’s turnaround is that Satya Nadella, the CEO since 2014, took the bold decisions of a heroic leader. He opted not to rely on the existing business (Windows) and chose not to be “rapacious.”
The more important lesson for most big old corporations, though, is not so much the individual decisions of a heroic leader, but rather how Microsoft as an organization overcame the disease of bureaucracy. By the time Nadella became CEO, Microsoft had already embraced Agile and was ready to implement his bold decisions.
Microsoft Agile Journey

The Decisions Of The Heroic Leader
According to The Economist, Microsoft’s triumph lies in decisions taken by Satya Nadella:
Microsoft missed social networks and smartphones because of its obsession with Windows, the operating system that was its main money-spinner. One of Mr Nadella’s most important acts after taking the helm was to de-prioritize Windows. More important, he also bet big on the “cloud”—just as firms started getting comfortable with renting computing power.”
Second, Nadella shifted away from “rapaciousness.”
Mr Nadella has changed Microsoft’s culture as well as its technological focus. The cult of Windows ordained that customers and partners be squeezed and rivals dispatched, often by questionable means, which led to the antitrust showdown… [Instead] work with regulators rather than try to outwit or overwhelm them.”
Breaking From Bureaucracy: Microsoft’s Agile Journey
The bold decisions that Nadella took were good decisions, but they would have had little effect if Microsoft had not been ready to implement them. An Agile transformation process had been underway for some years.


Popular posts from this blog

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation. In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can up

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices. Some of the rules  The roles of Scrum • Scrum Master - • Product Owner • Feature Team The PDCA cycle (  )  frequent communication about risks (daily) • Plan – Sprint planning • Do – Actual engineering sprint – deliver a potential shippable code • Check – Sprint review • Act – Retrospective  The scrum guide @ will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum. Apart from these rest of

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I