Digite

MAY 15, 2018

This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. 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. You should go read it now.

Development Team Review 93

Development Team Review Software Review Underperforming Technical Team SCRUM 93

Rebel’s Guide to PM

MAY 12, 2020

When I started working for White October we followed the conventional “scrum” format, where the team get together, share what’s new, what’s challenging and what’s happening, and everyone gives feedback and makes suggestions to unblock each other. In Scrum, the development team attend the daily standup meeting.

SCRUM 357

SCRUM Agile Energy Development Team Review 357

Gunther Verheyen

FEBRUARY 27, 2024

Having no other plans for that time being, I could completely focus on my work as curator: contacting people, collecting ideas for essays, reviewing potential essays, suggesting potential edits, ordering and categorizing them, reviewing the manuscript and the cover. years before the deadline they had in mind). 1986, [link]. (2)

SCRUM 71

SCRUM 2004 Software Review 2019 71

Scrum.org

MARCH 19, 2023

I wanted to determine whether ChatGPT 4 is superior to its predecessor, which left a good impression in recent months; see my previous articles on Scrum, Agile, and ChatGPT. Shall I notify you about articles like this one? The Product Owner and Scrum Master are now considered equal members of the Scrum Team.

ChatGPT 151

ChatGPT SCRUM Technical Review 2020 151

The IIL Blog

SEPTEMBER 6, 2023

By APMG International September 6, 2023 Agile project management is a flexible approach to managing projects which involves taking incremental steps referred to as sprints or iterations. The Benefits of Agile Project Management Agile project management often results in the early release of benefits due to its incremental nature.

Agile 88

Agile Underperforming Technical Team Software Review Development Team Review 88

Project Pulse Journal

APRIL 8, 2024

Improved Risk Management This component empowers teams to anticipate and mitigate potential risks by selecting a development approach tailored to the project's unique nature. Incorporating advanced risk assessment models enables a deeper understanding and identification of possible pitfalls.

Underperforming Technical Team 52

Underperforming Technical Team Cadence Development Team Review Technical Review 52

Planio

DECEMBER 18, 2023

In fact, an annual product survey found that over 30% of teams plan their roadmaps a year in advance, dispelling the myth that agile teams shouldn’t waste their time planning far into the future. If you’re a project manager or team leader gearing up to build a long-term product roadmap, this article is for you.

Planning 88

Planning Development Team Review Risk Management Software Review 88

Teamweek

JULY 2, 2020

This article will guide you through the best agile tools, taking a look at their key features and costs to inform your buying decision! Specifically, we’re going to look into tools for: Agile Planning Team/Resource Management Agile Estimation Scrum Tools for Backlog Management Source Control Continuous Integration & Deployment.

Software Developers 52

Software Developers Software Development Development Team Review Software Review 52

Scrum.org

SEPTEMBER 19, 2020

Do you want to get this article in your inbox? There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. 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.

Technical Review 191

Technical Review Software Review Development Team Review Cadence 191

Agilemania

FEBRUARY 21, 2023

Not maintaining requirements in an Agile team can lead to several challenges, including scope creep, missed deadlines, low-quality deliverables, and dissatisfied stakeholders. By maintaining requirements in an agile environment, teams can ensure that they have the most up-to-date and accurate information to make informed decisions.

Underperforming Technical Team 98

Underperforming Technical Team Agile Development Team Review Technical Review 98

Scrum.org

MARCH 22, 2021

Shall I notify you about articles like this one? The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. The interval to test via self-assessment is every 4–12 weeks, with teams of lesser fluency running their tests at the lower end of this range.

SCRUM 227

SCRUM Underperforming Technical Team Development Team Review Technical Review 227

Wrike

SEPTEMBER 30, 2023

By tracking changes made to code files and facilitating collaborative development, source control helps in maintaining a high level of code consistency throughout the software development lifecycle. Developers can quickly identify patterns and understand the logic behind the code, reducing the time required for maintenance tasks.

Software Review 36

Software Review Controlling Technical Review Development Team Review 36

Teamweek

NOVEMBER 4, 2022

