Rebel’s Guide to PM

AUGUST 6, 2022

And will make the decision to close the project down early if it can no longer meet its objectives. It’s fine to have a different cadence at different points in the project lifecycle. Make sure you have the latest info on project budgets and how close the project is to meeting its goals. When to hold the meetings. Key decisions.

Governance 363

Governance Government Risk Management Technical Review 363

Scrum.org

OCTOBER 2, 2018

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. The Sprint Increment Got Us Here.

Cadence 127

Cadence Development Team Review Software Review Technical Review 127

The Strategic Project Manager

JUNE 28, 2022

This post outlines the essentials of the agile scrum process. It then delves a little deeper into the most important element of the process – the sprint. It then looks at implications of the agile scrum process for project management and strategy. A Basic Agile Scrum Process Diagram. Sprints and the Team.

Process 40

Process SCRUM Agile Cadence 40

MPUG

DECEMBER 28, 2020

It’s less prescriptive and seems to be intended for a wider audience group, particularly non-software users. However, as you look closely at the new guide, a big picture emerges: The Product Goal is the long-term objective of the team. Introduction of Cadence. The diamond shapes in the cadence stream denote the Sprint Reviews.

Cadence 116

Cadence SCRUM 2020 Agile 116

Scrum.org

FEBRUARY 22, 2021

Meanwhile, some ideas have gained buzzword status in the process, causing the occasional collateral damage along the way. This core agile product creation process is agnostic to the product delivery framework, be it Scrum, XP, or any other framework. Think of “MVP.”). Download for free : The Scrum Anti-Patterns Guide.).

Software Review 141

Software Review Technical Review Cadence SCRUM 141

The Strategic Project Manager

OCTOBER 12, 2022

The concepts of scrum are powerful in business, not only in software development but also in other areas. This post reviews the basics of agile scrum roles, ceremonies, and their impact on developing strategy and managing projects. Here is a list of the primary agile scrum ceremonies that together constitute the agile scrum process.

SCRUM 98

SCRUM Agile Lean Cadence 98

MPUG

SEPTEMBER 4, 2023

As we will see, agile methods are, to a degree, a response to the kind of risks that software development projects face. The attitude to risk The risk attitude of your customer, client, users, or sponsor will dictate not only what risks you are willing to accept (risk tolerance), but also the intensity of your risk management processes.

Risk Management 98

Risk Management Risk Agile Technical Review 98

Planio

JANUARY 11, 2021

In this guide, we’re going to cover the tools, processes, and cultural shifts you need to make to successfully collaborate from wherever you are, Jump to a section: How to reverse Remote Sprawl: 10 reasons teams spread across time zones fall apart (and how to avoid them). Timing and team cadence: Decouple team cadences whenever possible.

Underperforming Technical Team 88

Underperforming Technical Team Cadence CTO Hire Technical Review 88

International Institute for Learning

APRIL 19, 2023

DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. To coordinate the teams, SAFe applies cadence and synchronization. Cadence means all teams are aligned to a standard, two-week delivery cycle. They emerged about a decade after the Agile Manifesto.

Agile 59

Agile Cadence Certification Lean 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. Handling merges of code changes made by more than one person.

Software Review 55

Software Review Software Technical Review Development Team Review 55

Agilemania

DECEMBER 2, 2021

SAFe endorses alignment, transparency, collaboration, and product delivery involving large size teams.The core of SAFe is based on four bodies of knowledge which are agile software development, lean product development, systems thinking, and DevOps. Apply cadence and synchronize with cross-domain planning. Take an economic view.

Technical Review 98

Technical Review Agile Software Review Lean 98

Leading Agile

APRIL 7, 2023

We pull the customer close. That having weekly planning cadences; daily standups, reviews, and retrospectives would give people a reason to get in the same room and collaborate. Things really take off with the advent of the CSM certification and PMI finally recognizing Agile as a legitimate way to do software project management.

Agile 133

Agile Governance Government Underperforming Technical Team 133

Scrum.org

MARCH 28, 2022

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. It is all about getting things out of the door, thus closing the feedback loop and starting another round of inspection and adaption. . 28 Sprint Anti-Patterns.

SCRUM 159

SCRUM Technical Review Software Review Consulting 159

Scrum.org

NOVEMBER 7, 2018

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. SAFe has a cadence at the Team and Program levels.

SCRUM 137

SCRUM Development Team Review Technical Review Cadence 137

The Strategic Project Manager

NOVEMBER 7, 2022

The sprint cycle includes key ‘ceremonies’: sprint planning, daily scrum, sprint review, and sprint retrospective. Extreme Programming (XP) – XP is focused on software development – but that does not mean it cannot be applied elsewhere! The agile methods described are primarily focused on software development.

Agile 52

Agile Software Review Cadence SCRUM 52

Planio

APRIL 24, 2023

Updating project management software to keep their team on track 9. According to the Association for Project Management : “Project management is the application of processes, methods, skills, knowledge, and experience to achieve specific objectives, according to defined acceptance criteria, within agreed parameters.”

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Scrum.org

NOVEMBER 7, 2018

To use the leadership styles model we discuss in the Leading SAFe class - the starting point is more of an orchestrating and technical expert kind of leadership stance and the goal should be to evolve towards a more serving the team and the process style over time. SAFe has a cadence at the Team and Program levels.

SCRUM 112

SCRUM Development Team Review Technical Review Cadence 112

Scrum.org

NOVEMBER 16, 2018

