We continue learning about the implementation of Agile at big companies from the series of blog posts by our project manager Ivanna, aka Vania.
Let’s now give her the floor once again.
Last time I wrote about how I got to know Agile and what experience Apple and Phillips had with this framework...
Today, let's talk about other famous companies.
Agile and Nokia
Interesting fact: Scrum standard, the organizing method that is most widely used by different companies, was invented by Nokia in the prime of its existence. This happened because Nokia thought that it would help them to be one of the leadinger companies of mobile phone manufacturing.
Here are some principles of working with this framework from Nokia:
- The product owner: the team should know who it is.
- The product owner has to have one product backlog with stories and rating. The latter has to be done by the team.
- A burndown-diagram is needed for the whole team to measure their productivity
- During the sprint, no one should interfere with the team’s work.
Agile’s introduction to Intel
Intel began to introduce Agile with the help of the training company Danube Technologies. Danube Technologies - is an American program from CollabNet, that offers products to improve engineering projects as well as Scrum management. Danube Technologies is the developer of the Scum add-ons such as ScrumWorks Basic and ScrumWorks Pro.
There is also a ScrumCORE department, that provides Scrum training by means of planned public courses and private lessons.
The Intel’s main task was to increase the productivity of developers, minimize risks and to reduce the amount of written documentation by narrowing down web development to the series of iterations. In other words, to make the process of developing the Intel products more flexible. So Agile has become their prefered method. Not everything went as planned at first though: top managers that were supposed to lead the whole team, didn’t attend trainings, and as a result of the theory gaps, they wasn’t able to introduce innovations in practice. The first visible results appeared only after a year.
The communication between the members of one team as well as between different teams has become the most effective way to understand what is the easiest way to adapt Agile principles to the Intel products manufacturing.
As time went on, using Agile principles as the basis, Intel developers had managed to set up their own way of working, that allows them to do their work really quickly, and thus to release a product on time. For example, teams realised that two-week long iterations do not work for them, so they changed it to a 9-days long one. This shows that Agile is not a list of rules that are to be strictly followed. On the contrary, if you follow the Agile manifest, you shouldn’t be afraid of adding something new to it.
As we have been doing, we will continue speaking about big companies and their experience with Agile. Next time find out about Microsoft, Salesforce and others. See you soon!
To be continued...