Scrum.org

AUGUST 18, 2022

In Kürze: HoA #43: Outcome-Based Product Planning mit Jeff Gothelf. Outcome-Based Product Planning hat Jeff Gothelf eines verdeutlicht: „Roadmapping ist im Zeitalter der agilen Produktentwicklung ein fehlerhaftes Konzept. Sehen Sie sich das Video jetzt an: Jeff Gothelf: Outcome-Based Product Planning — Hands-on Agile 43. ??

Agile 202

Agile Planning Software Review 2022 202

Accidental PM

MARCH 30, 2025

The core principles of Agile are outlined in the Agile Manifesto , which emphasizes the importance of individuals and interactions over processes and tools, working solutions over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.

Certification 75

Certification SCRUM Agile Technical Review 75

ProjectManager.com

MARCH 21, 2019

He achieves this with a mixture of agile, lean and lead, UX design and design thinking startup frameworks. For example, a user story might be written like this, “As a project manager, I want to print out my Gantt chart, so I can review it regularly on my office wall.” Related: How to Plan a Successful Product Launch.

Technical Review 386

Technical Review 2005 Software Review Development Team Review 386

Leading Answers

NOVEMBER 1, 2020

Yet we rarely see agile communications management plans. Why We Have Communication Management Plans Projects can be time-consuming and costly, and tie-up valuable employees for long periods with no guarantee of the outcome initially hoped for. This is where a good communications management plan comes in. Why is this?

Agile 135

Agile Planning Underperforming Technical Team Development Team Review 135

Agilemania

SEPTEMBER 15, 2022

Lean Portfolio Management (LPM) involves connecting strategy to execution by using lean principles. Budgets are allocated to execute an enterprise’s strategy by portfolio management teams. Business agility can be improved by combining LPM and agile development practices. Review of strategy alignment.

Lean 98

Lean Cadence Development Team Review Leadership 98

The IIL Blog

JULY 24, 2024

Predictive, Agile, and Lean/Kanban form the boundaries. An adaptive approach with empowered, self-organizing teams. Lean/Kanban. Gate reviews mark the completion of each phase. A typical pattern is the overlapping of design with development, and development with testing. Hybrid is the vast interior space.

2024 78

2024 Lean Software Review Development Team Review 78

Scrum.org

MAY 4, 2020

We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum. Source : Scrum Guide 2017.

SCRUM 215

SCRUM Agile Technical Review Development Team Review 215

Scrum.org

SEPTEMBER 24, 2021

But experience shows that getting together at least once per month to plan work is not unreasonable. Meeting again to discuss what the Developers accomplished at least once per month is also reasonable. And a quick discussion with the Scrum Team to talk about ways to improve how everything is working–that is, frankly, invaluable. .

SCRUM 240

SCRUM Software Review Lean Leadership 240

Scrum.org

AUGUST 3, 2020

In the short term, communication and proactive planning is key. For a longer-term, more empowering state, consider cross-training, opening up permissions, organizational design changes, even hiring and team forming strategies. Plan at least 2-3 cycles ahead so that developers can help identify dependencies early.

Underperforming Technical Team 253

Underperforming Technical Team Technical Review Software Review Development Team Review 253

Scrum.org

FEBRUARY 10, 2022

Bitte beachten Sie, dass ich Grammarly verwendet habe, um Tippfehler und Zeichensetzung zu korrigieren: While the cross-team big room planning is very useful, in my experience, SAFe is top-down. A dependency board used to be a good way to figure out what dependencies to eliminate; now, it only encourages people to “plan better.”

Lean 213

Lean Software Review 2022 Technical Review 213

Leading Answers

JUNE 22, 2022

We can create backlogs and release plans all we like, but until there is a motivated team with a shared vision of the end goal, it is like trying to push a rope—ineffective. Leadership is focused on creating the pull from the team and giving the team the goal and tools to overcome obstacles.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Energy 193

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. When a weak Development Team meets a commanding Product Owner, focusing on shipping new features, the team may end up as a feature factory, churning out new code while neglecting the technical foundation.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Project Bliss

MAY 10, 2017

Responding to change over following a plan. Source: Manifesto for Agile Software Development , Working software, collaboration, and responding to change are valued more highly than process, documentation, and following a rigid plan. Agile processes promote sustainable development.

Software Development 191

