The Scrum Guide: Framework for Delivering High-Value Products

The Scrum Guide

Framework for developing and sustaining complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is lightweight, simple to understand and difficult to master.

The Scrum Team

The Scrum Team: Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. It is designed to optimize flexibility, creativity, and productivity. It consists of:

• The Product Owner: Responsible for maximizing the value of the product and the work of the team. Responsible for managing the Product Backlog.
• The Development Team: Professionals who do the work of delivering a potentially releasable increment of 'Done' product at the end of each Sprint.
• The Scrum Master: Responsible for ensuring Scrum is understood and enacted. Helps those outside the Scrum Team understand their interactions with the team.

Scrum Events

Scrum Events: Used to create regularity and minimize the need for meetings not defined in Scrum. All events are time-boxed.

• The Sprint: Time-box of one month or less in which a 'Done', usable, and potentially releasable product Increment is created.
• Daily Scrum: A 15-minute time-boxed event for the development team to synchronize activities and create a plan for the next 24 hours.
• Sprint Review: Held at the end to inspect the Increment and adapt the Product Backlog if needed.
• Sprint Retrospective: Opportunity for the Scrum Team to inspect itself and create a plan for improvements.

Scrum Artifacts

Scrum Artifacts: Represents work to provide transparency for adaptation.

• Product Backlog: Ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made in the product.
• Sprint Backlog: Set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.
• Increment: Sum of all the Product Backlog items completed during a Sprint and the value of increments of all previous Sprints.

Specify Requirements

What is a model? A model is a simplified representation of a real object containing all the relevant attributes. Different processes will create different models of the same object.

• Functional requirements: Can be negotiated and implemented incrementally, have to be tested, and require understanding of the process.
• Non-functional requirements: Usually more critical to system functionality, can be measured easily, and are usually system requirements. They're easy to fulfill.

How to measure them? Speed (Transactions per second), Size (Megabytes), Ease of use (Training time), Reliability (Downtime), Robustness (Time to restart after a problem), Portability (Number of target systems).

Unified Modeling Language (UML)

Intended to provide a standard way to visualize the designs of a system.

• Types of diagrams:
  • Use Case Diagram
  • Activity Diagram: Graphical representations of a workflow, focus on procedures and activities.
  • Class Diagram: Represents object-oriented programming, with class name or identifier, data members, and member functions.

Interactions between classes:

• Inheritance: The process of a child or sub-class taking on the functionality of a parent or superclass.
• Bidirectional Association: Both classes are aware of each other and their relationship with the other.
• Aggregation: The Wheel class lives independently of the Car Class.
• Composition: Company class will always have at least one Department class.