Sample Solution

Scrum is meant for those kinds of work which people have found unmanageable using existing (defined) processes like uncertain requirements combined with unpredictable technology implementation risks. While deciding whether to apply Scrum in any organization, as opposed to plan-driven approaches, one should always consider whether the underlying mechanisms are well-understood or whether the work depends on collaboration and knowledge creation.

SCRUM Roles

The Scrum Team consists of three roles: a ScrumMaster, a Product Owner, and the Team.

1. ScrumMaster
The ScrumMaster is the keeper of the scrum process who is responsible for the following:
• Ensuring that the project is run smoothly
• Removing bottlenecks/obstacles that impact productivity
• Organizing and facilitating the critical meetings
2. Product Owner
The Product Owner has the responsibility of maximizing the value of the product and the work of the team along with managing the Product Backlog.
Product Backlog management includes:
• Presenting Product Backlog items clearly
• Ordering the Product Backlog items to best achieve goals and missions.
• Optimizing the value of the work the Team performs.
• Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Team will work on further.
• Ensuring that the Team understands items in the Product Backlog to the level needed.
The Product Owner may do the above work or have the Team do it, but the accountability remains on the product owner.
The Product Owner may represent the aspirations of a committee in the Product Backlog, but if anyone wants to change a Product Backlog item’s priority, they must address the Product Owner.
The decision of the Product Owner if final and the entire organization must respect it since the decisions are visible in the content and ordering of the Product Backlog. The team has to w