I ran into a new branching strategy, branch by sprint, this week. I will have to admit it was a new one to me. I’ve seen branching by environment (dev, test, staging, prod), branching by developer, and branching by feature/user story. I had not considered branching for a sprint. […]
A quick video introduction to Kanban with Trello. Kanban questions? Contact me for Kanban help.
A Vision of a Better Grocery List Just to show how versatile Trello can be I want to share one of the personal projects I built with it this week: a family Grocery List. We’re a family of five. Grocery shopping for that many people is the urban equivalent of big game hunting. Minimizing trips Read more about Trello Cookbook Recipe: Family Grocery List[…]
One of the key underpinnings of Agile is the concept that the things that have the most value go first. In Business as Usual conditions this means items land in the backlog, receive grooming, get prioritized by the business, and wait their turn in the On Deck queue for the development team. Happy happy! But Read more about Bees and Ants in Agile? Swarming for Problem Solving[…]
Our teams break down sprint planning into two main meetings: the “What” meeting and the “How” meeting. The “What” meeting involves the product owners and stakeholders. The “How” meeting is for the Scrum Development Team. To run a successful “What” meeting requires some preparation and sticking to some guidelines during the meeting. Do that and Read more about Most sprint planning meetings are Crap! How do I make mine great? (Part One)[…]
Don’t limit your thinking when it comes to defining “what” a Scrum development team is. It is not just those writing code. It’s not just developers or programmers. The team is everyone that moves the ball forward. Developers, testers, business analysts, scrum masters and product owners all play a role in the successful completion of Read more about What is a Scrum Development Team?[…]
This is a video tutorial I did on setting up Trello for your team or business. I use Trello constantly and couldn’t do without it. I think you will find it just as useful.
Sprint – a short development circle time boxed to typically two week periods in which the development works to complete the user stories they committed to during Sprint Planning.
Sprint Backlog – the collection of user stories committed to by the development team during the “How” meeting of Sprint Planning.
User stories start their lives as an unruly mess. They often have just the briefest of descriptions, no direction and no vision for what they will be when they mature and reach the status of Done. The skilled product owner or agilist responsible for grooming these user stories takes this rough form and elaborates it Read more about How to Groom User Stories[…]