A few posts back, I asked if an agile team should be expected to call their shots. In other words, should we expect that over time, an agile team should be able to accurately predict what they’ll be able to deliver at the end of the iteration? My asse…
Uncategorized
Enterprise Velocity, velocity
What do I look for day-one coaching an agile team? The first thing I want to know is if the team is really a team? Do they have everything (and everyone) they need to deliver an increment of working software? Do they plan together, do they work toge…
Uncategorized
Enterprise Velocity, velocity
So many folks want to flip a switch and magically become agile. They want all the benefits without any of the hard work that comes along with really transforming the organization. People think that just because they read a book… or took a few days …
Uncategorized
Agile Transformation, Enterprise Velocity, velocity
If you were going to write a book using agile methodologies, what might that look like? You might be inclined to create a backlog of topics… maybe play a little planning poker to get some idea of how big your book is in story points. You’d start wr…
Uncategorized
7 Habits, Agile Methodologies, Agile Methods, Backlog, Book Writing, Capabilities, Conversations, Decisions, Double Loop, Final Draft, Goodness, Poker, Publisher, Rethinking the Agile Enterprise, velocity, Write A Book, Writing Project
Earlier today we noodled on the secret sauce… maybe even THE most important value add… of implementing a Kanban system. Kanban gives us a very visual way of identifying and elevating the constraints in our system. The ONLY way to really get a tea…
Uncategorized
Backlog, Batch Size, Batch Sizes, Boundaries, Constraints, Cycle Time, Environments, Iteration, Iterations, Kanban, Kanban System, New Feature, Single User, Throughput, velocity, Wasteful Activity, Window Of Time
Last week I did a post called “The Hard Reality”. I made the point that anything you build… any document you create… that doesn’t result in revenue for the business… is wasting time and money. Personally, unless you build software as a hobby……
Uncategorized
Absolute, Great Software, High Quality Software, Making Money, People, Performance Time, Prerequisite, Quality Constraints, Quality Performance, Sake, Scope, Selling Software, Software Metrics, Software Teams, Time And Money, Time To Market, value, velocity, Wasting Time
We all want to be really good at what we do… we strive to get better… we want to think that we are making a contribution to the success of our organizations… we want to think that we are adding value. The hard reality… and one we NEED to reall…
Scrum
Circle Of Influence, Design Documents, Impediments, Kanban, Lean, Product Delivery, Relentless Focus, Revolutionary Ideas, Scrum, Self Organization, Success, Time And Money, velocity, Wasting Money, Wasting Time, Working Software
Is there a difference between the value a team delivers and their velocity? Said another way… if I increase the velocity of the team… aren’t I getting more value from them over time? Like so many things we talk about here… the answer really dep…
Uncategorized
Backlog, Correlation, Enterprise Velocity, Great Stuff, Iteration, Many Things, Market Teams, product owner, Relationship, Relative Size, Sales Marketing, value, Value Features, velocity
A rejection of the idea that agile teams should use a Release Backlog in addition to the already generally accepted Product and Sprint (or Iteration) Backlogs.
Uncategorized
agile release planning, Backlog, Backlogs, Contracts, Conventional Product, Conversations, Estimating and planning, Guarantee, High Priority, Horizon, Iteration, Literature, Preference, product backlog, Release Planning, Scope, Sprint, sprint backlog, Stakeholders, Subset, Top Priority, velocity, Velocity Changes
A while ago I posted about why I feel you shouldn’t estimate bugs. In a nutshell, if you estimate bugs you’ve essentially ‘double-dipped’ the feature. There’s the estimate for the feature and the estimate(s) for the bug(s) introduced while the feature was being built. If you’re using Scrum defects go to the top, they don’t [...]
Uncategorized
estimating, velocity