article thumbnail

Digital transformation’s fundamental change management mistake

CIO

For example, KPMG reports that 51% of technology executives have not seen an increase in performance or profitability from digital transformation investments. Agile and scrum methodologies put most of the emphasis on delivery activities when teams focus on completing user stories every sprint.

article thumbnail

Agile project management: Principles, benefits, tools, tips, and when to make the switch

CIO

Although agile does value documentation, it is not as heavily emphasized as it is in traditional project management, for which documentation is often very detailed and assembled in advance. Agile project management and Scrum Scrum is a powerful framework for implementing agile processes in software development and other projects.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Subbing for the Scrum Master to fill a project gap

Perficient

So when your project’s Scrum Master has to step away for a period of time, the business analyst may be the role that temporarily steps in to fill the gap. Here are some things to consider if you’re stepping into the Scrum Master’s shoes. The main thing to remember is that Agile is all about team communication and collaboration.

SCRUM 64
article thumbnail

Leaders Leveraging the OODA Loop in a Scrum@Scale Environment

scruminc

This blog post explores the synergy between the OODA Loop and Scrum, delving into how this powerful decision-making tool can be leveraged for effective impediment removal. In business, this could mean looking at performance metrics, team feedback, or market conditions. The term “impediment” holds significant weight.

SCRUM 45
article thumbnail

Making Scrum meetings more productive

Apiumhub

In the list of activities in the Scrum software development life cycle ranked by their popularity amongst developers, “attending meetings” is perhaps locked in a perpetual battle only with “writing documentation” for the position of last place. This is, of course, merely reciting from the doctrine of Scrum. Introduction.

SCRUM 82
article thumbnail

What is the Recommended Scrum Team Size?

Agile Pain Relief Notes from a Tool User

The Scrum Guide offers very limited guidance, suggesting 3-9 people per team (exclusive of ScrumMaster and Product Owner), without giving reasons or context for those numbers. While this is primarily about Scrum, the lessons are applicable for any work that is collaborative and knowledge-based. Clear Roles and Responsibilities [ 8 ].

SCRUM 117
article thumbnail

Exploring the Release Phase of a Scrum Project

SCRUMstudy

A Scrum project often goes through a number of phases. Five phases, composed of nineteen processes, are suggested in A Guide to the Scrum Body of Knowledge ( SBOK ). The Release phase is the final stage of a Scrum project. It is important to note that the processes are not necessarily performed sequentially or separately.

SCRUM 92