Scrum.org

AUGUST 15, 2022

What [shall we] do when a product requires many development teams? Your emphasis on teams that include all of the many stakeholders implies that everyone needs to have a basic understanding of every aspect of the product and delivery. His most recent book, Forever Employable , was published in June 2020.

Agile 213

Agile Planning Software Review 2022 213

Scrum.org

FEBRUARY 25, 2024

Dive into how leveraging custom GPTs might offer a novel path through Scrum’s common hurdles, focusing on creating actual customer value in the face of organizational and team-level challenges. ? Your single best investment to improve your professional standing ; order the Scrum Anti-Patterns Guide book now! ?

SCRUM 226

SCRUM ChatGPT Technical Review Development Team Review 226

Scrum.org

JUNE 11, 2021

They have to be able to create the right ideas for value and be expert at communicating those ideas to the Development Team. Your goal therefore should be to be reading at least 1-2 books per month that help you get better at being a Product Owner. Here is a solid list of books to get you started in the right direction.

Lean 234

Lean SCRUM Certification Development Team Review 234

Scrum.org

MAY 5, 2020

Due to the COVID-19 crisis, chances are that everyone in your organization is working from home. This includes your Product Owner and Development Team. Start a virtual book club. With your Scrum Team or within the wider organization, start a book club. Pick a book, a blog post or a podcast to start with.

SCRUM 220

SCRUM Development Team Review Technical Review Consulting 220

Digite

MARCH 12, 2018

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! Far too many projects and teams are occupied by far too many crises all through the development/ implementation lifecycle. Our Kanban Journey.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Scrum.org

MARCH 11, 2023

More things to think about come from Marty Cagan's “Inspired” book. The tool: Product Opportunity Assessment (POA): What problem will this solve? Sounds like you should start the 1st Sprint with focus on a Integrated Done Increment Not like others spending 600’000 CHF on Not Done Software. Can the user use it?

Underperforming Technical Team 195

Underperforming Technical Team Development Team Review Risk Management Risk 195

Scrum.org

SEPTEMBER 13, 2021

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Scrum Anti-Patterns: From Product Backlog to Sprint Review. Development teams often create tasks an engineer can finish within a day.

SCRUM 233

SCRUM Underperforming Technical Team Development Team Review 2020 233

Scrum.org

JULY 21, 2020

That is why we pay the Development Team to accept the responsibility to deliver a ‘done’ Product Increment. Waiting for the end of a sprint and a sprint review means waiting to ship a done project.” Or the Development Team is continuously delivering Increments during the Sprint. The statement is plain wrong.

Software Review 224

Software Review Underperforming Technical Team SCRUM Engineering 224

ProjectManager.com

JUNE 2, 2022

Once you’ve done the work of a product breakdown structure and the related product documentation, you can feed that information into project management software and jumpstart your project plan. In the illustration below, you can see that the product breakdown structure is used for building a book website. Step 1: Identify Products.

Prince2 221

Prince2 Risk Management Development Team Review Engineering 221

Scrum.org

MARCH 22, 2021

Your candidate should not align themselves with the fallacy that a team’s adoption of Scrum is working only because a Scrum Team’s forecasts and velocity are aligned. Cooking the agile books is easy to do ! Trends derived from these polls are great points for discussion during a team’s Sprint Retrospectives.

SCRUM 235

SCRUM Underperforming Technical Team Development Team Review Technical Review 235

Scrum.org

NOVEMBER 28, 2020

What is important about Scrum is that it is a framework, and Scrum Teams need to define their process, practices, and tools within the framework. If you’ve taken a Professional Scrum course with me or read my book , you know my thoughts on best practices. Having a team within a team was a bit confusing. Absolutely!

2020 222

2020 SCRUM Underperforming Technical Team Software Review 222

Scrum.org

JANUARY 10, 2021

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.

Software Review 230

Software Review Technical Review Planning Manufacturing 230

Scrum.org

OCTOBER 30, 2022

When I started my journey as a Scrum Master about 12 years ago, I read many books about Scrum. Interestingly, one of the first books I also studied was “ Extreme Programming Explained ” by Kent Beck. In order to make the start as smooth as possible, you spend lots of time with the team to practice the Scrum kickstart.