Waterfall projects rarely work because it doesn’t account for the micro, and sometimes macro changes that happen in the process. Is it software based or do users use physical boards? My clients get to decide the cadence of our “events.” You don’t “do” Agile, you become it, and Scrum is a means to that ultimate end.

SCRUM 119

SCRUM Cadence 2018 Agile 119

Planio

AUGUST 9, 2021

What is the best project scheduling software to use? For example, maybe you need to finish cleaning out old code or squash some lingering bugs before building out new features. The ‘scheduling’ part of a project schedule should be a collaborative process. Come up with a plan for updating and adapting your schedule.

Software Review 78

Software Review Technical Review Estimate Agile 78

Agilemania

MARCH 19, 2021

The vital aspect of the process must be transparent to people who are involved in the outcome. Those involved in the process should also inspect the product backlog, sprint backlog, and the increment to progress towards the product goal. Software Development. Use visual management to improve flows and processes.

SCRUM 98

SCRUM Lean Software Review Cadence 98

Velociteach

NOVEMBER 20, 2023

A Cadence to Managing Projects BILL YATES: Okay. There’s a cadence. There’s a cadence. Daily scrum meetings on every two weeks after you have your reviews; right? And so there is a structure and a pattern to the process, and it’s the same way in music. Every two weeks you’re delivering something. That’s so good.

Underperforming Technical Team 99

Underperforming Technical Team Cadence Certification Consulting 99

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. People leave and are replaced with new team members who don’t know the code base or the organization’s internal procedures. Scrum calls the list the Product Backlog.)

Software Review 79

Software Review Technical Review Cadence SCRUM 79

Leading Agile

FEBRUARY 11, 2019

It’s time now to move forward to the next level of proficiency in software delivery; what we might call “post-Agile.” Today, some of the same principles seem to present impediments or unnecessary challenges for many teams and organizations. How can the same principle be a good idea in 2002 and a bad idea in 2019?

Agile 94

Agile Underperforming Technical Team Software Review Technical Review 94

Agilemania

FEBRUARY 22, 2021

The vital aspect of the process must be transparent to people who are involved in the outcome. Those involved in the process should also inspect the product backlog, sprint backlog, and the increment to progress towards the product goal. Software Development. Use visual management to improve flows and processes.

SCRUM 52

SCRUM Lean Software Review Cadence 52

Planio

OCTOBER 15, 2020

Update your communication processes to understand when your remote workers need help. But to learn what it takes to really manage and lead a remote team, we spoke to remote managers at some of the world’s top companies, including Buffer, Zapier, Remote Year, Close, and Dribbble. Remote teams can easily drown in communication tools.

Underperforming Technical Team 88

Underperforming Technical Team Cadence Software Review Controlling 88

Scrum.org

AUGUST 9, 2022

between these departments regarding their way of working and processes. Business does not understand the complexity of software development or engineering work. organizations, I encountered close collaboration between parties. Is it a process? Once you have a goal, it is crucial to measure the progress on cadence.

Technical Review 171

Technical Review Cadence 2005 Initiating 171

Leading Agile

APRIL 20, 2023

But basically agile small teams working together are close to the surface. So this is why agile teams work and it’s also why we actually want Agile teams in Big Waterfall, big complex projects because we need those teams to operate close servers. I might be smaller in some cases for outsourcing things.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

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. Today’s PMI activity code, I’ll have up on the screen here in a minute. Jeff: Here are our process groups. Here are different processes.

PMI 59

PMI Software Review Estimate Risk Management 59

Wrike

DECEMBER 20, 2021

Over the past year, more companies have started using Agile methods to improve their project management processes. Some tasks are more easily carried out when team members are located close to one another. Others use project management software such as Wrike to plan, schedule, and monitor progress across all active initiatives.

2022 41

2022 Artificial Inteligence Technical Review Cadence 41

Workamajig

JANUARY 11, 2021

Acceptance Test: A process through which a project's end users run through the project to identify any potential issues before it can be formally accepted. Activity ID: An alphanumeric code used to identify an activity. Administrative Closure: A list of the requirements necessary to formally close the project.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

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. For those of you who are PMPs, your activity code today is on the screen. I’ll also invite you to stay on after the event and the recording closes.

Agile 59

Agile Underperforming Technical Team Software Review Cadence 59

Leading Agile

JUNE 29, 2023

So, who is responsible for closing that gap? Remember, our actions play a significant part in this process. It’s not a one-time switch; it’s a gradual process. Executives aren’t solely focused on delivering software to customers. Our goals and their goals may not be aligned.

Agile 77

Agile Technical Review Executing Influencer 77

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

Herding Cats

APRIL 16, 2019

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Management Processes (#MP). Agile Software Development (#ASD). Management Processes.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

OCTOBER 3, 2023

And so we ended up with a lot of folks doing standups and sprint planning and story cards and sticky notes and burndown charts and reviews and retrospectives. And so I was thinking about Scrum and so I just lifted this off of Mike Cone’s website and it’s attributed, so I hope he doesn’t mind too much mountain good software.

Governance 62

Governance Government SCRUM Agile 62

Leading Agile

MARCH 31, 2020

You leave like pretty close and you’re thinking about this in very similar ways. You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. Again, it was kinda like, which process do you pick? – That’s right. How do you like fix it? – Yeah.

Agile 63

Agile Technical Review SCRUM Engineering 63

MPUG

FEBRUARY 11, 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. This session is eligible for 1 PMI PDU in the strategic category, and the MPUG activity code for claiming the session is on the screen now. So what is a workspace?

Software Review 52

Software Review 2020 Risk Management Governance 52