Remove Blog Remove SCRUM Remove Test-Driven Development Remove Weak Development Team
article thumbnail

5 Tips for Successfully Implementing Behavior-Driven Development in Your Team

Gorilla Logic

Have you ever been part of a team where tickets are hard to understand or don’t supply enough detail for the team to properly work? Experiences like these make many developers think about using Behavior-Driven Development (BDD). Know your team members You work with your team every day and know them well.

article thumbnail

Definition of Done vs. User Stories vs. Acceptance Criteria

Agile Pain Relief Notes from a Tool User

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. User Stories.

SCRUM 105
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

20 Deadline Management Tips Scrum Masters Should Consider

Codegiant

Like I conveyed in my “The Ultimate Workplace Productivity Guide You Should Read to Get Things Done” blog post, I love starting things off with a quote. While producing this blog post, I collaborated with our in-house software development team. Deadlines are any software development team’s biggest nightmare.

SCRUM 52
article thumbnail

20 Deadline Management Tips Scrum Masters Should Consider

Codegiant

Like I conveyed in my “The Ultimate Workplace Productivity Guide You Should Read to Get Things Done” blog post, I love starting things off with a quote. While producing this blog post, I collaborated with our in-house software development team. These days, packages are ever-changing.

SCRUM 52
article thumbnail

A Guide to Program Increment (PI) Planning: Why PI Planning is the greatest tool you can have

Gorilla Logic

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. ” . The team can focus on writing code. Allows teams to think ahead.