Agile at Scale – Outcome Driven (or Broken)

Tyner Blain

Taking agile, a process otherwise optimized for small, cross-functional, collaborative teams and making it work at scale is fascinating. ” I’ve spent the last half-year in the beginning of my journey understanding how agile product management at scale can work.

Agile 459

Capabilities Release or Cadence Release

Herding Cats

In the Agile world the phrase deliver early and deliver often is good advice. Agile developers like to toss that phrase around as an alternative to having a plan for the delivered value we'll replace planning and estimating with early and often delivery.

The Potential of Agile

Tyner Blain

When an executive, too far removed from what makes creating products hard thinks of “agile” as a silver bullet it becomes difficult to manage expectations. It is precisely that potential which inspires not-yet-informed executives to learn about how agile could help them.

Agile 309

A Comprehensive Guide to Agile Project Management

Redbooth

If you work in tech or any industry where things change fast, you probably are familiar with agile project management. Agile methods are baked into productivity tech, from Trello to Airtable to Redbooth, and can improve any large body of work, from ad campaigns to app design.

Agile 137

Maintain a sense of change urgency through agility

Kiron Bondale

The specific cadence varies based on the complexity and duration of a transformation. This is why regardless of the nature of a transformation we need to inject agility into its delivery.

Agile 181

Agile Through a Matrix Lens

Tyner Blain

Agile” is something most teams do wrong*, without realizing they’re doing it wrong. Let’s apply this lens to agile as applied within a company, and see if it helps people decide to do things differently. When You Say Agile, What Do You Mean?

2014 191

How should I handle an agile-waterfall hybrid project?

Kiron Bondale

For example, technology deliverables might be completed in an agile manner whereas change management deliverables such as training collateral get produced in a traditional manner. This can be a challenge when an agile work stream has dependencies on a waterfall work stream.

Agile 156

I get the business rationale for agile, but what’s in it for ME?

Kiron Bondale

When we read about the rationale for an agile approach to project delivery, the focus is often on the benefits realized by the company or by their customers. While we can’t marginalize the benefits of early and frequent realization of business value there is a compelling case to be made about higher levels of job satisfaction and engagement for the team members working on successful agile projects when compared with their counterparts on equally successful traditional projects.

2016 174

7 Factors for running an effective Kanban Replenishment Meeting

Digite

In 2015, in a blog post called Kanban Cadences , David Anderson laid out a set of 7 Kanban cadences or meetings that provide comprehensive opportunities for feedback, planning, and review in an enterprise.

Agile Release Train (ART)

Digite

The concept of Agile Release Train is central to understanding the constructs of SAFe and to implement them. The Agile Release Train is the primary value delivery construct in SAFe. An Agile Release Train typically consist of 50-125 people. agile Agile ALM ALM

Agile 72

Is SAFe Agile?

Digite

Since the arrival of Scaled Agile Framework in the world market, there have been comparisons ad nauseum between the Scrum and SAFe frameworks. Many industry experts have come out and pointed possible flaws in the Scaled Agile Framework. Image credits: Scaled agile .

Agile 52

ESP Compared to Kanban Method

Digite

He highlights this with the adoption path for Kanban cadences (meetings) as to how Kanban is bottom-up and inside-out approach whereas ESP is the top-down and outside-in approach. We also anticipate the adoption of the Kanban Cadences to be different.

Releases and Deadlines in Agile

Herding Cats

But Agile at Scale has a different paradigm than Agile at the Table. Cadence Release - when a fixed period ends, go with what is ready to go. Cadence Release paradigm, is a flow-based approach. The Capabilities are laid out Cadence Releases in the chart below.

Release by sprint or capability?

Musings on Project Management

One of the Agile paradigm shifts from the "way we've always done it" is to shift release planning to either fixed calendar points -- at the end of one or more sprints, but typically three or more -- or when capability needed by the business is "done" In an interesting posting, here, the first idea is given the moniker "cadence release"; the latter "capabilities release". agile planning

2016 150

Shift from Annual to Continuous Planning to Enable Agility [Webinar]

Planview

Having a regular cadence that allows you to measure value against new demand is incredibly valuable, as it isn’t disruptive when measured against the annual plan and allows you to forecast on a regular basis.

Beginner’s Guide to Kanban for Agile Marketing

Digite

