Scrum.org

MARCH 14, 2023

And in the 21st century for software development teams, this means realizing the paradigm of Continuous Delivery. Plus, the technical capabilities in the form of teams focused on the value as goals and priorities. After focusing, delivering goes – as a shift towards creating customer-facing self-managing teams.

Agile 197

Agile Cadence Technical Review Development Team Review 197

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 136

SCRUM Development Team Review Technical Review Cadence 136

Rebel’s Guide to PM

AUGUST 6, 2022

Strong leadership in projects is important for success, so getting your project board and/or project steering group set up as soon as you can is a good start. For example, on one project, I had the CFO steering group, and attendees were all SLT (senior leadership team members). Who will get you access to the resources you require?

Governance 371

Governance Government Risk Management Technical Review 371

Scrum.org

MAY 27, 2021

“Such teams are typically well suited to periods of disruption, given their ability to adapt to fast-changing business priorities, disruptive technology, and digitization.”. We know Agile is not just for software teams. 4 – The Review. At the end of the sprint, after the Review, you have the Retrospective. 1 – Planning.

Agile 248

Agile Cadence Technical Review Software Review 248

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 113

SCRUM Development Team Review Technical Review Cadence 113

Agilemania

DECEMBER 13, 2021

41% proclaimed absence of leadership to be the main problem. The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. Code Quality. Leadership: SAFe inculcates the Lean-Agile mindset which is necessary to become a Lean-Agile leader.

Agile 98

Agile Lean Software Review Technical Review 98

Leading Agile

JULY 18, 2023

Third, how are we reproducing working tests in software? When people make such statements, they usually mean that they have trained product owners and a proficient Scrum master, and their team consistently follows the cadence of sprint planning, daily stand-ups, interviews, and retrospectives. First, how are we forming teams?

Agile 109

Agile Software Review Certification Technical Review 109

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. This also applies to refactoring parts of the tech stack, exploring new technology that might be useful, fixing some bugs, or sharing knowledge with fellow teammates.

SCRUM 156

SCRUM Technical Review Software Review Consulting 156

Velociteach

FEBRUARY 1, 2023

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. Projects where the problem and technical complexity are low, and the cost of change is high may favor a predictive methodology.

Planning 52

Planning Technical Review Governance Government 52

Leading Agile

APRIL 7, 2023

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. Total chaos.

Agile 133

Agile Governance Government Underperforming Technical Team 133

Planview

JUNE 1, 2021

Hosted by CITF, the UK’s leading membership organization for technology professionals, the webinar includes our insights and recommendations on extending Agile practices. Read on to review some answers to questions asked during the webinar along with a few of our other recommendations. His leadership has made our process seamless.

Cadence 148

Cadence Logistics Lean Agile 148

Planio

JULY 4, 2022

But often, the real issue is that they’re missing a key ingredient: leadership. Sprint review ceremony. Agile ceremonies — also known as Scrum ceremonies or just ‘events’ — are specific events that provide a structured framework for iterative software development processes. What are Agile ceremonies? And why do they matter?).

Agile 88

Agile Technical Review Development Team Review Software Review 88

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. According to research published in Harvard Business Review , nearly 90% of companies struggle to complete Agile transformations — even after successful pilot projects. Build a leadership team that can get your required buy-in.

Agile 78

Agile Technical Review Leadership Infrastructure 78

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

Resource Guru

SEPTEMBER 27, 2023

Setup also reveals key reasons for clients leaving agencies as: client dissatisfaction with strategic approaches, and changes in agency leadership and personnel Miscommunication is fertile ground for misunderstandings and frustrations. Failure to do so falls squarely on leadership and project managers concerned about retention.

Technical Review 52

Technical Review Underperforming Technical Team Software Review Transportation 52

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 97

Agile Underperforming Technical Team Software Review Technical Review 97

Wrike

DECEMBER 20, 2021

However, this interaction will require the use of new technology and strategies to manage it properly. Alongside that, full-time employees are increasingly working as members of dispersed, global teams, communicating and coordinating via online software and apps. Technology plays a huge role in that.

2022 41

2022 Artificial Inteligence Technical Review Cadence 41

Wrike

FEBRUARY 20, 2023

It is especially useful in software development and enterprise product management as these teams tackle projects and programs on extended timelines with continuous improvements, upgrades, and iterations released and delivered to customers over time. What is the Scaled Agile Framework?

Agile 36

Agile Development Team Review Lean Underperforming Technical Team 36

Leading Agile

APRIL 20, 2023

I think the servant leadership coaching world has talked about just be there for your teams and support them. I’m a huge advocate of servant leadership and taking care of your teams. We can make our bottom box bigger with some technologies and some expertise, some experience. This is a leadership responsibility.

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

PMI 59

PMI Software Review Estimate Risk Management 59

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?” However, this is not always the case, even when leadership teams are fully committed to Agile.

Agile 62

Agile Technical Review Governance Government 62

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

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 63

Agile Technical Review SCRUM Engineering 63

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. Here’s an example of a technical issue. Lewis’ and James Mills JR.’s Here we go.

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. Is it the leadership’s responsibility for being agile, right? Anybody on that boat you rush, you guys just aren’t raising your hands. Is it the teams?

Governance 62

Governance Government SCRUM Agile 62

Leading Agile

MARCH 17, 2021

Do they own the technology or do they have dependencies with tons of teams around them? And all that stuff’s like really super important, but we have this debate internally quite a bit with my leadership team. And business architecture kind of a nebulous term, but how do you form teams? What do you organize those teams around?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62