MPUG

MARCH 8, 2021

In this article, we will explore some of the practical problems faced by Lean-Agile practitioners during development of a new product or service and/or the building of a solution. Earlier, in one of my articles, I had mentioned that Agile is both iterative and incremental in nature. It’s usually based on a cadence. Flow-based.

Lean 64

Lean Software Review Technical Review Agile 64

MPUG

SEPTEMBER 4, 2023

In this article, we’re addressing a common question in modern project management: Do we need risk management in agile projects? What agile adds to this, therefore, is a distinct cadence of its own iterations or drawdowns of tasks into the Work in Progress part of the Kanban Board. Rapid development in the technology available.

Risk Management 98

Risk Management Risk Agile Technical Review 98

Scrum.org

OCTOBER 2, 2018

In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. A lot of people see the Scrum Sprint as mainly a release cadence.

Cadence 135

Cadence Development Team Review Software Review Technical Review 135

Scrum.org

OCTOBER 2, 2018

In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. A lot of people see the Scrum Sprint as mainly a release cadence.

Cadence 131

Cadence Development Team Review Software Review Technical Review 131

Velociteach

FEBRUARY 1, 2023

This article presents a framework for modeling project context and considerations for tailoring. Projects using well-understood solutions and technologies require less rigor. Problem complexity, technical complexity, compliance requirements, and the cost of change factor into this decision. Solution Complexity.

Planning 52

Planning Technical Review Governance Government 52

MPUG

FEBRUARY 1, 2021

In this article, we will learn about PMOs as organizational structures, about various types of PMOs, and about traditional roles within a PMO. A PMO, like the service providers I mentioned in the example at the beginning of this article, also exists to provide value and insight into project performances. Multi-Disciplinary. Resourcing.

Agile 94

Agile PMO Technical Review Cadence 94

Leading Answers

MARCH 7, 2019

I wrote this article about the choices of approach we have and ways for new PMs to navigate them.). 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.

Software Review 101

Software Review Technical Review Risk Management Software Developers 101

Scrum.org

FEBRUARY 22, 2021

Shall I notify you about articles like this one? Apparently, there is a difference in the inspect & adapt cadence when product strategy and Sprint Backlog are compared to each other. The product roadmap needs to be adapted to the learnings from running product experiments regularly in an appropriate cadence to meet that standard.

Software Review 156

Software Review Technical Review Cadence SCRUM 156

MPUG

JUNE 28, 2021

The Massachusetts Institute of Technology (MIT), US, notes in its web-archives that Odissi is two to three thousand years old. Now, you might be thinking what exactly a dance has to do with cadence in Agile? Let’s start first with the definition of cadence. Cadence – Definition and Basics. Working with Single Cadence.

Cadence 115

Cadence Agile Technical Review SCRUM 115

Digite

JUNE 13, 2018

In this article, Andrea explains the Kanban method in detail starting from its origin to its principles and its application. The limit on work being reviewed, however, might be different, depending on how long this piece of the workflow takes, how many people are assigned to review work, and other factors.

Agile 110

Agile Technical Review Cadence Software Review 110

Wrike

JUNE 11, 2023

Ease of use : A goal tracking tool should be intuitive and user-friendly, allowing you to easily set up and track your goals without any technical difficulties. For example, you can set a regular cadence for reviewing your goal tracking data. Note: This article was created with the assistance of an AI engine.

Monitoring 36

Monitoring Software Review Cadence Technical Review 36

Scrum.org

JANUARY 30, 2023

This article is another excursion into this nascent yet fascinating new technology of generative AI and LLMs and the future of knowledge work. If technology can pass a Wharton MBA exam , maybe, it deserves some attention. Shall I notify you about articles like this one? I am no longer sure about that.

ChatGPT 209

ChatGPT Agile Artificial Inteligence Consulting 209

Project Management Essentials

AUGUST 3, 2019

Outsourcing is a good option for organizations where technology is not a core or strategic competency. Typically, technology contracts are fixed-scope/fixed-price and assume an adversarial buyer-supplier relationship. Poorly coded features may be technically complete, but not acceptable. Outsourced Agile. Plan for Success.

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

Resource Guru

OCTOBER 18, 2023

Our focus in this article is primarily on “billable hours,” which are the hours dedicated solely to client-facing, revenue-generating tasks. On the other hand, simpler projects may increase your rate due to easier management. An uptick in confirmed projects should trigger a review of available resources.

Underperforming Technical Team 52

Underperforming Technical Team Software Review Technical Review Monitoring 52

Wrike

SEPTEMBER 3, 2023

In this article, we will explore the importance of a status report, the elements of a comprehensive report, the steps to design a template, and tips for making your status report more effective. It is crucial to avoid using excessive jargon or technical terms that may confuse or alienate stakeholders.

Risk Management 36

Risk Management Cadence Risk Technical Review 36

Leading Agile

APRIL 20, 2023

When you look at the literature that’s out there, I was reading an article recently about empowering teams, and the very first line in the step of the five steps for how to empower your teams was “manage your teams in an empowered way.” Some organizations do operations reviews or bigger retrospectives.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Leading Agile

MAY 3, 2023

The roles, the ceremonies, the artifacts, the cadences, all those different things that we model as implementation details. Are we doing reviews? What kind of reviews and retrospectives are we doing and how are we doing them?” It happened with RUP, it happens with SAFe, it happens with Scrum, it happens with everything.

Agile 62

