Ever do the retrospective dance? You know the one, where at the end of the sprint everybody plays all the retrospective games: start-stop-continue, timeline, word-pong, or sprint-painting — and then nothing in your team actually changes? Maybe somebody takes notes, there’s an “action list”, you create new stories, or whatever, but the next sprint there you are with the same items all over again? That’s a fun game, right? [Learn more][1].
[1]: http://www.whattofix.com/blog/archives/2009/09/how-to-really-m-2.php
Uncategorized
Fun Game, Games, Painting, Php, Pong, Software Teams, Sprint
Time for another (almost) weekly installment of Interesting Post. Every week I feel like the number of agile related articles was pretty light… but then I go to build this post… and realize there was a ton of great content out there. I guess I ju…
Uncategorized
Amp, Architecture, Avalanche, Business Agility, Contracts, Document Templates, Dynamism, One Thing, Principle, Proceedings, Project Failure, Quote Of The Day, Related Articles, Retrospective, Scope, Scrum, Sprint, Stasis, Team Members, Time Budget
Okay… time to wrap this thing up. If you missed any of the first three ‘Noodling on Kanban’ posts… I included links at the bottom of this one… just to make it easy on you guys 
There is clearly much more to this topic than I wanted to try and …
Uncategorized
Aup, Boy Scout, Buffer Rope, Constraints, culture, David Anderson, Development Methodology, Drinks, Iterations, Kanban, Lunch, Mature Product, Noodling, Personal, Retrospect, Scotland, Scout Story, Scrum, Splitting Hairs, Sprint
For the final cross-cutting theme in “Rethinking the Agile Enterprise”… Dennis and I are going to talk about talking.In other words we are going to explore how organizations talk to each other when delivering work. We plan to integrate the idea that…
Uncategorized
Address, Adoption, Agile Enterprise, Backlog, Conversation, Conversations, Creative Solutions, Entire Team, product owner, Setting Goals, Sprint, Tradeoffs
The Scrum Team is responsible for the high-quality and timely delivery of sprint commitments in line with the expectations of the Product Manager and Product Owner. The Scrum Team is cross-functional and multi-skilled- they know their strengths and work together to support eachother through challenging times. They’re not all experts in every area, however between them they have a wide range of abilities and areas of expertise. [Learn more][1].
[1]: http://agile101.net/2009/08/12/agile-scrum-team-roles-responsibilities
Uncategorized
Agile Scrum, Amp, Challenging Times, Commitments, Eachother, High Quality, Sprint, Timely Delivery
Ideally bugs belong on the product backlog just like any feature request. But, that would often necessitate a significant change for the rest of the organization so two backlogs are used.
Uncategorized
Accommodation, Address, Adoption, Backlog, Backlogs, Boojum, Bug Database, Bugs, Cold Turkey, Concurrent Projects, Databases, Developers, Ideal, Marketing Database, Marketing Group, New Feature, Perspective, product backlog, Solution Teams, Sprint, Sprint Artifacts, Sprinting, Tech Support Group, User Stories
Today we are experimenting with 1 day sprints as an attempt to clear a large backlog of product work and client related work. During our last retrospective we noticed that there was at least one interruption each day during the sprint and while they were small, it’s still proving the point that when your [...]
Uncategorized
Attempt, Backlog, Bugs, Client Feedback, Client Requests, Coaching tips, Definitly, Email, Implementation Team, implementing scrum, Improvements, Interruption, Phone Call, Phrase, Product Developers, Resistance, Retrospective, Scrum, Scrum Tips, short sprints, Spirit, Sprint, Support Implementation, tactics
It’s been quite a while since I last blogged, my apologies to my faithful 10-person readership. Today was a particular hellish day after being off for only a few days. I came back to complete dis-array within the team and process and actually was quite surprised based on how well things were going and how [...]
Uncategorized
Admiral, Apologies, Array, Asteroids, Backlog, Coaching tips, Customer Support, Darth Vader, Dis Pleasure, Exercise, Few Days, Fires, Readership, Scrum Master Training, Scrum Tips, Sprint, Subordinate, Subordinates, Team Member, Team Members
A list of things (such as all other team members) that should be visible from within an ideal agile workspace.
Uncategorized
Acceptance Tests, agile books, Alistair Cockburn, Backlog, collocation, continuous integration, Current State, Customer Acceptance, Ears, Feedback Devices, Human Resources, Important Information, Lava Lamp, product backlog, product owner, Production Server, Programmable Devices, Rabbits, Ron Jeffries, Scrum Roles, Sprint, sprint backlog, sprint burndown chart, taskboard, Team Members, Traffic Lights, Visual Feedback, Visual Reminder, Workspace
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