We’re honored to republish this blog post ‘Beginner’s Guide to Kanban for Agile Marketing’ by Andrea Fryrear which was originally published in the Agile Sherpas blog! They also increase the number of learning opportunities for your Agile team.

SCRUM 52

GAO Cost Estimating and Assessment Guide Applied to Agile

Herding Cats

There are not specific to Agile Software Development. Agile. Agile teams, for the most part, are a fixed set of resources, so the spending plan is essentially Flat. Either a Cadence Release Plan or a Capabilities Release Plan.

When the Agile rubber hits the enterprise road

quantmleap

H aving been ‘doing’ both Waterfall and Agile for quite some time now I feel fairly qualified to point out the idiosyncrasies in both approaches. So, while I have had my fair share of frustrations with pure command-and-control organizations, my beef today is with Agile advocates that are exhibiting less than agile attitude when attempting to bring Agile into large command-and-control environments.

2015 52

How do your pods divide and conquer?

Kiron Bondale

A good practice with agile delivery is to keep team sizes small to reduce the number of communication channels. Tagged: agile project management , project decision making , Valuable projects. Agile Project Management agile project management project decision making Valuable projects

2016 170

Don’t Say NoGet Them to Understand Your Team Delivery Capacity

Leading Agile

Let’s say that on average stakeholders request a couple of large items, a couple of medium-sized ones, and five small ones in any given cadence, iteration, release, or whatever unit of time your organization uses for such matters.

Handling Unplanned Work

Leading Agile

We did our short-term planning last week and we came up with an idea of what work we would be able to complete in the next iteration or cadence. ” If you’ve chosen an “agile” approach for the work, it’s because “agile” is a fit for the situation.

2018 72

Do you deliver dazzling demos?

Kiron Bondale

