What is Scrum?

What is Scrum?

The Scrum Guide defines Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems”.

So what are Empiricism and Lean thinking?

    1. Scrum is simple and is based on empiricism and lean thinking.
    2. Empiricism allows you to make decisions based on what is observed.
    3. Lean thinking is all about removing waste and “Focusing on the most important things”. 

How many Pillars and Values are in Scrum? 

  1. Scrum is supported by 3 Pillars and 5 Values
    1. Scrum Pillars – Transparency, Inspection, Adaptation
    2. Scrum Values – Commitment, Focus, Openness, Respect, and Courage

 

Scrum Team

Excited colleagues celebrating success as a team, standing behind a glass wall with colorful stickers at a scrum event.

 

What are the roles in Scrum?

  1. Scrum requires a Scrum Master, Product Owner, and the Scrum Team
    1. Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide
    2. Product Owner works on the Product Backlog
    3. Scrum Team focuses on executing the backlog items. Developers are the people in the Scrum Team.

How many events are in Scrum?

  1. Sprint is a container for all the events. In total, we have 5 events – sprint, sprint planning, daily scrum, sprint review, sprint retrospective.
  2. Backlog Refinement is not an official event.

What value does the Scrum Team produce?

Scrum’s artifacts represent work or value. Each artifact contains a commitment !!!

  • Product Backlog –> Product Goal
  • Sprint Backlog –> Sprint Goal
  • Increment –> Definition of Done

Watch the video on Scrum Values

Upcoming CoursesScrum at Scale FundamentalsScrum at Scale

 

 Get in touch

What is an Agile Release Train in SAFe?

Agile Release Train Scaled Agile Framework SAFe

What is an Agile Release Train?

The below video essentially covers how an agile release train can be built while implementing the Scaled Agile Framework – SAFe 5.0

  • Overview of SAFe Scaled Agile Framework – SAFe 5.0
    • Big Picture
    • What is an Agile Release Train?
    • ART Goals
    • How are they Organised?
  • Identify Value Streams
    • Operational Value Stream
    • Development Value Stream
    • ART Delivers Value Streams
  • Organize Around Value
    • ART Roles
    • Team Iterations
  • Where do I start?
    • Implementation Roadmap
    • First ART
  • Q&A’s

 

Effective User Stories with BDD ( Behavior Driven Development )

  • BDD is about implementing the software by describing its behavior from the perspective of its users.
    • “It’s finding places of misunderstanding and filling it with understanding”
  • Behavior-driven development does more than improve communication and reduce errors in production.
  • It provides an up-to-date record of an application’s features.
  • In other words, it produces living documentation that’s readable by both business and technical teams.
    • This living documentation can be invaluable for many parts of the organization since it shows exactly what the application is supposed to do and proves that it can do it.

Behavior-driven development is a game-changer for many Agile teams. You can watch the video to get more insights.

 

Scaling Patterns

efficient agile logo

What are Patterns?

  • A repeatably applicable solution to a problem that arises in a specific context.
  • Patterns come from our reflective observations about our hands-on interactions to solve problems in the world.

No Patterns are Stand Alone! Changes we make in one place may have unintended side effects elsewhere

The below video covers various aspects of Scaling Scrum Patterns

Looking for a Scrum@Scale Course, Book Here: https://www.efficientagile.com/certified-scrumscale-practitioner/

Scrum@Scale transforms organizations into #Agile enterprises, right from Fortune 100 companies to start-ups. Created by the inventor of Scrum, #JeffSutherland, it naturally extends the core Scrum framework to deliver hyper-productive results across industries and disciplines. This includes industries like software, hardware, services, operations, and R&D. Explore how you can scale scrum across your organization or department using #Scrum@Scale.

 

Scrum@Scale – Scaling the Scrum Master

Dr. Jeff Sutherland developed Scrum@Scale based on the fundamental principles behind Scrum, Complex Adaptive Systems theory, game theory, and his work in biology.

How you take scrum itself that is completely consistent with the scrum guide on an individual team or apply that to hundreds of teams without having introducing anything that’s not scrum.

