Agile Scrum (SDLC)
At ALTECiSyS, we practice Agile Scrum process methodology for projects management. Agile Scrum is a management framework for incremental product development using one or more cross-functional, self-organizing teams of about seven people each.
It provides a structure of roles, meetings, rules, and artifacts. Teams are responsible for creating and adapting their processes within this framework.
Scrum uses fixed-length iterations, called Sprints, which are typically two weeks or 30 days long. Scrum teams attempt to build a potentially shippable (properly tested) product increment every iteration.
Characteristics of Agile Scrum:
-
Self-organizing teams
-
Product progresses in a series of month-long "sprints"
-
Requirements are captured as items in a list of "product backlog"
-
No specific engineering practices prescribed
-
Uses generative rules to create an agile environment for delivering projects
-
One of the "agile processes"
Scrum defines a minimal set of process elements that make up a Sprint. Scrum defines three roles, three ceremonies and three types of artifacts.
- Roles
-
-
The Scrum Master is responsible for facilitating Scrum. The Scrum Master does not organize the team or its tasks. He facilitates the team by coaching, teaching and supporting it.
-
The Product Owner is responsible for the features and the ROI of the product.
-
The responsibility of the Team is to deliver the Potentially Shippable Product Increment each Sprint. Teams are self-organizing and cross-functional.
-
- Ceremonies
-
-
The purpose of Sprint Planning is that the Product Owner presents the Product Backlog with his prioritized requirements as user stories. After that the Team selects the items it can deliver in the next Sprint and a Sprint goal is defined.
-
The Purpose of the Daily Scrum Meeting is to review the status in the Team to ensure communication and information flow inside the Team. Each team member answers the three questions "What did I do yesterday?", "What will I do today" and "Are there any impediments?".
-
The purpose of the Sprint Review is to present and demonstrate the Sprint result to the customer or product owner or other relevant stakeholder and get the acceptance for delivered Potentially Shippable Product Increment.
-
- Artifacts
-
-
The purpose of a Product Backlog is to provide a prioritized list of all features or user stories that cover all important details, which a customer or Product Owner wants to have in product.
-
The purpose of Sprint Backlog is to cover all selected backlog items which the Team will complete in the upcoming Sprint and give their commitment to. In the Sprint Backlog the Team plan required tasks to implement the selected backlog items.
-
The purpose of the Sprint Burn Down is to publicly display the remaining work of the current Sprint. If the Sprint Backlog is updated every day, it gives a simple view of the sprint progress, on a daily basis.
-