DO send meeting invitations well in advance and if you are following a standard sprint or iteration cadence (e.g. While this article is primarily aimed at teams who are using an agile delivery approach, it is equally applicable to traditional projects. Tagged: agile project management , customer satisfaction , improving project management. Agile Project Management agile project management customer satisfaction improving project management

Essential SAFe 4.0 – How is it Different from SAFe 4.0?

Digite

was launched by Scaled Agile Inc. in 2016 as a method to help organizations scale up their existing agile practices. But isn’t that also the reason behind organizations adopting Scaled Agile framework in its glorious entirety? What was the need for Scaled Agile Inc.

9 Best Practices for Your Daily Scrum Meeting

Project Bliss

I proposed the Daily Scrum Meeting, along with two other activities , as an Agile practice you can adopt if you want to gain some of the benefits of Agile – even if your team hasn’t adopted full Agile. Agile takes discipline.

SCRUM 263

What’s Worse Than Not Automating Your Software Delivery Pipeline?

Leading Agile

James Grenning , a well-known leader in the embedded software field and the author of Test-Driven Development for Embedded C is also among the authors of the Agile Manifesto and an early adopter of Extreme Programming (XP). Sounds good. What are “all the things,” by the way?

Build a CI/CD Pipeline in the Cloud: Part Two

Leading Agile

Now, your friendly neighborhood Agile Coach has probably hammered home the point that every piece of work the team carries out must deliver customer value. This could be the only Story the team tackles in their first development cadence or iteration or Sprint or what-have-you.

2018 62

The Difference Between The Kanban Method and Scrum

Digite

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. In this article, he outlines the similarities of the two as WIP Limiting, Pull-based systems – with cadences and a focus on learning – while also explaining their differences. Cadences. This also includes cadences.

An Incremental Paradigm

Herding Cats

We were speaking a Homeland Security yesterday on Agile development in the Federal Government and there was a senior director who brought up a paradigm that resonated with me. Agile and Incremental and Iterative Development and Deployment.

Kanban to manage Complex/ Quick Moving Situations

Digite

At the same time, we ensure we follow many of the recommended Kanban cadences, including the Daily Standup Meeting, the Weekly Replenishment Meeting (where fine-tuning of the story/ defect prioritization takes place) as well as Release Retrospective and a Quarterly Strategy Review Meeting.

Scrum or Kanban for Application Support teams?

Digite

Frequently, especially in a Scrum environment, it can be difficult to match the cadence of doing both. Lean/ Kanban Uncategorized agile Kanban Lean Lean Software Development Project Management Scrum Visual Project Management

SCRUM 65

Kanban and Scrum Together – Not So Fast

Digite

–and– along with an absence of time-boxes or any other time-bound constraint (the Kanban cadences are not constraints). Regarding cadences not being constraints, I would posit that a Replenishment meeting with a cadence of 2 weeks is exactly the same kind of a time-bound constraint as a Sprint Planning meeting that happens every 2 weeks. Lean/ Kanban agile Kanban Lean Scrum WIP WIP limit

SCRUM 40

To See or Not to See?

Digite

As you may all be familiar by now, the few Kanban principles that are most commonly applied to software are Visualization, Map the Value Stream, Limiting WIP, Removing Impediments to flow and Regular Cadence & Measurements for continuous improvements. It is not enough to Visualize.

Deliver Fast or Deliver as Planned (Update)

Herding Cats

A popular mantra in Agile is deliver fast, deliver often. Where we work and where agile is becoming the norm, we have another view. The notion of agile is the basis of all military process, not just 5 coders in the room with their customer. Agile Capabilities Planning

Using Kanban in Marketing

Digite

I was learning several new concepts including Lean, Agile, Application Lifecycle Management (ALM), Project Program Management, etc. Our Cadences. Kanban Lean/ Kanban Uncategorized agile continuous improvement Kanban in Marketing Lean marketing management

Unravelling PI Planning

Digite

There is a quote introducing PI Planning content on the Scaled Agile Framework website. A Program Increment is a fixed timebox of 8 to 12 weeks (default being 10 weeks as recommended by Scaled Agile Inc.). SAFe Uncategorized agile PI Planning Program Increment Release Train Engineer

The Tangible Value of The “Intangibles”

Digite

This approach can be easily extended to strive for uniform cadence across the value stream. Kanban Lean/ Kanban agile class of service CoS LeanOne of the important aspects of The Kanban Method is Class of Service (CoS). CoS is a risk categorization mechanism for any work item.

Kanban = Continuous Delivery? Not Necessarily

Digite

We do product releases every 4-6 weeks, and these get deployed to our SaaS servers – that cadence is well established. Lean/ Kanban agile Kanban Lean Lean Software Development Management Release Management Scrum

Is Macroeconomics and Social Science the Same as Software Development?

Herding Cats

There a popular notions in the agile development world that authors like Hayek and Taleb speak to how software development works. You Can’t Understand Agile Without Understanding Hayek. This is the basis of the Agile Product Roadmap and Product Release Plan (either cadence or capability based). This is also the core principle of Agile - evolutionary emergence of the needed requirements to fulfill the needed Capabilities. .

2016 36

Team using “Waiting for Release” column on their kanban board

Digite

We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established. Lean/ Kanban agile Kanban Lean Lean Software Development Management Release Management ScrumHere’s is another question that I recently answered on a discussion forum –. “My My team is using Kanban board but they seem to prefer to collate a couple of tickets then ‘do a release’ as appose to releasing each ticket.

What Are OKRs? How to Use OKRs for Planning (and Achieving) Your Goals

Planio

Is the OKR adaptable and agile? Remember to make sure your Key Results are adaptable and agile enough that they can be completed in many ways. Because of the Agile nature of OKRs, it’s important to set and stick to regular check-ins.

2018 94

A Review Of Scrum For Kanban Teams

Digite

The explicit inclusion of the Scrum Values is a relatively recent ( 2016 Scrum Guide ) addition, but the Agile Manifesto is definitely a value system and Scrum fully supports those values. Kanban teams are fully capable of doing everything that Scrum teams do, described as some sort of feedback meetings that happen on a cadence. Software development teams, striving to be agile, using Scrum or Kanban, will generally need/produce the same things.

SCRUM 40

Same Same but Different †

Herding Cats

Much of the conversation in social media around agile techniques seems to be based on the differences between the variety of choices of a method, a process, or a practice and definitions of terms for those choices. Both agile advocates and engineered systems advocates practice innovation and creativity. Why are the core principles of managerial finance and the microeconomics of decision making in the presence of uncertainty rejected by the agile development community? .

How Charles Byrd Gets It Done: Project Management & Networking Tips

Project Management Hacks

Out of college with a BBA in information technology I started on a help desk providing 2nd and 3rd level support for Cadence, a Silicon Valley software company. An Agile approach wins every time in these situations due to its inherent flexibility and delivery focus.

2016 83