Gorilla Logic

NOVEMBER 10, 2021

Program Increment (PI) Planning, following the definition provided by Scaled Agile, “ is a cadence-based, face-to-face event that serves as the heartbeat of the Agile Release Train (ART), aligning all the teams on the ART to a shared mission and vision. ” . What is PI Planning? Imagine not losing an entire day of your sprint by planning it.

Technical Review 95

Technical Review Software Review Tools Programming 95

James Shore

JUNE 19, 2021

A typical Agile team consists of about 3-8 people, and perhaps 2-5 developers. It’s possible to double that size by using pair programming, described in “Pair Programming” on p.XX, along with the other Delivering zone practices described in Part III. Despite the name, it’s not a pure Scrum-based approach.

Agile 117

Agile Coaching Software Review Technical Review 117

Marcus Blankenship - Podcasts

JUNE 11, 2020

In this episode of Programming Leadership, Marcus and his guest, M. The results will be more engaged team members, scrum masters, and a way of working that converts skeptics and naysayers into Agile evangelists. Understanding extreme programming (XP) and why it’s valuable (23:41). Extreme Programming: [link]. Episode 46.

Agile 59

Agile Software Review SCRUM Weak Development Team 59

James Shore

OCTOBER 27, 2020

I see a startling parallel between DHH [David Heinemeier Hansson, creator of Ruby on Rails] and Kent Beck [creator of Extreme Programming]. That’s why they can create things like Extreme Programming and Rails, which really give the industry a jolt. The specific programming skills depend on the team’s purpose.

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

JUNE 6, 2018

There are two major ways to discover opportunities for cross-skilling: Kanban/Scrum Team Board. Kanban/Scrum Team Board. Skills Matrices and Scrum/Kanban Team Boards will only get you to the point where you know there is a need for growth, and where. A group of team members get together to practice with a programming challenge.

SCRUM 65

SCRUM Software Review How To Quality Assurance 65

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. What’s BDD?

Weak Development Team 95

Weak Development Team Technical Review Software Review Systems Review 95

James Shore

JUNE 2, 2021

Next, mix in even more bugs by with concurrent programming. In an early analysis of a company practicing a variant of Extreme Programming (XP), they reported an average reduction from 2,270 defects to 381 defects, an 83% decrease. Programmer errors occur when a programmer knows what to program, but makes a mistake. How about C?

Software Review 80

Software Review Systems Review Technical Review Test-Driven Development 80

James Shore

NOVEMBER 12, 2020

Hi, I’m your Scrum Master,” she says. Modern software development takes a lot of skills. Not just programming skills; people skills. If customer skills are about figuring out what to do, development skills are about figuring out how to do it. Programming. Pair Programming. Mob Programming.

Weak Development Team 86

Weak Development Team UI/UX Coaching Software Review 86

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

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? A couple decades ago, object-oriented programming promised this nirvana, but it never quite delivered.

Agile 69

Agile Software Review Technical Review Microservices 69

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. Growing Knowledge Skills Matrices and Scrum/Kanban Team Boards will only get you to the point where you know there is a need for growth, and where.

How To 52

How To Software Review SCRUM Quality Assurance 52

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. We use Extreme Programming as our model of how to develop software. They also love test-driven development, pairing, continuous integration, and evolutionary design. And were an XP shop.

Engineering 141

Engineering Software Review Weak Development Team Agile 141

James Shore

JUNE 7, 2021

Programmed? People’s decisions are an enormous factor in your development system. Programmed? For example, providing the wrong command-line argument to a program. For example, “engineer programs back-end to provide safe default when ServiceOmega times out” is an example of a “knowledge and mental models” event.

Analysis 72

Analysis Weak Development Team Software Review Systems Review 72

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.

Technical Advisors 52

Technical Advisors Continuous Delivery Software Review Systems Review 52

LeanEssays

JUNE 5, 2015

By contrast, product development in western countries focused on resource efficiency, completing each phase of development before starting the next, and following the original plan with as little variation as possible. In 1991 the University of Michigan began its Japan Technology Management Program.

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. Extreme Programming, in particular, saw an explosion of grass-roots interest among programmers. Get me some Agile.”. we were not a fan.

Agile 99

Agile Weak Development Team Development Team Review Development 99