Why does Scrum Work?

1. The basic premise is that if you are committed to the team and the project, and if your boss really trusts you, then you can spend time being productive instead of justifying your work.
2. This reduces the need for meetings, reporting, and authorization.
3. There is control, but it is subtle and mostly indirect.
4. It is exercised by selecting the right people, creating an open work environment, encouraging feedback, establishing an evaluation and reward program based on group performance, managing the tendency to go off in different directions early on, and tolerating mistakes.
5. Every person on the team starts with an understanding of the problem, associates it with a range of solutions experienced and studied, then using skill, intelligence, and experience will narrow the range to one or a few options.
6. Keep in mind that it can be difficult to give up the control that it takes to support the Scrum methodology.
7. The approach is risky, there is no guarantee that the team will not run up against real limits, which could kill the project.
8. The disappointment of the failure could adversely affect the team members because of the high levels of personal commitment involved.
9. Each person on the team is required to understand all of the problem and all of the steps in developing a system to solve it, this may limit the size of the system developed using the methodology.

How does Scrum work?

•  The first thing that happens is the initial leader will become primarily a reporter.
•  The leadership role will bounce around within the team based on the task at hand.
•  Soon QA developers will be learning how requirements are done and will be actively contributing, and requirements people will be seeing things from a QA point of view.
•  As work is done in each of the phases, all the team learns and contributes, no work is done alone, the team is behind everything.
•  From the initial meeting, the finished product is being developed.
•  Someone can be writing code, working on functional specifications, and designing during the same day, i.e. “all-at-once”.
•  Don’t be surprised if the team cleans the slate numerous times, many new ways will be picked up and many old ways discarded.
•  The team will become autonomous, and will tend to transcend the initial goals, striving for excellence.
•  The people on the team will become committed to accomplish the goal and some members may experience emotional pain when the project is completed.


•  Scrum is an agile process to manage and control development work.
•  Scrum is a wrapper for existing engineering practices.
•  A scrum is a team-based approach to iteratively, incrementally develop systems and products when requirements are rapidly changing
•  Scrum is a process that controls the chaos of conflicting interests and needs.
•  Scrum is a way to improve communications and maximize co-operation.
•  Scrum is a way to detect and cause the removal of anything that gets in the way of developing and delivering products.
•  Scrum is a way to maximize productivity.
•  Scrum is scalable from single projects to entire organizations. Scrum has controlled and organized development and implementation for multiple interrelated products and projects with over a thousand developers and implementers.
•  Scrum is a way for everyone to feel good about their job, their contributions, and that they have done the very best they possibly could.


Scrum naturally focuses an entire organization on building successful products. Without major changes -often within thirty days – teams are building useful, demonstrable product functionality. Scrum can be implemented at the beginning of a project or in the middle of a project or product development effort that is in trouble.

Scrum is a set of interrelated practices and rules that optimize the development environment, reduce organizational overhead, and closely synchronize market requirements with iterative prototypes. Based on modern process control theory, Scrum causes the best possible software to be constructed given the available resources, acceptable quality and required release dates. Useful product functionality is delivered every thirty days as requirements, architecture, and design emerge, even when using unstable technologies.