NimbleWork

MAY 1, 2024

In a software development project, email notifications, team meetings, and code reviews can be represented using symbols to visualize the communication and collaboration process. In this example, we will consider a software development team working on a web application for an e-commerce platform. Source: Medium 2.

Software Review 52

Software Review Process Technical Review Development Team Review 52

Scrum.org

AUGUST 1, 2023

They commence their journey with clear intentions, understanding their role as value maximizers, focusing on delivering value, and diligently setting up their Product Backlog , goals, and stakeholder interactions. Validation: Regular assessment with stakeholders to ensure alignment. Vision: The overarching goal of the product.

Technical Review 150

Technical Review Development Team Review Transportation SCRUM 150

International Institute for Learning

JANUARY 25, 2023

Instead, you rely on the contributions and the support of the key stakeholders, the development team members, and possibly other product people who help you manage a large product. For example, the marketer has to create the marketing strategy, and the development teams have to design and build the product.

Development Team Review 52

Development Team Review Leadership Influencer SCRUM 52

Scrum.org

AUGUST 17, 2020

If you are looking to fill a position for a Scrum Master (or agile coach) in your organization, you may find the following 47 Scrum Master interview questions useful to identify the right candidate. Then sign up for the Food for Agile Thought newsletter and join 26k other subscribers. Question 02: Success Factors of “Agile”.

SCRUM 232

SCRUM Technical Review Software Review Agile 232

nTask

DECEMBER 21, 2021

This backlog contains many different elements like enhancements, bug fixes that the development team has to perform, new features that have to be introduced, and the technology upgrades that are needed in the current product. Let’s take a look at the core principles of the product backlog management process.

2022 78

2022 Underperforming Technical Team Technical Review Development Team Review 78

LiquidPlanner

MAY 15, 2018

Business teams struggled with understanding their role in a software project while trying to sort through all the technical jargon used to build a website. Related: Adopting Agile is an Exercise in Change Management. Given these challenges, how does applying Agile practices improve the relationship?

Agile 74

Agile Software Review Technical Review Development Team Review 74

Planio

MAY 27, 2020

Without a clear definition of done , your development team doesn’t know what they’re working towards, your stakeholders are free to increase the scope, and your users most likely end up with a product that’s cluttered, confusing, and unusable. When can the development team change the definition of done (and how should they do it?).

Software Review 145

Software Review Technical Review Development Team Review Defining 145

Leading Answers

MARCH 7, 2019

When our projects undertake defined, repeatable work using technologies and approaches our organizations have experience in, then uncertainty and change rates are typically low and manageable. Designing something is typically a consensus-gathering and problem-solving exercise. Here, traditional project management approaches work great.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

Planio

DECEMBER 14, 2018

Sprints are the backbone of any good Agile development team. But maybe more than that, sprint planning aligns the development team with the product owner. Like any relationship, the one between you and your team requires communication and clarity. Step 1: Review your product roadmap.

Software Review 107

Software Review Planning Technical Review Development Team Review 107

Scrum.org

MARCH 11, 2020

TL; DR: Development Team Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the Development Team in Scrum. Do you want to get this article in your inbox?

Development Team Review 227

Development Team Review Underperforming Technical Team Software Review Technical Review 227

Agilemania

NOVEMBER 11, 2022

Keep reading to find out more about this essential role in your company’s software development team. A Scrum Master is a facilitator who helps a Scrum team to self-organize, collaborate, and continuously improve. Facilitating daily stand-up meetings with the team. Providing feedback to the team. Agile fundamentals.

SCRUM 88

SCRUM Certification Technical Review Lean 88

MPUG

JULY 15, 2019

Also, in software development, requirement change is the rule, rather than the exception. Stories in Agile Development replace requirements. The remaining work happens when the story is developed. This leads to the concept of epics in Agile development. It’s an extension of the user story concept.

Agile 99

Agile Software Review Infrastructure Estimate 99

nTask

NOVEMBER 12, 2018

