Discover

What is theSCRUM?

theSCRUM is an open source software solution to help teams manage the Scrum process:

• Product backlog management for the Product Owner,
• Sprint backlog management for the Scrum Master and the team,
• Roadmap management and release management for organization with several projects / several Scrum teams.

What is Agile software development?

From Wikipedia:

Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The term was coined in the year 2001 when the Agile Manifesto was formulated. Agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals.

What is SCRUM?

From Wikipedia:

Scrum is an iterative incremental framework for managing complex work (such as new product development) commonly used with agile software development. Scrum is a “process skeleton,” which contains sets of practices and predefined roles. The main roles in Scrum are:

1. the “ScrumMaster“, who maintains the processes (typically in lieu of a project manager);
2. the “Product Owner“, who represents the stakeholders;
3. the “Team“, a cross-functional group of about 7 people who do the actual analysis, design, implementation, testing, etc.

During each “sprint“, typically a two to four week period (with the length being decided by the team), the team creates a potentially shippable product increment (for example, working and tested software). The set of features that go into a sprint come from the product “backlog,” which is a prioritized set of high level requirements of work to be done. Which backlog items go into the sprint is determined during the sprint planning meeting. During this meeting, the Product Owner informs the team of the items in the product backlog that he or she wants completed. The team then determines how much of this they can commit to complete during the next sprint. During a sprint, no one is allowed to change the sprint backlog, which means that the requirements are frozen for that sprint. After a sprint is completed, the team demonstrates the use of the software.

Scrum enables the creation of self-organizing teams by encouraging co-location of all team members, and verbal communication across all team members and disciplines that are involved in the project.

A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called requirements churn), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. As such, Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team’s ability to deliver quickly and respond to emerging requirements.