Why Scrum?

Have you ever wondered why scrum is becoming more and more popular with every passing day? The simplest answer is that it is better than traditional project management in many ways.

The main difference between the traditional project management model and the scrum framework is the way in which the project is handled.

Let's take a look at a few differences between scrum and typical project management models.

Emphasis

Traditional project management is based on processes.

Where in scrum, it asks for a change in mind set with its focus on the people involved in the project. Although processes and tools are necessary for completing a project successfully, it is always the people who undertake, participate in and implement the project. They do the work that takes the project from idea to reality.

According to scrum, the key factors in any project are the people involved and the emphasis is on them and their actions. Various cross functional teams work in parallel across sprints to deliver potentially shippable deliverables at the end of each sprint.

Size

What gives scrum edge over other practices when it comes to the size of the team? Scrum can be used to manage projects of all sizes. It works well for most projects and team sizes. Large projects utilize multiple scrum teams which work at stint to ensure project progress.

Documentation

Since its early days, scrum has focused on producing working software over comprehensive documentation. It still does and has expanded its focus to include the incremental development of products over hefty documents. While documentation is necessary and useful for any project, scrum teams focus on interim deliverables in which real value is delivered to the customer. The documentation is done minimally as in when it is required. Lessons learned are recorded during retrospective meetings.

Process Style

The iterative model helps the product development improve over time. It maximizes opportunities for feedback and ensures potentially shippable versions of working products at the end of each sprint or iteration.

In a traditional model, the amount of functionality not completed remains hidden. And no product is delivered until the end or very near the end of the project.

Upfront Planning

In delivering the greatest value in the shortest amount of time means prioritizing work based on customer needs and differentiating “what will be done “ from “what needs to be done”.

Scrum encourages iterative decision making based on data over the detailed upfront planning practiced in style. It does not emphasize on meeting the project plan targets but focus more on satisfying customer requirements.

Traditional project management can lead to a situation where the plan is succeeded but the customer is not satisfied...

In addition to iterative planning and delivering, scrum supports the collaboration of all parties involved. The customer, business team and project team..etc which help to minimize risk and achieve satisfaction.

Domain

In the traditional method, the domain is assumed to be predictable. In today's business environment change is rapid and long term planning is problematic. Predicting and planning every detail of a new service and product is almost impossible. This is the main reason the domain is known to be unpredictable or exploratory.

Perspective to Change

Scrum uses its low upfront planning framework to be adaptable to change.

Risk management is continuous and works with the product owner, scrum team and scrum master to determine the best approach to handle identified risks. Where in traditional models, risks are handled up front even before many risks are being identified.

According to scrum, each deliverable goes to the quality assurance team as it is developed and testing is carried out keeping customer value in mind.

Strict controls such as acceptance criteria and a clear definition of done are in place to avoid deviations to the customers' requirements.

Leadership

In traditional methods, the process is given more importance. As opposed to the control and command style of management style, scrum believes that today's employees have much more to offer than just their technical expertise. And therefore deliver greater value when self-organized.

Unlike traditional methods in which value justification is done before the project commences, it is done throughout the project.

Management Style

The management style followed in scrum is decentralized in nature such that the work force does not have to be dependent on management for everything; which is the case in old autocratic project management methods. This encourages the workers to be innovative problem solvers.

Scrum believes that product development is a shared value creation process that needs all the stakeholders working and interacting together to deliver the greatest value. Command and control the rule of the day in traditional models.

Performance Measurement

How is team performance measured in scrum and traditional models? In scrum it is measured by the business value the team creates. While plan conformity decides the measurement of performance in traditional project methods, in scrum the team develops business value at the end of every sprint.

Return On Investment

Does scrum give a good return on investment? The answer is a big YES and the ROI starts early and is continuous throughout the project life. Where in traditional methods, the project provides ROI to the customer at the beginning and the development team at the end of the project.

Customer Involvement

How does scrum value the customers' participation?scrum highly recommends and is designed for effective involvement of customers throughout the project.In the traditional method, customer involvement during product or service is usually very limited but can vary depending on the projects life cycle.

In Summary

The factors above are not equally weighted; each is assessed depending on the individual project and circumstances.

Once we’ve decided which basic methodology to utilize, we can further refine the process to best fit our project goals. Ultimately, although the way in which we do our work is important, delivering a solid and maintainable product that satisfies our customer is what really counts.

What Do You Think?

Have you used any of these methods within your team? Have you faced any problems when using scrum or any traditional methods? How have you addressed them? Please share your thoughts and experiences.