SCRUM 213

SCRUM Development Team Review Closing Technical Review 213

Digite

MAY 15, 2018

In case you haven’t read Yuval’s post, basically, it presents a map of values and practices in Scrum to Kanban language, and encourages Kanban teams to approach Scrum from a practices point of view. This is probably the set of things that, regardless of the name, Scrum and Kanban teams will have the most in common.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Scrum.org

JUNE 22, 2019

For years, I’ve fulfilled the role of Scrum Master for many different organizations and Scrum Teams. These teams were mostly focused on software development. These organizations were able to attract the smartest developers and create products customers loved. Examples of a Developer Culture.

Underperforming Technical Team 184

Underperforming Technical Team Technical Review Software Review Development Team Review 184

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

LiquidPlanner

SEPTEMBER 20, 2018

These teams struggle with Agile practices as business analysts author reams of business requirements only to have a development team write the user stories. Business representatives assume the product owner role but only check in with their team at the sprint review. The development team is distributed.

Agile 144

Agile Software Review Development Team Review Certification 144

nTask

JULY 7, 2021

PERT stands for the Project Evaluation and Review Technique. Well, that’s how the famous American engineer and management consultant, Harold Kerzner puts it in his book. Featured Resources: The 36 Best Gantt Chart Software for Project Management in 2021. Let’s begin. PERT chart. Let us explain. Gantt charts. Gantt view in nTask.

Development Team Review 148

Development Team Review 2021 Software Review Consulting 148

Scrum.org

AUGUST 17, 2020

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Though whatever the case, we can say for sure that Scrum is very popular in software development. Introduction.

SCRUM 234

SCRUM Technical Review Software Review Agile 234

Scrum.org

MARCH 4, 2019

Whatever it is we do, from the outside it looks like the majority is enjoying this new and more playful approach for software development. Once bugs come raining down we learn that DONE software does not run on 'localhost'. Scrum Masters focus on themselves and the team while doing Scrum by the book.

SCRUM 156

SCRUM Software Review Development Team Review Underperforming Technical Team 156

The IIL Blog

JULY 31, 2024

In her book, The Content Strategy Toolkit , Meghan Casey says, “The first key to getting stakeholders on board and aligned is to have empathy for where they are starting from. I like to do assessments from time to time, beyond the regular meetings and updates. Many software tools are available for recording and tracking requirements.

Technical Review 88

Technical Review Development Team Review 2013 Underperforming Technical Team 88

Scrum.org

NOVEMBER 24, 2021

Which activities can be fulfilled by others in the team, and what is needed for that? One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018). Maarten, who is an experienced Product Owner, added that he spends a lot of time on this with his teams.

2014 233

2014 2008 Technical Review 2019 233

Epicflow Blog

JULY 5, 2024

A capacity planning tool is software developed to assist organizations in allocating and managing their resources more effectively. Features of a capacity planning software Here are some key functionalities a robust capacity planning tool should possess. Why do you need capacity planning software?

2024 100

2024 Planning Development Team Review Consulting 100

Scrum.org

MARCH 4, 2019

Whatever it is we do, from the outside it looks like the majority is enjoying this new and more playful approach for software development. Once bugs come raining down we learn that DONE software does not run on 'localhost'. Scrum Masters focus on themselves and the team while doing Scrum by the book.

SCRUM 26

SCRUM Software Review Development Team Review Underperforming Technical Team 26

Scrum.org

FEBRUARY 22, 2022

In one situation it was all about a brand new platform with new hardware and software in a stack not familiar to me and new teams that hadn’t worked together before. In the second experience the size change was even more significant and introduced a new complexity by having teams at different locations on three different continents.

Software Review 209

Software Review Underperforming Technical Team Technical Review Development Team Review 209

Scrum.org

JANUARY 9, 2023

Follow-up question : Why is it beneficial that the team adheres to the values and practices of Scrum? This can help improve the overall quality of the team's work and ensure that the team is meeting its goals. Question : Should a Scrum Master remove problems on behalf of the Scrum Team? In-person and remote attendees.).

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

