Blog Cadence Controlling Software Review 
Scrum.org
MAY 16, 2024
This blog describes how Business Agility can be achieved with Product Management by moving up on the Org Topologies™ map. Due to their limited scope of ownership (tasks or features) and span of control (single team), all they can maximize is the utilization of their team’s capacity. But what value can the low-level PO maximize?
Scrum.org
JANUARY 5, 2021
Due to horrible time-management on my part, we could not answer all the questions in the webinar, so we are answering them in this blog instead. You might get more value from reading this blog if you watched the recording and reviewed the slides that are available on the webinar page - A Cycle Time Journey: 164 to 8 Days in 6 Months.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
SEPTEMBER 19, 2020
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.
Henny Portman
JULY 26, 2020
Furthermore, neither agile or scrum contemplates how the agile team should be connected to a larger organization and to external partners who will likely have differing development processes and cadences. Conducting a meeting: make the path visible and start down it and control the dialogue. The book is divided into four sections.
Scrum.org
APRIL 11, 2019
In this blog I want to share some common collaboration problems and solutions I experimented with. Delivering working software is perceived as an IT responsibility instead of a Business-IT collaboration. I was successful with optimising for feature size that could be delivered in a two-sprint cadence. Lack of product focus.
Digite
MARCH 12, 2018
split across different cities and even countries, though all speak the same language), and getting the know-how under control etc. 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!
Agilemania
DECEMBER 13, 2021
The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. Code Quality. Apply cadence and synchronize with cross-domain planning. Empirical process control. In the Scaled Agile Framework, every team member works diligently.
Expert insights. Personalized for you.
161 
Let's personalize your content