Vadiraj Thayur, McAfee
Agile is a buzzword in the software industry and most companies are investing a huge amount in adopting Agile practices. Scrum, being one of the most prevalent agile methodologies is not very easy to adopt. There is no single way of adopting Scrum and that is why it is important to also learn from the experiences of teams who have adopted Scrum successfully.
Scrum is very flexible and this makes adoption tough and confusing. There are a huge percentage of teams worldwide who have been unsuccessful in adopting scrum, resulting in undesirable outcomes. An approach which works for one team might not work for another, even within the same company. If the project involves geographically distributed teams, the challenge gets tougher. So, adoption should be a mix of recommended practices and some real-world learnings.
The basic intent of this paper is to share the scrum adoption experience of a Distributed Agile team in McAfee. This approach also conforms to the Scaled Agile Framework adopted by McAfee for Distributed Projects. In McAfee, as part of the Business Platform Services (BPS) team, we adopted Scrum.
Because there is no best way for adopting Scrum, along with basic scrum principles, experiences of teams also come in handy. This paper shows the actual steps the team followed to successfully adopt scrum and its results. It could be a good case study for teams planning to adopt scrum in their projects.