Agile Technical Review Governance Government 62

Leading Agile

AUGUST 13, 2018

Technical teams who are building or supporting application software usually work from a prioritized list of improvements, new features, and ideas to try out. All that unplanned activity used to create stress for technical workers. Unexpected or unplanned work isn’t always due to “defects.” There will be stress.

Software Review 98

Software Review Technical Review Cadence SCRUM 98

Scrum.org

MARCH 11, 2024

This article covers the three Scrum accountabilities (formerly roles) and addresses interferences of stakeholders and IT/line management with this crucial Scrum event. Shall I notify you about articles like this one? Technically, it is the prerogative of the Product Owner to cancel Sprints.

Technical Review 186

Technical Review Underperforming Technical Team SCRUM Software Review 186

Leading Agile

MARCH 31, 2020

– I was working in my office down in technology Parkway. You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. And it’s not always get better the technology get better the processes, it’s get better producing the outcome. And BPR was about the technology.

Agile 71

Agile Technical Review SCRUM Engineering 71

Leading Agile

JANUARY 21, 2021

So you do review and retrospective to say, do a burn down chart. So I need a backlog, I need a dedicated team and I need the technical ability to produce a working test and increment at the end of every sprint. And they were writing HBR articles and stuff around this whole idea of business capability modeling.

Sustainability 111

Sustainability Agile SCRUM Technical Review 111

Digite

FEBRUARY 13, 2018

Continuing our theme of helping Agile teams understand the Kanban Method, so they can effectively adopt it for their improvement efforts, I am again honored to publish a guest article by another great friend of ours – Dave White. You will enjoy this excellent article. New challenges (technical and business) are always arising.

Cadence 94

Cadence SCRUM Lean Underperforming Technical Team 94

Scrum.org

DECEMBER 7, 2020

The Product Owner theses also address the Product Owner’s part in Scrum events from Sprint Planning to Sprint Review to Sprint Retrospective, and the Daily Scrum. Do you want to get this article in your inbox? Roadmap planning is—like Product Backlog refinement—a continuous effort, just at an extended cadence.

Technical Review 230

Technical Review SCRUM Estimate Cadence 230

Scrum.org

MARCH 28, 2022

Welcome to the Sprint anti-patterns article from my series on Scrum anti-patterns, covering the three Scrum roles—pardon me: accountabilities—and addressing the contributions of stakeholders and the IT/line management. Shall I notify you about articles like this one? Moreover, I add some food for thought.

SCRUM 184

SCRUM Technical Review Software Review Consulting 184

Leading Agile

AUGUST 19, 2020

We’re starting to see HBR articles written more than one. They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right? And he’s like, I want to be pissed at you when I read the title, but when I read your article, it was actually dead on, right?

Agile 100

Agile SCRUM Governance Government 100

Leading Agile

JUNE 29, 2023

My dad is a rocket scientist, and we went to Georgia Tech, where they had installed a nuclear reactor. Here are some books you need to read, try this article, attend this conference, or go to this two-day course. Our technologies often impede our ability to achieve our goals in infrastructure and operations.

Agile 75

Agile Technical Review Executing Influencer 75

Digite

MARCH 12, 2018

That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? 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.

Development Team Review 154

Development Team Review Software Review Cadence Technical Review 154

Scrum.org

AUGUST 9, 2022

If your answer to this question is: ''frequently", "often" or "always", this article might be helpful. indicated that there is still a challenging situation between their IT (sometimes called Delivery, Tech, etc.) Regardless of working for Business or Technology, be the first to start. Remember about cadences. vice versa.

Technical Review 196

Technical Review Cadence 2005 Initiating 196

Wrike

FEBRUARY 20, 2023

In this article, we discuss all you need to know about SAFe : what it is, its core principles, and its four main levels. It also includes standard Agile recurring events such as sprint planning, reviews, and retrospectives. We’ll also share how to determine if SAFe is right for your company and when best to use the framework.

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

MPUG

OCTOBER 16, 2019

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. And today’s session is eligible for one PMI PDU in the technical category, and the code for claim that is on the screen now, that’s mpugwebnlearn091819.

Agile 40

Agile Technical Review Software Review Engineering 40

Leading Agile

FEBRUARY 11, 2019

Because the recovery phase was not officially recognized (typically due to time reporting rules that prohibited honesty regarding overtime), management missed the opportunity to learn from experience and repeated the death march pattern again and again. Stable Team. Projects are assigned to stable, pre-existing teams.

Agile 115

Agile Underperforming Technical Team Software Review Technical Review 115

MPUG

MAY 18, 2022

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. If you’re brand new to Agile, there is an updated article I did, Intro to Agile Project Management. Here’s an example of a technical issue. Here we go.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

Scrum.org

SEPTEMBER 19, 2020

Do you want to get this article in your inbox? 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. Sprint Reviews are a zone free from death by PowerPoint. Scrum Events. Show, don’t tell.

Technical Review 210

Technical Review Software Review Development Team Review Cadence 210

MPUG

JUNE 1, 2022

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. When that one is going to wait two days before the assignments due to just say, hey, why don’t we change this to that? Melanie: Hello.

PMI 59

PMI Software Review Estimate Risk Management 59

Leading Agile

AUGUST 20, 2018

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. Reviewing code by eyeballing it to ensure compliance with coding standards. Security review. Handling merges of code changes made by more than one person.

Software Review 78

Software Review Software Technical Review Development Team Review 78