SCRUM Basics
Whats a SCRUM ?, basically is team environtment to define objetives and personal contributions to a project.
Traditional methods to onboard a project
Waterfall model
Itterative model
Scrum is based on the itterative model.
Key Agiles principles
- Satisfaction & delivery (Costumer)
- Welcoming change
- Deliver Frequently
- Communication is the key
- Environment and trust
- Face to face communication
- Software as measure of progress
- Sustainable Development
- Attention to details
- The power of less
- Self-organizing teams
Agile development
But first take a look inside the manifesto:
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
…Manifesto for Agile Software Development, Authors: Beck, Kent, et al. (2001)
Agile Methodologies
Agile Methodology is a people-focused, results-focused approach to software development that respects our rapidly changing world. It’s centered around adaptive planning, self-organization, and short delivery times. A little about these.
Dynamic System Development Methodology (DSDM)
Prioritization and collaboration. It was used to fine-tune the traditional approaches.
Scrum
Manage tasks within a team-based development environment.
Extreme Programming (XP)
Improve productivity and introduce checkpoints where new customer requirements can be adopted
Test-driven Development (TDD)
Relies on the repetition of a very short development cycle
Lean
Lean is centered on preserving value with less work.
Kanban
Method through which Just-In-Time (JIT), an excellent way for promoting improvement.
The Scrum Team consists of three roles, namely a ScrumMaster, a Product Owner, and the Team.
The Scrum events time-boxed events, with a max.duration.
The sprint (2 weeks project - 1 month project)
Is based on a Sprint goal(Objective that provides guidance to the Team on why it is building the product increment) to develop a product. Provides guidance to build the product increment. Can be renegotiated between the owner group and the team. Cancellation during a sprint is very uncommon, and might occur if the organization changes direction or if market or technology conditions change.
Sprint Planning Meeting (4hours for two weeks project/ 8hr 1month project)
Meetings are focuse on :
- What needs to be and can be delivered in the Sprint increment?
- How wiil the wrokd needed for the execution of sprint be achieved?
Topics about the meeting:
- Prodduct Backlog
- Latest product increment
- Projected capacity of the team during the sprint
- Past performance of the team
- Discuss the funcionality during the sprint
- Provide clarifications on the product Backlog items
By the end of the Sprint Planning meeting, the work is divided into tasks of duration of one day or less.
Daily Scrum Meetings (dayli meet 15 min)
During the meeting each team member explains:
- What did he do yesterday tha helped the team meet the sprint goal?
- What will he do today to help the team meet the sprint goal?
- Does he see any impediments that prevent him or the Team from meeting the Sprint goal?
If necessary, the Team may meet immediately after the Daily Scrum Meeting, for any detailed discussions, or to re-plan the rest of the Sprint’s work.
Following are the benefits of Daily Scrum Meetings -
- Improve communication within the Team.
- Identify impediments, if any, in order to facilitate an early removal of the same, so as to minimize impact on the Sprint.
- Highlight and promote quick decision-making.
- Improve the Team’s level of knowledge
Sprint Review (2 hrs for 2 weeks projects / 4hr for 1month project)
Is held at the end of every sprint. to understand what was done in the sprint. Basesare to obtain feedback and progress unitedly. Attendees include the Scrum Team and key stakeholders, as invited by the Product Owner. The Product Owner explains what Product Backlog items have been completed during the sprint and what has not been completed. The Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved. The Team demonstrates the work that it has completed and answers questions, if any, about the Increment. The outcome of the Sprint Review is an updated Product Backlog, which defines the probable Product Backlog items for the next Sprint.
Sprint Retrospective(1 hr for 2 weeks project/ 3hr 1 month project)
The purpose of the Sprint Retrospective is to :
- Combine the learnings from the last Sprint, with regards to people, relationships, process, and tools.
- Identify the major items that went well and potential improvements.
- Creation of a plan for implementing improvements to increase product quality.
- The Sprint Retrospective is an opportunity for the Scrum Team to introspect and improve within the Scrum process framework so as to make the next Sprint outcome more effective.
Scrum Artifacts provide key information that need to be aware for understanding the product under development
The following artifacts are defined in Scrum Process Framework :
- Product Backlog
- Sprint Backlog
- Burn-Down Chart
- Increment
Product Backlog
Features, functions, requirements, enhancements, and fixes that are needed as part of the end product
Sprint Backlog
Is the set of product Backlog items selected for the sprint, plus a plan for delivering the product increment and realizing the sprint goal The Sprint Backlog is a plan with enough detail that can be understood but the Team to track in the Daily Scrum.
Increment
The sum of all the Product Backlog items completed during a Sprint combined with the increments of all previous Sprints. At the end of a Sprint, the new Increment must be a working product, which means it must be in a useable condition. The purpose of each Sprint is to deliver Increments of potentially releasable functionality.
Sprint Burn-Down Chart
Sprint Burn-Down Chart is a practice for trending the work expended by the Scrum Team. This has been proven to be a useful technique in monitoring the Sprint progress towards the Sprint Goal.
The Product Owner tracks this total work remaining at least every Sprint Review.
Conclusion
Scrum’s roles, events, artifacts, and rules are inevitable. If only some parts of Scrum are implemented, the result is not Scrum. Scrum needs to be implemented in its entirety and functions well if aligned with other techniques, methodologies, and practices.
Congratulations, if stay at this point , probably you have a little notion about SCRUM. Fore more details visit :
Tibi gratias ago pro Lectio.