ESP Compared to Kanban Method


David Anderson is a thought leader and pioneer in the field of Lean/ Kanban for Software Development and managing effective software teams. We also anticipate the adoption of the Kanban Cadences to be different.

The Potential of Agile

Tyner Blain

In stochastic systems, such as software development, the amount of time required to implement any particular feature (supporting a capability, and therefore the solution of a valuable problem) varies. Most people see – and act on – the cadence of development and delivery.

Agile 245

Agile at Scale – Outcome Driven (or Broken)

Tyner Blain

I “went agile” in 2000/2001 – I was writing software and leading teams at an enterprise software company at the time, and we adopted elements of XP and other agile practices in what we branded (internally and externally) as Fast Cycle Time (FCT).

Agile 383

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. Let's look at the thesis of Hayek in light of software development and the decisions that must be made when spending other people's money in the presence of uncertainty. He was not a program manager of engineered to order software intensive system of systems. Macroeconomics is the dismal science - treat it as such when developing software.

2016 52

A Comprehensive Guide to Agile Project Management


The model has been favored by software engineers for its efficacy and flexibility, and it’s beginning to catch on in agencies and startups. The quick cadence of sprints is balanced by the support of standups and reviews.

2018 83

Beautiful Example of the Disconnect Between Those who Pay and Those Who Spend

Herding Cats

How many more working demos will be coming before we can go live with the software I'm paying you to build? How many more working demos before we can start shipping the production version of the software he's paying us to build? Software Engineering is a Verb.

Quote of the Day

Herding Cats

This is called Software Engineering Economics. Herding Cats: Capabilities Release or Cadence Release. Better have a plan to reduce technical and programmatic uncertainty (both of which have aleatory and epistemic behaviours respectively) at a planned rate, for a planned cost, on a planned time. Or plan on being late, over budget, and reduced probability of technical success, before you start. All Value is Cost and Time dependent.

Kanban = Continuous Delivery? Not Necessarily


From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. We do product releases every 4-6 weeks, and these get deployed to our SaaS servers – that cadence is well established.

2018 52

How to Make Your Project Schedule Work for You


And, by incorporating schedule metrics and weekly reviews into the project cadence, the team and your stakeholders will have a better understanding of the changes in the project schedule. Featured Project Management SoftwareAt a recent conference, I was asked, “Why do project managers hate schedules?”. I had to think about this for a while because I don’t think project managers hate schedules.

2016 55

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


From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established. Kanban has a really simple, yet critical feature, that provides the most elegant solution to a problem that has forever dogged most software teams and their customers! Here’s is another question that I recently answered on a discussion forum –. “My

2018 46

The Difference Between The Kanban Method and Scrum


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. Both methodologies believe in delivering software incrementally to maximize the opportunity to get feedback and capture ROI. Incremental delivery of software also mitigates risk and maximizes the opportunity to learn from a business, process, and technical perspective. Cadences.


GAO Cost Estimating and Assessment Guide Applied to Agile

Herding Cats

There are not specific to Agile Software Development. Either a Cadence Release Plan or a Capabilities Release Plan. The GAO Cost Estimating and Assessment Guide has 12 steps. These describe the increasing maturity of the project's artifacts.

Why Write Requirements

Tyner Blain

The cadence by which you update those requirements as you get smarter (learning more about your market, adapting to changes in your market, etc) and your team consumes those updates will impact the team’s ability to stay focused on a – by definition – moving target.

2013 190

An Incremental Paradigm

Herding Cats

Like the agile incremental house cartoon, or the bicycle morphing into a car, NO discussion of the incremental or iterative development of software can take place without a Product Roadmap and Release plan.

When the Agile rubber hits the enterprise road


The reality in such circumstances is that while the software development aspect of the project/program can utilize Agile methods, the project in its entirety is still bound to interface with non Agile delivery teams, operating with a different cadence, different milestones, and different operational requirements. 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.

2015 52

Difference Between Agile Project Management and Scrum

Brad Egeland

There has been a rise in the transition of project management, product management and software development teams from traditional Waterfall methodologies to Agile ones. Those who don’t know much about agile, are also unaware of its popular frameworks like Kanban that is used to implement agile software development. An incremental, iterative approach to software development is called Agile.


A Review Of Scrum For Kanban Teams


It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. Kanban teams are fully capable of doing everything that Scrum teams do, described as some sort of feedback meetings that happen on a cadence. People on software development teams, regardless of Scrum or Kanban, will goal set, seek feedback, deliver increments of product, and reflect on how they work.


Agile Release Train (ART)


Program Increments (PIs) provide a development timebox (default 10 weeks) that uses cadence and synchronization to facilitate planning, limiting WIP, provide for aggregation of value and assure consistent retrospectives.

Agile 72

Kanban to manage Complex/ Quick Moving Situations


In my over 25+ years in the software industry, this has been an all too familiar situation! I have often wondered – doesn’t speak too well of us as software professionals! Is this you?

2018 74

Same Same but Different †

Herding Cats

These systems fall into the Software Intensive System of Systems (SISoS) category. The notion that innovation and engineering - software engineering - are somehow in conflict is common. . In the software engineering domain, like the developer domain, design is the basis of this innovation. Regular delivery of incremental business value - defined in a Product Roadmap, scheduled in a Cadence or Capability release plan. Two Books in the Spectrum of Software Development.

Is SAFe Agile?


At this level, we have an Agile team that is cross-functional and works together to deliver working software every 2 weeks (or 4 weeks as per the discretion of the teams) – which are called Iterations. This ensures that the Software is maintained in a releasable state always.

Agile 52

Deliver Fast or Deliver as Planned (Update)

Herding Cats

The Plan for the delivery of value is shown in the Product Roadmap and implemented in the Cadence Release Plan, or sometimes in the Capabilities Release plan. But when we enter the Agile At Scale domain - ERP, Enterprise IT, Software Intensive System of Systems - we've got a separate issue.

To See or Not to See?


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.

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.

2016 83

Using Kanban in Marketing


However, I had not seen Kanban being applied to software development, project management, etc. I got to understand much better the application and benefits of the Kanban method for software Development and knowledge work. Our Cadences.

Give a Damn: Why You Need A Mentorship Relationship

Function Point

Now please understand, I was not in the software business and I didn’t know how to write code at the time, so this was not an easy concept to jump into. She guides us in creating a business cadence through the use of the One Page Plan. Function Point Productivity Software is the leading all-in-one project and task management software, specially designed for ad agencies, design studios and internal marketing departments looking to streamline their business.