In this article, we’ll cover: the definition of coding challenges different types of interview coding challenges the benefits of coding challenges during job interviews and other qualities to look out for when hiring a software developer. Different question types are available with Toggl Hire skills assessments.

Software Review 94

Software Review Underperforming Technical Team Development Team Review Technical Review 94

Digite

MARCH 12, 2018

Alternatively to the previous: I believe The IT Skeptic had an article about having two boards – one focused on the stakeholder epics, the other on the actual short-term tasks. Dev Lane for the main dev activity. The Dev board value stream follows a Test Driven Development flow. Is it a good idea?

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Scrum.org

JANUARY 9, 2023

Shall I notify you about articles like this one? For example, “Q 03” refers to the third question of the guide.). 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.

ChatGPT 219

ChatGPT SCRUM Underperforming Technical Team Technical Review 219

Project Pulse Journal

APRIL 17, 2024

From individual coding tasks to large-scale releases, the DoD sets the bar for quality and completeness, ensuring everyone - from developers to stakeholders - is on the same page. This article will help you craft a robust DoD that suits your project needs and team dynamics. Ready to transform your project delivery process?

Software Review 52

Software Review Development Team Review Technical Review 2024 52

MPUG

JUNE 19, 2023

In this article, we will define change orders and provide steps for how to integrate change orders in Microsoft Project. What is a Change Order In project management, a change order refers to a documented request that modifies a project’s original scope, schedule, or budget.

Development Team Review 52

Development Team Review Software Review Risk Management Budget 52

Scrum.org

FEBRUARY 24, 2020

TL; DR: 27 Sprint Anti-Patterns Holding Back Scrum Teams . Welcome to Sprint anti-patterns article from our series on Scrum anti-patterns, covering not just the three Scrum roles, but also the stakeholders as well as the IT management. Do you want to get this article in your inbox? Anti-patterns of the Development Team.

Development Team Review 248

Development Team Review Software Review SCRUM Engineering 248

Scrum.org

JUNE 18, 2021

What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to develop team cognition and become high-performing. Pictures of a session where we created a skill matrix with a team.

2010 183

2010 SCRUM 2006 Software Review 183

Scrum.org

SEPTEMBER 13, 2021

Shall I notify you about articles like this one? Scrum Anti-Patterns: From Product Backlog to Sprint Review. I added new questions on Scrum anti-patterns, from the Product Backlog to the Sprint Planning to the Sprint Review, to provide more insight into the Scrum value creation process and the organization’s return on investment.

SCRUM 204

SCRUM Underperforming Technical Team Development Team Review 2020 204

NimbleWork

FEBRUARY 18, 2024

Waterfall methodology refers to the sequential phase-gated project management workflow. Risks are identified and mitigated early during the project lifecycle, which allows teams to comply with stringent compliance regulations and organizational policies across the project lifecycle.

Agile 71

Agile Software Review Development Team Review Software Engineering 71

Scrum.org

FEBRUARY 27, 2022

A learning model is a must to build a learning organization/team. In this article, I would like to share a learning model that I applied to the teams, helping them learn and develop as follows: Stage 1 - Inspiration: This is the stage of determining the reason and the point of learning? with different stakeholders.

SCRUM 186

SCRUM Development Team Review Defining Executing 186

Scrum.org

SEPTEMBER 24, 2021

When I present the Scrum framework to a new team, I almost always hear someone cry out, “How can we get anything done with so many meetings?! ” The Scrum framework consists of five events (what the uninitiated refer to as meetings), three artifacts, and three roles. See my article Can Scrum work for Hard Deadlines to learn more. .

SCRUM 207

SCRUM Software Review Lean Leadership 207

Scrum.org

FEBRUARY 4, 2020

Do you want to get this article in your inbox? The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” To a certain extent, it is also a negotiation between the Product Owner and the Development Team. Source : Scrum Guide 2017.

Development Team Review 193

Development Team Review Underperforming Technical Team SCRUM Technical Review 193

Scrum.org

MAY 6, 2019

The Sprint Goal is a phrase that can be used in many different ways: The Development team uses it at every Daily Scrum, to inspect the work done and adapt the work left. Is it defined in a way that provides guidance and flexibility to the Development Team? References. The Scrum Team also crafts a Sprint Goal. ". "