They are considered to be an invaluable source of collecting information and feedback from the development team and help in keeping the team aligned with the Sprint goals. Sprint Review Meeting. Usually, the entire team is expected to be present during this meeting, including the product owner and the Scrum master.

SCRUM 123

SCRUM Development Team Review Technical Review 2018 123

Scrum.org

FEBRUARY 25, 2024

You can sign up here for the ‘Food for Agile Thought’ newsletter and join 42,000-plus subscribers. ? The Idea of a Scrum GPT Exploring Scrum in the real world often uncovers a tangle of anti-patterns—those practices that, despite best intentions, stray from agile principles and hinder progress.

SCRUM 187

SCRUM ChatGPT Technical Review Development Team Review 187

Leading Answers

JUNE 14, 2018

Instead, we launch agile transformations, digital transformations and productization transformations.   Agile Transformations. The goal:  Agile transformations move organizations from working with traditional project management approaches to using agile approaches. Transformations are flavor of the month.

Technical Review 116

Technical Review Agile Lean Sustainability 116

Scrum.org

JANUARY 9, 2023

Can a large language model, not specializing in anything “agile,” pass a screening interview for a Scrum Master position? You can sign up here for the ‘Food for Agile Thought’ newsletter and join 36,000-plus other subscribers. ? ? ?? Follow-up question : Why is it beneficial that the team adheres to the values and practices of Scrum?

ChatGPT 222

ChatGPT SCRUM Underperforming Technical Team Technical Review 222

Scrum.org

FEBRUARY 9, 2022

Agile is an umbrella term encompassing a variety of frameworks and approaches to value delivery in complex environments. The word agile came into widespread use following the creation of the Agile Manifesto in 2001. The Agile Manifesto includes four values and 12 principles that describe a better way to approach complex work.

Agile 246

Agile Software Review Technical Review SCRUM 246

Leading Answers

JUNE 14, 2018

Instead, we launch agile transformations, digital transformations and productization transformations.   Agile Transformations. The goal:  Agile transformations move organizations from working with traditional project management approaches to using agile approaches. Transformations are flavor of the month.

Technical Review 60

Technical Review Agile Lean Sustainability 60

Scrum.org

SEPTEMBER 13, 2021

If you are looking to fill a position for a Scrum Master (or agile coach) in your organization, you may find the following 54 interview questions useful to identify the right candidate. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 33,000-plus subscribers. ?? Shall I notify you about articles like this one?

SCRUM 211

SCRUM Underperforming Technical Team Development Team Review 2020 211

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. November 19, 2020 : If you use Scrum then join the free Hands-on Agile meetup—it will be worth your time ! Keeping technical debt at bay. Read more: Technical Debt & Scrum: Who Is Responsible ?).

SCRUM 230

SCRUM Underperforming Technical Team Technical Review Software Review 230

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. But a full Agile transformation isn’t just about the development process you use — it’s a way to bring creativity, innovation, and lean operations to every aspect of your business. What is an Agile transformation?

Agile 78

Agile Technical Review Leadership Infrastructure 78

Scrum.org

MARCH 2, 2020

Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns which easily can impede any agile transition. The early majority of organizations are already adopting BDD/DDD or Pragmatic Agility.).

SCRUM 223

SCRUM Development Team Review Underperforming Technical Team Technical Review 223

MPUG

MAY 6, 2021

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Kyle: Today’s session is eligible for one PMI, PDU in the technical category, and the code for claiming that with PMI is on the screen now. Technology is wonderful.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Scrum.org

NOVEMBER 27, 2018

But many teams struggle with this rule. An increment is considered “Done” by the Development Team, but requires further testing and stabilization in the next Sprint. Or work is considered “Done” by the Development Team, but the install package still needs to be created. It is tempting to fall into “shades of Done”.

Software Review 150

Software Review Technical Review SCRUM Software 150

Planio

APRIL 6, 2021

A product requirements document (PRD) is one of the most important documents for teams using traditional project management. However, an increasing number of Agile teams are starting to see the value of adding more planning to their process. Agile is all about staying lean and adapting to user feedback, right?