Planio

OCTOBER 19, 2021

And whether you’re a designer, developer, team lead, or administrator, your job requires many of the same skills that separate the best project managers: organization, effective collaboration, and being goal-oriented. Step 12: Plan your first sprint as a team. Step 13: Review progress and adjust your plan.

Technical Review 199

Technical Review Software Review Risk Management Estimate 199

Scrum.org

FEBRUARY 10, 2022

Again, I have HOURS of content on this—articles, books, videos, etc. SAFe is inconsistent with an agile mindset as it is plan-focused, bureaucratic, complicated, dis-empowers team autonomy, and includes a lot of often unnecessary processes and structure. how to run a proper review). Better risk identification. Is perfect?

Lean 213

Lean Software Review 2022 Technical Review 213

Gunther Verheyen

FEBRUARY 27, 2024

In the summer of 2019 I got in touch with O’Reilly Media about their ambition to add a book about Scrum to their “97 Things” series. As the title of the series suggests, the idea was to collect 97 essays in the book, to be provided by people from around the world. 8 People contributed 3 Things.

SCRUM 81

SCRUM 2004 Software Review 2019 81

Scrum.org

JULY 1, 2019

Working software over comprehensive documentation. The Agile manifesto should be known by all and understood by everybody in the team and in the whole organisation. We need to probe, assess and respond to be able to adapt to change. The Scrum team also needs to support this vision and purpose.

SCRUM 161

SCRUM Underperforming Technical Team Development Team Review Controlling 161

Scrum.org

FEBRUARY 7, 2022

Again, I have HOURS of content on this—articles, books, videos, etc. SAFe is inconsistent with an agile mindset as it is plan-focused, bureaucratic, complicated, dis-empowers team autonomy, and includes a lot of often unnecessary processes and structure. how to run a proper review). Better risk identification. Is perfect?

Lean 183

Lean Software Review 2022 Agile 183

Leading Agile

NOVEMBER 2, 2020

They will say things like, “I’ma a hint Jeff Sutherland wrote a book.” It’s not even about working tested software as fast as you can deliver it, it’s really about what is that combination of working tested software that we can put reliably in front of a customer, so that we can start charging money for it.

Agile 118

Agile Development Team Review Underperforming Technical Team Consulting 118

MPUG

DECEMBER 28, 2020

It’s less prescriptive and seems to be intended for a wider audience group, particularly non-software users. My perspective is based on my analysis, my own interpretations, and the interactions I’ve had with Agile practitioners who follow my publications, books, and/or courses. Single Scrum Team. Introduction of Cadence.

Cadence 116

Cadence SCRUM 2020 Agile 116

Leading Answers

MAY 8, 2022

There are thousands of agile practices documented in books, blogs and presented at agile conferences every year and likely many times more that never get reported. Let's review some popular techniques often seen on Scrum teams. . Agile Concepts: Frequent delivery – Deliver working software frequently.

Agile 109

Agile Underperforming Technical Team Technical Review Software Review 109

Binfire

AUGUST 27, 2017

The Agile project management methodology has been used by software engineers and IT professionals for the past sixteen years. In the late twenty century, many software engineering researchers in academia were studying the disturbing fact that most software and IT projects finish late or fail to finish at all.

Agile 97

Agile Technical Review Software Review Development Team Review 97

Leading Agile

NOVEMBER 13, 2018

It’s interesting to me that in the software field we habitually sling buzzwords around as if we were talking about real Things, when in fact the buzzwords are only metaphors. “Velocity” in software development doesn’t mean velocity. In software development, it’s only a metaphor.

Software Review 113

Software Review Underperforming Technical Team Software Developers Software Development 113

nTask

MARCH 16, 2022

The implication of an agile methodology allows teams to execute projects faster, with greater adaptability and a streamlined workflow. Mostly, agile methodology is used by companies where project requirements are constantly changing, for example, software and marketing agencies. Working software over comprehensive documentation.

Agile 97

Agile Technical Review Software Review Development Team Review 97