What is SCRUM?

Creating new product or feature is not an easy task. And having our product in a succeed marketplace is even more of a challenge. A good product can stable in this marketplace which fulfil customer need and simultaneously crating a business value to product. Scrum helps us to archive these goals. Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. It breaks large complex project to smaller ones. And reviewing and adopting along the way. Scrum helps to organize the team in well manner way and it helps to complete stuffs in minimum time.

        1. A product owner orders a product to some complex problem.

        2. During a sprint, the scrum team turns a section of work into an increment of value.

        3. The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.

        4. Repeat

History of Scrum

        • Scrum was as first introduced by professor Hirotaka Takeuchi and professor Ikojiro Nonaka                     in their 1986 Harvard Business Review article. In 1995 Software developers Ken  Schwaber                 and jeff Sutherland each presented their version of scrum which we are using today.

What is sprint?

        • Scrum team fix the timeline of product. When it fixed it cannot be extended. When the                             timeline is fixed the product, or the deliverable of project prioritize and delivered in two-                        week cycle. We called that cycle as sprint.

The Roles of Scrum team

Who is scrum master?

        • Scrum masters are the champions for scrum within their teams. They coach teams, product                     owners, and the business on the scrum process, and look for ways to fine-tune their practice                     of it. An effective scrum master deeply understands the work being done by the team and can                  help the team optimize their transparency and delivery flow. As the facilitator-in-chief,                             he/she schedules the needed resources (both human and logistical) for sprint planning,                             stand-up, sprint review, and the sprint retrospective.

Who is the Product owner?

        • The Product Owner (PO) is a member of the Agile Team responsible for defining Stories and                 prioritizing the Team Backlog to streamline the execution of program priorities while                             maintaining the conceptual and technical integrity of the Features or components for the                         team. Project owner is not only focus on stuffs to be completed but also, he manages                             business and market requirements.

Who is the Development team?

        • Set of members who working together to create a product. Development team has the                             freedom to organized themselves. And manage their own works to increase efficiency. 

The Scrum Artifacts

        • Artifact are physical records that provide project details. Scrum Artifact basically include                         What is Product backlog?

        • The product backlog is a list of new features, enhancements, bug fixes, tasks, or work                             requirements needed to build a product. It is compiled from input sources like customer                         support, competitor analysis, market demands, and general business analysis. It is a cross-                    team backlog that is maintained and curated by the product owner between sprint cycles and                  as any new ideas arise. It contains tasks that were once in an active sprint but deprioritized                     and moved to the backlog. 

What is Sprint backlog?

        • The sprint backlog is a set of product backlog tasks that have been promoted to be developed                 during the next product increment. Sprint backlogs are created by the development teams to                     plan deliverables for future increments and detail the work required to create the increment.

What is the Burndown chart?

        • A sprint burndown chart is not an official scrum artifact, but many teams use it to                                     communicate and track progress toward the sprint goal during the sprint. Burndown charts                     are graphs that display tasks completed over the duration of a sprint. Burndown charts are                     very useful in helping to gauge the active execution velocity of a team so they know whether                  they will complete what is planned or need to reprioritize the sprint tasks.

What is the Product increment?

        • A product increment is the customer deliverables that were produced by completing product                     backlog tasks during a sprint. It also includes the increments of all previous sprints. There is                 always one increment for each sprint and an increment is decided during the scrum planning                     phase. An increment happens whether the team decides to release to the customer. Product                     increments are incredibly useful and complementary to CI/CD in version tracking and, if                         needed, version rollback.

How does Scrum process work?

        • Scrum process starts with product owner. He is the person who represent the final user’s                         requirements and he has the authority to save what goes into the final product.  Product                         owner creates a product backlog which is a list of tasks and requirement the final product                         needs. And the product backlog must be prioritized.

        • Now the team which is the product owner and the scrum team get together for sprint planning                 which is when the entire team decides together what to work on from product backlog list.                     The Scrum process is based on iterative cycles called Sprints which typically last 2-4 weeks                 during which the product is designed, coded, and tested, while meeting every day to assess its                 progress (daily Scrum).

        • Along the way, the Scrum Master keeps the team focused on its goal.

        • At the end of the sprint, the work should be potentially shippable for showing to a                                     stakeholder.

        • The sprint ends with a sprint review and retrospective meetings.

        • As the next sprint begins, the team chooses another chunk of the product backlog and begins                 working again.

        • The project will either goes on until it is completed the entire wish list, or it will be stopped                     due to the time or budget has already been exhausted.

        • This goes on until the project is deemed complete, either by stopping to work (deadline,                         budget, etc.) or by completing the entire wish list.

What is the Scrum board?

        • This is the place where you can organize backlog and task that you are working on. Scrum                     board can be a white board with sticky notes for each task and is can be complicated                             software with task tracking and graphs. It depends on what you want to do and how want to                     do.