Scrum Case Analysis

Implementing Scrum
3.1 Scrum Suitability
Before adopting Scrum for your project, you should examine the suitability. In some cases, the better choices may be some other methodologies. The following aspects have to be considered before selecting Scrum to be applied to your project:
1. Accessibility of Product Owner: A representative of the customers or the product marketing should be available to act as the voice of the customer throughout entire project execution.
2. Level of technical talent: Availability of sufficient technical talent within the team to achieve gradual evolution of the solution.
3. Geographic distribution: Scrum works best with co-located, small teams.
4. Evolving requirements: Scrum fits better for projects require more

It describes the business objectives for the product, including the major objectives and relative priorities, and it outlines competitive positioning. It should provide clear guidance to all team members that supports evaluating the functional and nonfunctional requirements to determine the subset of requirements that are most valuable in the near term. The vision should be reviewed and updated as the customer’s needs change.
The Product Roadmap is the mid-level view that provides visibility across multiple re-leases. It describes the planned releases, marquee features for each release, technical strategy for the product, and target audience or customer base. It should include information about the direction of development for both the product and technology.
The Release Roadmap defines the overall strategy and a high-level path through the current release. It includes the prioritized goals for the release (for example, it specifies whether it is most important to automate existing functionality or provide new functionality to the users). It outlines the vision for the release and the strategy to achieve that vision, along with a description of each sprint.
The typical outcome of release planning is a high level of plan with roughly agreed upon contents for various sprints in the near

In this session the team collaborates to create a high-level design of the features it has committed to deliver. An outcome of this session is the sprint backlog, and the list of tasks that the team collectively needs to execute in order to turn the items in the selected product backlog into running tested features. This set of tasks is called the sprint backlog. The sprint tasks may be related to design, coding or testing of the features being delivered as appropriate. During SP2 the team may have additional questions regarding the requirements. The ScrumMaster must ensure that the Product Owner and, if necessary, other stakeholders are on call to answer