Remember if you do introduce any extra roles or if you introduce any teams that are not scrum teams – That is going to slow down implementation and cripple the transformation”. You can watch the below video to get more insights on Scrum@Scale.

Looking for a Scrum@Scale Course, Book Here: https://www.efficientagile.com/certified-scrumscale-practitioner/

 

 

Scrum@Scale transforms organizations into Agile enterprises, right from Fortune 100 companies to start-ups. Created by the inventor of Scrum, Jeff Sutherland, it naturally extends the core Scrum framework to deliver hyper-productive results across industries and disciplines. This includes industries like software, hardware, services, operations, and R&D.

Scrum@Scale – Getting The Foundations Right

Scrum@Scale transforms organizations into Agile enterprises, right from Fortune 100 companies to start-ups. Created by the inventor of Scrum, Jeff Sutherland, it naturally extends the core Scrum framework to deliver hyper-productive results across industries and disciplines. This includes industries like software, hardware, services, operations, and R&D.

Looking for a Scrum@Scale Course, Book Here: https://www.efficientagile.com/certified-scrumscale-practitioner/

 

Scrum@Scale – Scaling the Product Owner

Product Owner is one of the key roles within Scrum.

Watch the below video to get some insights “How you can scale scrum across your organization or department using Scrum@Scale.” Some of the topics covered are

  • Scaling the Product Owner – the “what”
  • Understanding the components in PO Cycle
  • PO Scaled Roles & Events
  • Understand the PO Organisation
  • Case Studies
  • Other Scaling Frameworks

Looking for a Scrum@Scale Course, Book Here: https://www.efficientagile.com/certified-scrumscale-practitioner/

 

 

Scrum@Scale transforms organizations into Agile enterprises, right from Fortune 100 companies to start-ups. Created by the inventor of Scrum, Jeff Sutherland, it naturally extends the core Scrum framework to deliver hyper-productive results across industries and disciplines. This includes industries like software, hardware, services, operations, and R&D.

Automating Tests within the Sprint

Does your “Definition of Done” include “Automated tests” or does most of the QA work get carried forward sprint after sprint?

Most Scrum teams i.e. nearly 80-90 percent of them get into this phase at least once!! You are not Alone!

Test Automation is a key factor to incorporate in any Agile teams. If you are spending a lot of time performing manual testing during every sprint, you are never going to get things “Done”.

With manual testing in place in every sprint,

  • You may spend ‘n’ hours in Sprint-1

  • n+3 hours in Sprint-2

  • n+5 hours in Sprint-3 etc.

The time spent testing new features and any changes to the existing features will increase the manual test effort. The amount of time spent on regression testing will also increase drastically.

By the time you decide to launch to the marketplace, the “testing effort may take weeks to complete”.

Will automation help overcome this issue? Yes…

  • Identify tests that are repetitive or run frequently in the sprint, as they become the best candidate for automation. Automate simple tests.

  • Stay up to date with all the tests and get the product backlog items automated slowly and this will bring down the manual test effort gradually.

  • Have a well-defined “definition of done”.

Why not Automate as early as possible?

Get your Sprint 0 to do all the groundwork and shape up the test environment, strategy, tool selection, BDD, TDD etc…

Let the Developer and QA work on a story together….say you have 5 Acceptance Criteria for a story and it may take 3 days for the story to be completed.

  • Dev / QA –> Work on AC-1 (acceptance criteria 1 from the feature)

  • Dev writes the code to cover AC-1 & QA writes the automated tests, prep test cases, test data for AC-1

  • Dev checks-in code for AC-1 & QA checks-in automated test code for AC-1

  • Let the CI (Continuous Integration) take care of the rest, tests are executed against the Dev code. Fully Tested and its “Done”

  • Continue the similar pattern for remaining Acceptance Criteria, AC-2 to AC-5.

On the 3rd Day of the Sprint,

We have Dev “Done”, QA “Done” and Story/feature is “Done” “Done” 🙂

Avoid the “Mini Waterfall” or so-called waterfall-agile “W-Agile” approach that happens in the last few days of the sprint.

Upcoming Courses

Select your currency
EUREuro