Agile Pain Relief Notes from a Tool User

JUNE 26, 2012

There was a pause and Scrum Master Steve asked, What do you know about our estimation process? Focus improvement efforts on getting better at doing the work, i.e. learn Test Driven Development and make your build run faster. Kirby just looks around in confusion. The reply was, Nothing. What Estimation tips do you have?

SCRUM 52

SCRUM Examples How To Test-Driven Development 52

Agile Pain Relief Notes from a Tool User

DECEMBER 10, 2019

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 107

SCRUM Software Review Weak Development Team Technical Review 107

Agile Pain Relief Notes from a Tool User

FEBRUARY 27, 2012

They agree to raise the issue in the next Daily Scrum. In addition they discovered that their existing Unit Tests only provide 10% Code Coverage. Day 2 During Daily Scrum Ian describes what theyve learned from installing Sonar and trying to configure PMD. Lets give them some reading/study options.

SCRUM 52

SCRUM Examples Technical Review Software Review 52

Agile Pain Relief Notes from a Tool User

JUNE 6, 2018

That’s all fine and good to say, but how do you figure out where to start? There are two major ways to discover opportunities for cross-skilling: Kanban/Scrum Team Board. Kanban/Scrum Team Board. If you’re unfamiliar with how a Team Board works or what it looks like, I posted an example of a Kanban Board previously on this blog.

SCRUM 65

SCRUM Software Review How To Quality Assurance 65

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 masters don’t take these points into consideration while planning their sprints. new bugs can occur at any point in time. And value is what you’ll receive?—?but

SCRUM 52

SCRUM Software Review Weak Development Team Technical Review 52

Agile Pain Relief Notes from a Tool User

JULY 18, 2012

import Figure from '@/components/global/figure.astro'; import Photodune2996181DifferentColorsSlicedAppleXs from 'src/content/blog/scrummaster-tales-story-splitting-fun/images/photodune-2996181-different-colors-sliced-apple-xs.jpg'; Picking up from: Learning How to Estimate The team are still in the Backlog Grooming/Refinement session.

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

Net Objectives

JULY 9, 2018

The promoted belief that you should focus on the framework & then learn how to do this later is not just self-serving, it is wrong. Most Scrum courses teach story writing w/ "As a I want so that I get ". In any event, it does not provide a way to get to clear acceptance criteria. That has to be taught separately. .

SCRUM 40

SCRUM Training Test-Driven Development Construction 40

Agile Pain Relief Notes from a Tool User

JUNE 5, 2018

import Footnotes from '@/components/global/footnotes.astro'; import Figure from '@/components/global/figure.astro'; import AgilePainReliefKanbanBoardMockupBV21024x609 from 'src/content/blog/how-to-cross-skill-and-grow-t-shaped-team-members/images/AgilePainRelief_KanbanBoard_Mockup_B_v2-1024x609.jpg';

How To 52

How To Software Review SCRUM Quality Assurance 52

Gorilla Logic

MARCH 17, 2023

It enhances your existing Agile approach , synthesizing Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). At a minimum, your stakeholders are likely to include: technical leads, QA leads, Product Owners, Scrum Masters, developers, QA engineers.

Weak Development Team 95

Weak Development Team Technical Review Software Review Systems Review 95

James Shore

JUNE 19, 2021

Remember, coaches are the people who help each team learn how to apply Agile ideas and practices.) Dedicate a member of each team to learning how to be a coach, and back them up with experienced coaches—possibly hired for that purpose—who work with two or three teams simultaneously. Test-Driven Development.

Agile 117

Agile Coaching Software Review Technical Review 117

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). Scrum: Novice to Ninja: [link]. So, let’s take one of them, I think you said unit testing, is that right?

Agile 59

Agile Software Review SCRUM Weak Development Team 59

James Shore

OCTOBER 27, 2020

This frustration can lead to teams being redirected away from learning how to be Agile, and solely focused on delivering software, before they’ve finished learning. It can take months for team members to figure out how to work most effectively together, so keep teams together for as long as possible. Long-lived.

Agile 132

Agile Software Review Coaching Weak Development Team 132

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

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

Gorilla Logic

NOVEMBER 10, 2021

But can we go deeper into what PI planning is and how it works? In this article, you will learn what PI Planning is, what the benefits of PI planning are, and discover some best practices for how to do PI planning well. Keep in sync: The PO sync up meeting and the scrum of scrums are not only for the execution of the PI.

Technical Review 95

Technical Review Software Review Tools Programming 95

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? We have learned a lot about how to deal with dependencies over the last few years.

Agile 69

Agile Software Review Technical Review Microservices 69

James Shore

NOVEMBER 12, 2020

Hi, I’m your Scrum Master,” she says. They choose features; decide how to group features into releases; collaborate with the rest of the team to create an achievable plan; condense the team’s plan into a roadmap that can be shared with stakeholders; and help the team adapt their plans in response to feedback and changing business conditions.

Weak Development Team 86

Weak Development Team UI/UX Coaching Software Review 86

James Shore

JUNE 2, 2021

QSM found 11% defect reduction and 58% schedule reduction on a Scrum team; 75% defect reduction and 53% schedule reduction on an XP team; and 75% defect reduction and 30% schedule reduction in a multi-team analysis of thousands of developers. Test-Driven Development. How to Fix a Bug. Energized Work.

Software Review 80

Software Review Systems Review Technical Review Test-Driven Development 80

Capgemini

MARCH 27, 2020

This can be achieved using methodologies like Scrum, Kanban, SAFe®, DevOps etc, leading to responsive business prioritization and short delivery iterations. That’s because the significant gains in development speed and release frequency you need to be a responsive, agile organization have ramifications for the overall delivery quality.

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. Introduction People Internal Quality Lovability Visibility Agility Profitability How are you measuring productivity? How are you measuring productivity? They tend to be passionate, senior developers.

Engineering 141

Engineering Software Review Weak Development Team Agile 141

LeanEssays

FEBRUARY 18, 2014

One of the things Scrum has contributed to the practice of software development is the idea that small autonomous teams perform much better than large project teams or single-discipline teams that work in sequence. The Theory of Constraints can help here.

Technical Advisors 52

Technical Advisors Continuous Delivery Software Review Systems Review 52

James Shore

JUNE 7, 2021

Either way, once the dust has settled and things are running smoothly again, you need to figure out what happened and how you can improve. The details of how to respond during an incident are out of the scope of this book. You’re ready to decide how to improve your development system. This is incident analysis.

Analysis 72

Analysis Weak Development Team Software Review Systems Review 72

LeanEssays

JUNE 5, 2015

To counter sequential processes and the long integration and defect removal phase, agile software development practices focused on fast feedback cycles in these areas: Test-driven development: Start by writing tests (think of them as executable specifications) and then write the code to pass the tests.

Software Development 55

Software Development Software Review Software Development 55

James Shore

AUGUST 19, 2020

So Shane and I are rewriting the book for a modern audience: “Here’s what Agile really is, and here’s how to make it really work.” We’re keeping the pragmatic, down-to-earth, “here’s how to do it” approach, but we’re updating absolutely everything else. In the rest of this book, I’ll show you how to apply Agile ideas for real.

Agile 99

Agile Weak Development Team Development Team Review Development 99