Introduction to Scrum:
Full stack developer dedicated to crafting seamless user experiences. I thrive on transforming complex problems into elegant solutions!
Delivering quality products on time in the fast paced world we live in today, requires a structured yet flexible approach. The Scrum framework is a popular agile project management framework that strengthens team organization, collaboration and the ability to change course in short timeframes.
To better understand the system, this blog outlines a basic overview of scrum.
What is Scrum?
Scrum is a lightweight agile framework used for product development. It is focused on delivering small, incremental updates with a collaborative, accountable and continuously improving approach.
What are the 'key components' of Scrum? - Scrum has several key elements to guide how teams operate;
Scrum Team - Product Owner - The individual responsible for defining the product vision, prioritization of work ( Product Backlog), and determining the team is building the correct thing.
Scrum Master- A member of the team who facilitates the sprint process, removes any obstacles to progress and ensures the team is compliant with Scrum principles.
Development Team- The people who are responsible for delivering a working product increment at the end of the sprint.
Artifacts - Product Backlog - a working document and evolving list of features, tasks, and improvements for the team to complete work.
Sprint Backlog - a list of commit multiple things from the Product Backlog that the team will complete as a commitment in a duration of a sprint.
Increment - the total sum of all done work at the end of a sprint. It should be a working product.
Events - Sprint - a fixed duration of time ( normal duration is between 1-4 weeks) where the team will complete a number of tasks. Sprints happen immediately one after each other without breaks in time.
Sprint Planning - at the beginning of each sprints, the team will determine which items to complete in the upcoming sprint.
Daily Stand up - a brief meeting to reflect briefly on what was done yesterday, what will be done today and roadblocks.
Sprint Review - Once the sprint has completed, the team holds a review to demonstrate the completed work to stake holders and receive feedback.
Sprint Retrospective - A engaged conversation for the team to reflect for them to reflect and to facilitate conversations about what went well and what could of been improved in the sprint.