Development Team Review 124

Development Team Review Technical Review SCRUM Defining 124

Project Pulse Journal

MAY 18, 2024

This article provides a high-level view of PM technologies. Discover how to assess the relevance of these tools and identify how you can help achieve project excellence with the help of traditional techniques and cutting-edge technology solutions. Ready to take your project management skills to the next level?

Technical Review 52

Technical Review 2024 Development Team Review Risk Management 52

Project Pulse Journal

APRIL 16, 2024

Conduct the Sizing Session - Team members assign a t-shirt size to each backlog item through discussion and consensus or by individual voting (similar to planning poker). Review and Adjust - Once all items are sized, review the assignments to ensure consistency across the backlog. splitting an XL task into two L tasks).

Agile 52

Agile Technical Review Software Review Development Team Review 52

Scrum.org

DECEMBER 4, 2022

Shall I notify you about articles like this one? Answer : “Business agility refers to the ability of a company to quickly and effectively respond to changes in its environment. It gets a bit repetitive; however, the Generative AI adds agile practices and refers directly to agile software development.

ChatGPT 179

ChatGPT Generative AI SCRUM Agile 179

Epicflow Blog

NOVEMBER 24, 2021

Each of them has certain peculiarities, so development teams can choose the one that works best for them. . One more distinctive feature of Agile methodology is its focus on collaboration and self-organizing cross-functional teams. It can be difficult to assess the efforts and time required for certain deliverables.

Underperforming Technical Team 98

Underperforming Technical Team Agile Development Team Review Software Developers 98

ProjectManager.com

NOVEMBER 22, 2021

The term scrum was introduced in a “Harvard Business Review” article from 1986 by Hirotaka Takeuchi and Ikujiro Nonaka. It became a part of agile when Ken Schwaber and Mike Beedle wrote the book “Agile Software Development with Scrum” in 2001.

Technical Review 483

Technical Review Prince2 Manufacturing Lean 483

Wrike

OCTOBER 5, 2023

In this article, we will explore the concept of negative testing, delve into its process and impact on software quality, discuss the challenges it presents, and shed light on future trends in this domain. This helps developers understand the root causes and facilitates efficient fixes.

Artificial Inteligence 36

Artificial Inteligence Underperforming Technical Team Software Review Development Team Review 36

Scrum.org

NOVEMBER 24, 2021

Note that Bass calls this “Groom” in reference to “Product Backlog Grooming”. 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).

2014 213

2014 2008 Technical Review 2019 213

MPUG

DECEMBER 28, 2020

In this article, I’ll outline the top changes and the deeper meaning associated with each change. 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.

Cadence 116

Cadence SCRUM 2020 Agile 116

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. Shall I notify you about articles like this one? There is a reason why some refer to the Product Owner role as the “Achilles heel” of the Scrum team or the “single wringable neck.”

Underperforming Technical Team 189

Underperforming Technical Team SCRUM Technical Review Development Team Review 189

MPUG

AUGUST 14, 2023

This article delves into the potential challenges of transitioning from an opportunity to a project. Customer demands and aspirations drive sales teams, while project managers are responsible for delivering the project within defined constraints. This extraneous input creates what I refer to as turbulent flow.

Underperforming Technical Team 52

Underperforming Technical Team Development Team Review Estimate Closing 52

Project Pulse Journal

APRIL 15, 2024

But why settle for a one-size-fits-all approach when the landscape of your projects is as varied as the team behind them? This Article allows you to explore these methodologies in-depth, tailor them to fit your unique project needs, and wield them to achieve unparalleled project outcomes.

Software Review 52

Software Review Technical Review Agile SCRUM 52

Scrum.org

SEPTEMBER 1, 2018

The Scrum is the whole of the Development team, the Product Owner and the Scrum Master. The Scrum team has affinity with the family of roles, yet it is not a role in the Scrum framework. The Scrum Master is servant leader for the Scrum team. The Daily Scrum is a 15-minute time-boxed event for the Development team.

SCRUM 94

SCRUM Development Team Review Software Review Influencer 94