Scrum: An Overview & How It’s Used In Practice

Scrum Origin

What Is Agile?

Agile in a nutshell
  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan
  1. Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity — the art of maximizing the amount of work not done — is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  • Collaboration
  • Self-Management & Highly-Motivating Team
  • Communication
  • Focus on good quality product/software
  • Effectiveness & Efficiency
  • People as Focus

Scrum As An Agile Methodology

source: https://d112uwirao0vo9.cloudfront.net/wp-content/uploads/2019/09/Scrum-Method-1024x751.jpg

Scrum Values

  • Commitment: Scrum team must commit to achieving the goal for each iteration
  • Focus: Scrum team just focusing on doing the jobs of the sprint to achieve the goal
  • Openness/Transparency: Scrum team & stakeholder must be open to the progress and problems that happened along the way
  • Respect: Scrum team must respect each other
  • Courage: Scrum team must have the willingness to do a tough job

Scrum Roles

  • Product Owner: Managing & organizing the product backlog items. Communicating with stakeholders to ensure that the product backlog is aligned with what the stakeholder really wants & feasible to be implemented.
  • Scrum master: Ensure that the scrum team follows the scrum principles and making sure that the team keeps productive doing sprint tasks within the time span.
  • Development: Self-managing/Autonomous group of developers that focus on creating the product.

Scrum Artifacts

  • Product backlog: List of features that must be implemented in the future
  • Sprint backlog: List of features that must be done on certain iteration
  • Increment: Concrete stepping stone/milestone toward the goal.
product backlog items in our project

Scrum Flow & Its Implementation in PPL

  1. Sprint
  1. Scrum master explains the sprint backlog
  2. The scrum master asks the development team which backlogs wanna be taken from those sprint backlogs.
  3. Once the development team has chosen the backlogs for the sprint, the scrum master asks the development team to vote the story point for each chosen backlog. In this session, the development team usually discusses the feasibility of the backlog to estimate the story point. We use scrum poker as a platform for this kind of stuff. If one or more members of the development team choose story points that really far different from others, those members must explain the reason why do they vote for that point. The scrum master then tries to assign a story point that kind of middle point/median between those voted points.
  4. After the story points have been assigned to all chosen backlogs, the final step is the scrum master asks the development what tasks need to be done to fulfill all of the chosen backlogs. The tasks of the sprint are listed using GitLab issues.
  5. After the scrum master has broken down the tasks, the next step is for each member of the development team to choose several tasks from all of the sprint tasks. The scrum master task is to assign the task who’s in charge of the task in GitLab issues.
  6. Sprint planning finished
sprint tasks in our group project
result of the sprint review

When Not to Use Scrum

Stakeholder/Client Doesn’t Want Proactively Involve in Your Project

Scrum Team Doesn’t Embrace The Change

Scrum Team That’s Reactive Instead of Proactive

Agile In Practice

Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software & deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.

Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

left(before revision): right(after revision)

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Closing Notes

References

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Interesting Spark SQL function

R is Our Mighty Programming Language

How To Get Uranium Prices With An API

Migrating Pods with Containerized Applications Between Nodes…in the Same Kubernetes Cluster?

How to get started in web development?

Deploy Overleaf Community on your laptop

“If it turns out that this is incurable, would you marry me?”

Find out different Fun commands like sl, cowsay etc. in Linux from the Internet

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Krisna Ihsani

Krisna Ihsani

More from Medium

Agile — Why, When and How to Estimate

Implement Efficient ITSM Workflows By Enabling Direct Actions In Jira

What is Agile Project Management?

To-Be or Not-To-Be AGILE!