Software Development Software Developers Software Review Agile 191

Scrum.org

JUNE 2, 2024

Recursos Sugeridos para aprender los fundamentos: Manifiesto Agile : AgileManifesto.org Libros : “Scrum: The Art of Doing Twice the Work in Half the Time” de Jeff Sutherland “Agile Estimating and Planning” de Mike Cohn. Scrum: Roles : Product Owner, Scrum Master, Development Team. La guía Scrum 2.

Agile 194

Agile 2001 SCRUM Development Team Review 194

The IIL Blog

OCTOBER 17, 2023

Agile team A cross-functional group of individuals (e.g., Product Owner, Scrum Master, Development team members) who work collaboratively to deliver value in an Agile project. Backlog A list of tasks, features, or requirements to be addressed by an agile project manager or team and is often associated with Agile methodologies.

Development Team Review 148

Development Team Review Project Life Cycle Underperforming Technical Team Estimate 148

Scrum.org

NOVEMBER 6, 2018

When it comes to Scrum Teams this means a tough discussion during Sprint Review of which PBIs we want to freeze, and taking that into account during the next Sprint Planning. For a Scrum Team, this again means looking at both the high-level PBIs in the Product Backlog and Sprint-level PBIs. . Differentiated Service.

Process 172

Process Development Team Review SCRUM Energy 172

Scrum.org

JANUARY 9, 2020

I am actively forming the opinion that this is the wrong term to be used both in how various assessments assess understanding and by practitioners in the agile community. However, with assessments for certification in scrum by Scrum.org, the preceding explanation would cover the required understanding.

Underperforming Technical Team 159

Underperforming Technical Team Infrastructure Development Team Review Lean 159

Scrum.org

FEBRUARY 7, 2022

Please note that I used Grammarly to correct typos and punctuation: While the cross-team big room planning is very useful, in my experience, SAFe is top-down. Executives that are not close to the customer problems make the decisions at the portfolio level, and teams execute, which can lead to disengaged teams.

Lean 183

Lean Software Review 2022 Technical Review 183

Digite

MARCH 12, 2018

We started with a single Kanban board, but with 2 separate swim lanes for the product manager and the dev team – see below – Planning Lane for the Product Owner. Dev Lane for the main dev activity. every week or less, and we have a single workflow between Dev and Ops as you will see below.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Scrum.org

FEBRUARY 1, 2021

