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 143

SCRUM Development Team Review Technical Review Cadence 143

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. In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. What we REALLY mean when we say Working Software. Can it also be a release cadence?

Cadence 131

Cadence Development Team Review Software Review Technical Review 131

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 115

SCRUM Development Team Review Technical Review Cadence 115

Scrum.org

FEBRUARY 22, 2021

To prevail in today’s game of an accelerated innovation-based competition—software is eating the world—, every organization needs to acquire a holistic understanding of an agile product creation process: A vision leads to a strategy that (probably) results in a portfolio of products (and services). Then we don’t have those questions anymore.”

Software Review 156

Software Review Technical Review Cadence SCRUM 156

Planio

AUGUST 9, 2021

What is the best project scheduling software to use? Monday.com: Best for non-technical teams. For example, maybe you need to finish cleaning out old code or squash some lingering bugs before building out new features. Ask each person to help estimate their workload, uncover dependencies, and set deadlines for due dates.

Software Review 78

Software Review Technical Review Estimate Agile 78

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. There will be stress.

Software Review 98

Software Review Technical Review Cadence SCRUM 98

Wrike

DECEMBER 20, 2021

However, this interaction will require the use of new technology and strategies to manage it properly. Some tasks are more easily carried out when team members are located close to one another. Technology plays a huge role in that. There are many advantages to having face-to-face interaction with employees.

2022 41

2022 Artificial Inteligence Technical Review Cadence 41

Scrum.org

MARCH 11, 2024

Every activity required to achieve the Product Goal, such as Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, occurs 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.

Technical Review 186

Technical Review Underperforming Technical Team SCRUM Software Review 186

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. Some organizations do operations reviews or bigger retrospectives.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Leading Agile

MARCH 31, 2020

. – I was working in my office down in technology Parkway. 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. And BPR was about the technology. How do you like fix it?

Agile 71

Agile Technical Review SCRUM Engineering 71

Scrum.org

JULY 31, 2023

They did not have the skills or authorization to make software and configuration changes in the banking systems. Their work was restricted to: specifying changes requested by the operational teams, assigning them as tasks to technical teams somewhere in the adjacent IT group, chasing progress.

Technical Review 167

Technical Review Software Review 2022 2021 167

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 184

SCRUM Technical Review Software Review Consulting 184

Planio

JANUARY 11, 2021

Timing and team cadence: Decouple team cadences whenever possible. A major part of project management is adding restraints and order to the chaos of building software. Timing and team cadence: Decouple team cadences whenever possible. Finally, you could avoid company-wide cadence entirely like the team at Gumroad.

Underperforming Technical Team 88

Underperforming Technical Team Cadence CTO Hire Technical Review 88

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 131

Agile Governance Government Underperforming Technical Team 131

Planio

APRIL 24, 2023

Updating project management software to keep their team on track 9. But over the years, project managers have learned to follow a strict project lifecycle, which helps them manage every step of the journey, from establishing initial goals to handover and closing. Assessing and mitigating project risks 7.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Scrum.org

APRIL 11, 2019

Delivering working software is perceived as an IT responsibility instead of a Business-IT collaboration. I was successful with optimising for feature size that could be delivered in a two-sprint cadence. Connect the dots by making reporting on market research data and customer feedback data a mandatory item of the Sprint Review.

Underperforming Technical Team 153

Underperforming Technical Team SCRUM Development Team Review Software Review 153

Leading Agile

JUNE 29, 2023

My dad is a rocket scientist, and we went to Georgia Tech, where they had installed a nuclear reactor. So, who is responsible for closing that gap? Executives aren’t solely focused on delivering software to customers. Our technologies often impede our ability to achieve our goals in infrastructure and operations.

Agile 75

Agile Technical Review Executing Influencer 75

Scrum.org

AUGUST 9, 2022

indicated that there is still a challenging situation between their IT (sometimes called Delivery, Tech, etc.) Business does not understand the complexity of software development or engineering work. Technology departments struggle with empathizing with Business, customer-faced teams, not understanding how hard their work is.

Technical Review 196

Technical Review Cadence 2005 Initiating 196

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 115

Agile Underperforming Technical Team Software Review Technical Review 115

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. Business, Technical, Systems, Risk, and Project Management Briefings and Presentations.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

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

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

Workamajig

JANUARY 11, 2021

Activity ID: An alphanumeric code used to identify an activity. Administrative Closure: A list of the requirements necessary to formally close the project. The agile approach is usually used in software projects where the scope is not always known and adaptability is prioritized.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

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 78

Software Review Software Technical Review Development Team Review 78

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. As I was introduced, I was a software and programming instructor for many years.

PMI 59

PMI Software Review Estimate Risk Management 59