Remove Cadence Remove Engineering Remove Software Review Remove Technical Review
article thumbnail

Release planning and predictable delivery

Scrum.org

TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Professional Developers create working software.

article thumbnail

Are These DevOps Obstacles Getting in the Way of Your Agile Transformation?

Leading Agile

As more and more companies scramble to untangle the code of their monolithic legacy software and get it into the cloud, strategic priorities are shifting. Leave with an actionable roadmap for aligning your technical practices with the work of the Transformation that you can begin implementing today.

Insiders

Sign Up for our Newsletter

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

article thumbnail

11 Proven Stakeholder Communication Tactics

Scrum.org

Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog.

article thumbnail

Troubleshooting in Lean-Agile Development

MPUG

It’s usually based on a cadence. As shown in the above figure, there is no regular timeboxed iteration, but incremental delivery can happen in cadence. When you fire a gun in the dark, it’s difficult to aim due to the lack of light. Developers, with all due respect to them, are generally optimistic people.

Lean 65
article thumbnail

Sprint Anti-Patterns

Scrum.org

Every activity required to achieve the Product Goal, such as Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, occurs within Sprints. This also applies to refactoring parts of the tech stack, exploring new technology that might be useful, fixing some bugs, or sharing knowledge with fellow teammates.

article thumbnail

Kanban to manage Complex/ Quick Moving Situations

Digite

That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals!

article thumbnail

28+2 Sprint Anti-Patterns Holding Back Scrum Teams

Scrum.org

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. This also applies to refactoring parts of the tech stack, exploring new technology that might be useful, fixing some bugs, or sharing knowledge with fellow teammates.

SCRUM 159