(All Scrum team members need to communicate with stakeholders and customers to avoid losing critical information in translation. That is a reason for having, for example, the Sprint Review with stakeholders and customers.) ????. You will] challenge technical decisions of engineers and review and evaluate deliverables in detail.” (The

Technical Review 209

Technical Review 2020 SCRUM Development Team Review 209

Scrum.org

FEBRUARY 21, 2023

Additionally, I have a strong background in product discovery, which involves identifying customer needs, validating product ideas, and conducting experiments to inform product development decisions. Background : As the “Manifesto for Agile Software Development” states, it is mainly about adaptability over following a plan.

ChatGPT 172

ChatGPT Development Team Review Technical Review SCRUM 172

Scrum.org

JULY 29, 2019

It is defined in the Scrum glossary as follows: An indication of the average amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Development Team for use within the Scrum Team. Invite your manager to the Sprint Review. And that's important!

Technical Review 181

Technical Review Underperforming Technical Team Development Team Review Software Review 181

Scrum.org

JUNE 11, 2019

In most of the success stories, the involvement was not limited to the Sprint Review. Often, Development Teams also refined items with stakeholders, invited them to join Sprint Planning or visited them at their workplaces to better understand what they needed. By making active experiments transparent (e.g.

SCRUM 193

SCRUM Development Team Review Software Review Lean 193

Scrum.org

AUGUST 17, 2020

Product discovery using the Design Thinking, Lean Startup, or Lean UX frameworks help, but in any case, a good Scrum Master will want the Scrum Team to be a part of this process (whether by participating in user interviews or running experiments). There is greater respect among stakeholders for the product delivery teams.

SCRUM 234

SCRUM Technical Review Software Review Agile 234

Scrum.org

FEBRUARY 18, 2020

In two other blog posts, I covered how this can make your Sprint Retrospective more effective , and also how it can improve your Sprint Planning. The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. “The

SCRUM 203

SCRUM Development Team Review Software Review Lean 203

Agilemania

NOVEMBER 8, 2022

The agile release plan helps in aligning the teams by addressing multiple aspects that can contribute to creative and innovative problem-solving. Your agile release plan will ultimately show you what you can expect out of each sprint and ensure your efforts are laser-focused. What is an Agile Release Plan?

Agile 98

Agile Planning Software Review Technical Review 98

Scrum.org

FEBRUARY 14, 2019

And instead of adapting to the continuous value of product coming from the Scrum Team, the organization starts resisting the product or the team delivering it. It's just one of the examples that can occur when you're moving from a plan-driven approach to a continuous value delivery and empirical approach like Scrum. Conclusion.

SCRUM 172

SCRUM Development Team Review Lean Risk Management 172

Scrum.org

FEBRUARY 25, 2024

Reassigning Team Members : Frequently moving team members between Scrum Teams disrupts the building of trust and undermines the stability and effectiveness of teams​​. In the absence of this feedback, teams may engage in gold-plating under the assumption that they are adding value.

SCRUM 226

SCRUM ChatGPT Technical Review Development Team Review 226

Planview

JUNE 1, 2021

It can be challenging to expand Agile practices beyond IT and development teams. At the same time, our traditional planning processes cannot keep up or sustain us anymore: The annual plan is most on-strategy the day you finish it. Every quarter that goes by, the plan becomes less relevant.

Cadence 148

Cadence Logistics Lean Agile 148

Scrum.org

JANUARY 14, 2021

Lean/Agile Leadership. Both SAFe and Scrum/Nexus emphasize the need for a different style of leadership - leaders who serve, have a growth mindset, lead by example, live and breath Lean/Agile principles and practices, and strive for relentless improvement. . The Nexus reviews, retrospects, plans, and refines together every Sprint.

Cadence 107

Cadence Technical Review Development Team Review Lean 107

TrustRadius Project Management

FEBRUARY 21, 2019

This methodology breaks a software development project into incremental stages, slowing building on successive stages with what are called “sprints”. Overall, both can be beneficial to a software development team. The full scope of the project is agreed upon by the development team and their customers in advance.

Software Review 132

Software Review Agile Development Team Review Software Development 132

nTask

AUGUST 22, 2019

The term Agile refers to a way of managing projects that incorporates constant improvement, scope flexibility, team involvement, and delivering crucial quality products. This method often results in low-quality products due to delays in milestones, financial issues and lack of prioritized characteristics for the products.

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

Scrum.org

MARCH 20, 2024

how many Scrum teams do we need, who should be on each Scrum team) Artifacts: Where should the artifacts be stored in alignment with organizational policies? Developers should work with the Product Owner to size higher ordered Product Backlog items so that they can be done within one Sprint.

SCRUM 202

SCRUM 2020 2024 Development Team Review 202

MPUG

DECEMBER 28, 2020

The new guide clearly informs that Sprint Reviews should not be considered “gates” for releasing value. As there can be multiple Increments, the sum of all these Increments are presented to the (key) stakeholder at the Sprint Review. The diamond shapes in the cadence stream denote the Sprint Reviews. Lean Thinking.

Cadence 116

Cadence SCRUM 2020 Agile 116

Scrum.org

OCTOBER 10, 2018

Indeed, the range from a Monte Carlo forecast can be more accurate and useful to a team in Sprint Planning than an absolute value, such as an average velocity or burn rate projection. In our earlier example, we knew the team velocities for seven Sprints, which were 114, 143, 116, 109, 127, 153, and 120 points. days or less.

Underperforming Technical Team 163

Underperforming Technical Team Technical Review Development Team Review Estimate 163

Leading Answers

JANUARY 16, 2021

Prioritizing based on business value is an example of the lean concept of 'Taking an Economic View of Decision Making.' ' In deciding which feature to develop first, those with the highest economic value are selected. I do not think the teams have been weak at threat avoidance. Risks Actions in the Backlog.

Risk 145

Risk 2006 Underperforming Technical Team 2012 145

Scrum.org

JULY 10, 2018

While working diligently behind feature flags, using elements of Scrum, it wasn’t clear to the stakeholders the value being delivered and how well the teams were progressing towards their end goal. Development teams are structured and empowered by the organisation to organise and manage their own work. Lessons learnt.

Technical Review 124

Technical Review Development Team Review 2017 Engineering 124