Lean 78

Lean Technical Review Software Review Underperforming Technical Team 78

Scrum.org

FEBRUARY 4, 2020

“The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Remember: user story creation is a team exercise.). To a certain extent, it is also a negotiation between the Product Owner and the Development Team. Source : Scrum Guide 2017.

Development Team Review 198

Development Team Review Underperforming Technical Team SCRUM Technical Review 198

Leading Answers

JUNE 22, 2022

This is part one in a series on leading agile teams from the Beyond Agile book. We will examine what leadership entails and how it applies to agile teams. It can be learned and exercised on a small scale before being brought to bear on larger groups.   EQ as a Foundation for Leadership.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Energy 193

Planio

JANUARY 31, 2022

That’s why a product roadmap is the backbone of every great development team. And unfortunately, too many teams treat roadmapping like just another project, leaving it behind to collect dust as they move on and start building software. Why you need a roadmap (even as an agile team). Agile product roadmap example.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Planio

AUGUST 1, 2023

6 rules to follow How to bring strategy and tactics together: 5 examples for different teams 1. Product development teams 2. Digital marketing teams 3. Sales teams 4. Customer service teams 5. A successful strategy isn’t a set-and-forget exercise. A successful strategy isn’t a set-and-forget exercise.

Development Team Review 78

Development Team Review Infrastructure Software Review Governance 78

Scrum.org

SEPTEMBER 27, 2021

This latest update to the interview guide addresses Product Owner anti-patterns from Product Backlog management and refinement to the Sprint Review. You can sign up here for the ‘Food for Agile Thought’ newsletter and join 33,000-plus subscribers. ?? Remember: Product Backlog item creation is a team exercise in most cases.).

Underperforming Technical Team 193

Underperforming Technical Team SCRUM Technical Review Development Team Review 193

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 “Scrum Question of the Week” exercise. At the start of the week, you offer the team a question about the Scrum theory & principles. Things to try….

SCRUM 180

SCRUM Development Team Review Technical Review Consulting 180

Scrum.org

OCTOBER 19, 2020

If you are looking to fill a position for a Scrum Master (or agile coach) in your organization, you may find the following 47 interview questions useful to identify the right candidate. These should allow an interviewer to deep dive into a candidate’s understanding of Scrum and her agile mindset. Scrum Teams are no exception.

SCRUM 164

SCRUM Underperforming Technical Team Software Review Development Team Review 164

Scrum.org

JANUARY 14, 2021

The Nexus group of teams is very similar to the Agile Release Train (ART) construct. In both SAFe/Scrum it is a self-managing team of self-managed teams with a couple of key roles at the team of teams level. . Lean/Agile Leadership. You cannot scale crap - Scaling requires technical excellence.

Cadence 137

Cadence Technical Review Development Team Review Lean 137

Scrum.org

JUNE 23, 2019

This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The Development Team is responsible for all estimates.

Development Team Review 174

Development Team Review Technical Review SCRUM Estimate 174

Leading Agile

MARCH 17, 2021

This is Mike Cottmeyer's talk from AgileIndy 2021 on The Executive's Guide to Why Agile Transformation Fails. Announcer] This is Mike Cottmeyer’s talk from AgileIndy, 2021 on “Why Agile Transformation Fails.” So I got involved with agile back in like 2003 and I was working in this company called CheckFree.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

Scrum.org

JUNE 23, 2019

This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The Development Team is responsible for all estimates.

Development Team Review 166

Development Team Review Technical Review SCRUM Estimate 166

Agilemania

MAY 25, 2022

The Product Backlog is a major Agile and Scrum Artifact. A lot of teams struggle while managing it. . Technical Debt . Boosts efficiency: Since prioritization of tasks happens regularly, the development team will be able to manage their time better. Why is that? . What are the reasons? . What is a Product Backlog?

Underperforming Technical Team 52

Underperforming Technical Team Development Team Review Technical Review SCRUM 52