Agile Pain Relief Notes from a Tool User

JULY 18, 2012

When you still have development to test handoffs (i.e. before you start doing ATDD (Acceptance Test Driven Development), smaller stories enable more frequent handoffs and allow testers to work on smaller chunks of code. A number of reasons: Small stories provide focus and a short horizon for the team.

SCRUM 52

SCRUM Examples Technical Review Software Review 52

Codegiant

AUGUST 15, 2021

And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases. Most scrum teams don’t take these points into consideration while planning their sprints. Trust me — new bugs can occur at any point in time.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Codegiant

AUGUST 15, 2021

And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases. Most scrum teams don’t take these points into consideration while planning their sprints. Trust me — new bugs can occur at any point in time.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

James Shore

JUNE 19, 2021

Although this book is focused on individual Agile teams, many organizations have more than one development team, and they’re often dependent on each other to finish their work. A system of interdependent Agile teams is called large-scale Agile. The goal is to create your large-scale system with as few interdependencies as possible.

Agile 117

Agile Coaching Software Review Technical Review 117

Gorilla Logic

MARCH 17, 2023

It enhances your existing Agile approach , synthesizing Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). You start by defining the desired behavior of the software in terms of concrete examples or scenarios that describe the behavior of the system in a clear, concise way.

Weak Development Team 95

Weak Development Team Technical Review Software Review Systems Review 95

Agile Pain Relief Notes from a Tool User

JUNE 6, 2018

There are two major ways to discover opportunities for cross-skilling: Kanban/Scrum Team Board. Kanban/Scrum Team Board. Demonstrates that in any system where there is a bottleneck, the rest of the system should be subordinated to the bottleneck until the bottleneck is cleared. Skills Matrix. Skills Matrix.

SCRUM 65

SCRUM Software Review How To Quality Assurance 65

James Shore

OCTOBER 27, 2020

Not just spending money—that’s comparatively easy—but making real, meaningful changes to organizational structures, systems, and behaviors. A team composed of many of the same developers, at the same company, using the same Agile process, later produced a product with compelling value in one-fifth the time. well, that’s because it is.

Agile 132

Agile Software Review Coaching Weak Development Team 132

James Shore

JUNE 2, 2021

How about a real-time embedded system? This is how it turns out: The GMS team delivered this product after three years of development, having encountered a total of 51 defects during that time. Test-Driven Development. Test-driven development is your defect-elimination workhorse.

Software Review 80

Software Review Systems Review Technical Review Test-Driven Development 80

Silk and Spinach

OCTOBER 6, 2016

In many of them I see a familiar pattern: The managers and business analysts are sent on courses and sent to conferences and given books to read; most of them change their job title to things like Scrum Master or Product Owner; they create their plans using “stories” written on post-it notes, and they organise their projects into Sprints.

Development 60

Development Agile Test-Driven Development SCRUM 60

LeanEssays

JULY 16, 2015

Once you get past the sales pitches and confirmation biases, it doesn’t take much research to discover that agile and Scrum don’t have such a great track record. Question 1: Should you use Scrum or Continuous Delivery? Yet without a solid foundation in the technology that produces great systems, agile is pretty hollow.

Agile 69

Agile Software Review Technical Review Microservices 69

Marcus Blankenship - Podcasts

JUNE 11, 2020

The results will be more engaged team members, scrum masters, and a way of working that converts skeptics and naysayers into Agile evangelists. Engaged scrum masters are essential for long-term change (26:49). Convincing skeptics to try a new system (32:12). Scrum: Novice to Ninja: [link]. Show Notes.

Agile 59

Agile Software Review SCRUM Weak Development Team 59

Agile Pain Relief Notes from a Tool User

DECEMBER 9, 2019

jpg'; One of the more frequently asked questions in my Scrum workshops is around the difference between Definition of Done and Acceptance Criteria , and how they relate to User Stories. While Acceptance Criteria is a commonly understood concept in software development, Definition of Done is unique to Scrum.

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Codegiant

APRIL 14, 2020

Now, let’s check which Agile development methodology would be most suitable for your team: Different Agile Methodologies Scrum ?—?it’s It’s an iterative agile process that typically consists of three Scrum roles and time boxes. Also, in the Scrum project management, you have a Product Owner, Scrum Master, and Scrum Team.

Agile 52

Agile SCRUM Software Review Technical Review 52

Agile Pain Relief Notes from a Tool User

JUNE 5, 2018

jpg'; As we discussed in Specialists Are Overrated , developing cross-skills and T-Shaped" people in a team has many benefits for the team/organization itself, the customer, and the individual. A Skills Matrix is a self-reporting system where team members provide their own estimate of their skill in a specific area.

How To 52

How To Software Review SCRUM Quality Assurance 52

James Shore

NOVEMBER 12, 2020

Hi, I’m your Scrum Master,” she says. The back-end systems never quite work the way you thought they would, either, and it takes forever for Ops to update the development environment with new builds. Until then, development on an Agile team looks similar to development on any other team. Test Driven Development.

Weak Development Team 86

Weak Development Team UI/UX Coaching Software Review 86

Capgemini

MARCH 27, 2020

Tomorrow’s leaders are already starting to transform towards new delivery models that will enable them to develop more exploratory and adaptive strategies. The information system (IS) of the future supports this approach and delivers an abundance of innovative services in record time. That’s not all.

Agile 52

Agile Weak Development Team Software Review UI/UX 52

James Shore

JANUARY 10, 2025

This is a transcript of my keynote presentation for the Regional Scrum Gathering Tokyo conference on January 8th, 2025. They also love test-driven development, pairing, continuous integration, and evolutionary design. They tend to be passionate, senior developers. How are you measuring productivity?

Engineering 141

Engineering Software Review Weak Development Team Agile 141

James Shore

JUNE 7, 2021

For an excellent and practical guide to incident response, see Site Reliability Engineering: How Google Runs Production Systems [Beyer et al. Failure is a consequence of your entire development system. In reality, failure is a consequence of the entire development system in which work is performed.

Analysis 72

Analysis Weak Development Team Software Review Systems Review 72

LeanEssays

FEBRUARY 18, 2014

In a lean environment, the leader’s role is to set up strong teams, to be sure, but it is also to devise a system – let’s call it a goal system – which assigns goals to teams. So it’s clear that the start of a goal system is a system-level, unifying goal. So we need to look elsewhere for ways to set up a goal system.

Technical Advisors 52

Technical Advisors Continuous Delivery Software Review Systems Review 52

LeanEssays

JUNE 5, 2015

Instead, Modig and Ahlström demonstrate that lean is about flow efficiency – that is, the efficiency with which a unit of work (a flow unit) moves through the system. In my case, the dental system was focused on the efficiency of the lab’s milling machine – no doubt an expensive piece of equipment. Consider our dental experience.

Software Development 55

Software Development Software Review Software Development 55

James Shore

AUGUST 19, 2020

So, what allows me to do this—what allows me to do this show, this software development show every week, and what allows me to write this book—is the people who hire me for training and consulting. First, business analysts would interview stakeholders and document the system requirements. In theory, anyway.). Get me some Agile.”.

Agile 99

Agile Weak Development Team Development Team Review Development 99