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 24, 2019

Tech Infrastructure != Many organizations divide their technology stack between front-end and back-end systems and place an API boundary between the two. This is a slightly broader definition of “front-end” that we normally hear from, say, web app developers. Value Stream. Half-Agile Transformations.

Technical Review 115

Technical Review Agile Infrastructure Cadence 115

Scrum.org

MARCH 14, 2023

In Scrum terms, this is about improving upon the Definition of Done. 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. with a product backlog).

Agile 193

Agile Cadence Technical Review Development Team Review 193

Scrum.org

JANUARY 22, 2020

Scrum, in its more general definition, is a simple framework to help us address complex challenges. Product development is the subset of complex problem domains where Scrum took root first; by explicitly acknowledging software and new product development to be complex work, serving to deliver complex products in complex circumstances.

Cadence 200

Cadence SCRUM Software Review Technical Review 200

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

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 134

Cadence Development Team Review Software Review Technical Review 134

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 110

SCRUM Development Team Review Technical Review Cadence 110

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 126

Cadence Development Team Review Software Review Technical Review 126

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

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. Once a Product Backlog item meets the Definition of Done, it can be released into the hands of users.). A new Sprint starts immediately after the conclusion of the previous Sprint.

SCRUM 151

SCRUM Technical Review Software Review Consulting 151

Planio

JULY 4, 2022

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. Agile is an umbrella term for different iterative and feedback-driven software development processes. (And why do they matter?).

Agile 88

Agile Technical Review Development Team Review Software Review 88

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

APRIL 4, 2023

The Scaled Agile Framework wasn’t exactly what the authors of the Agile Manifesto imagined 20 years ago when they set out to define a better way of building software. It requires the ability to continuously deploy software, to continuously get feedback on it. And by the definition of Agile, it absolutely isn’t, right?

Technical Review 88

Technical Review Agile SCRUM Governance 88

Digite

JUNE 13, 2018

Anderson best articulated its application to software development, in 2013, in the foundational book Kanban: Successful Evolutionary Change for Your Technology Business, and its adoption hasn’t been as universal as Scrum’s during the early days of Agile software development. You have permission to modify your process.

Agile 110

Agile Technical Review Cadence Software Review 110

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

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 79

Software Review Technical Review Cadence SCRUM 79

Gunther Verheyen

DECEMBER 20, 2019

Scrum, in its more general definition, is a simple framework to help us address complex challenges. Product development is the subset of complex problem domains where Scrum took root first; by explicitly acknowledging software and new product development to be complex work, serving to deliver complex products in complex circumstances.

SCRUM 55

SCRUM Cadence Software Review Technical Review 55

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. And you know, this is what it means to get to a definition of done. Are we doing reviews? What kind of reviews and retrospectives are we doing and how are we doing them? Is there a product owner?

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

APRIL 20, 2023

We can make our bottom box bigger with some technologies and some expertise, some experience. And teams have a cadence where they’re operating with intent but within constraints. Some organizations do operations reviews or bigger retrospectives. I might be smaller in some cases for outsourcing things.

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

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

JANUARY 21, 2021

So it’s like the ability to form teams, the ability to create clear backlogs the ability to get to a working tested increment of software at the end of every sprint. So again, I’m anchoring not on feature level agility that we often talk about when it comes like agile software development but how do I pivot an organization?

Sustainability 84

Sustainability Agile SCRUM Technical Review 84

Workamajig

JANUARY 11, 2021

Activity ID: An alphanumeric code used to identify an activity. The agile approach is usually used in software projects where the scope is not always known and adaptability is prioritized. Projects might additional calendars as well to show resource availability, communication cadence, etc.

Underperforming Technical Team 78

Underperforming Technical Team Project Life Cycle Estimate Risk Management 78

Leading Agile

AUGUST 19, 2020

So the first lens or the first set of foundational things that we’re going to talk about when it comes to predictability is the idea of the three things, teams, backlogs, working tested software. They deliver it, they review it with the product owner, product owner says yes, and then they get to claim the points, right?

Agile 89

Agile SCRUM Governance Government 89

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. 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 17, 2021

Do they own the technology or do they have dependencies with tons of teams around them? But what I would suggest that it’s only a concern to the extent that we’re a profitable company, that we can put out software when we say we’re gonna put out software or put out product, when we say we’re gonna put out product.

2021 62

2021 Agile Underperforming Technical Team SCRUM 62