Kanban is the New Scrum « The Hacker Chick Blog. Maybe it’s all the time I spend with startups, but while I strongly value Scrum’s ideas behind self-organizing teams & continual feedback – I can’t help but feel Kanban represents the next level of agility, giving us more flexibility and capitalizing on the lessons we’ve learned from Lean.
A lot of people tend to think Agile means Scrum – you know how it goes: And I think there’s a lot of goodness in Scrum. It provides clear structure for what the team needs to do (the Sprint Backlog), gives them focus for getting it done (backlogs are fixed for the duration of the sprint), and then enables the team to determine the best methods for getting that work done.
It even provides them a coach (ScrumMaster) who’s job it is to make sure they have what they need and to get impediments out of their way. ApiDoc - Inline Documentation for RESTful web APIs. Syntaxe Python.
The home of Scrum. Psychological Models in Scrum - ScrumPulse Webcast #6 Note: this episode of #ScrumPulse is moderated by Professional Scrum Trainer, Mark Noneman.
Learning, responsibility and power - the three psychological models very useful in a Scrum Master's daily work. Scrum Masters, while working with teams, battle multiple problems and dysfunctions. Having three lines of responsibility - towards the Development Team, the Product Owner and the Organization - they tackle different problems in those areas, but they often originate at one point.
While working with those three beings, it's crucial to understand how humans acquire skills and how to tell if what one's doing is helping them or yanking them back. But all needs to be based on the proper form of power, otherwise it might turn against you. Share this Article. Visual feedback for web design and development. QR Code Generator – create QR codes for free (Logo, T-Shirt, vCard, EPS)
Integrating OKRs with Trello. How do we organize Trello by Objectives?
For integrating the OKR workflow, we need an additional construct for organizing tasks by month and weekly timeframes; for each individual. Here’s how we arrange our Trello board: Stateful cards with labels — Instead of using lists as swimlanes for tracking progress - like “To-do”, “Doing” and “Done”, we use labels for tracking progress of each task (card). The advantage is that now we can use any number of labels, and come up with some creative names! We will think of each card as a Key Result for a stated objective, which can be assigned to relevant team members. 2. This gives us flexibility in terms of moving Key Results (cards) between weeks, we can measure the weekly task velocity. 3. Finally, we keep a meta list for tracking the Objectives. The card links the Objectives (Trello checklists) with the Key Results (Trello cards in the “Week #” lists).
This is how the entire board looks like: Trello Filters Tl;dr and DIY Trello Template. The World's Most Popular Framework for APIs. Ward Explains Debt Metaphor. Git Tutorials and Training. 5 Steps to Build a Killer Dashboard: the information you need, when you need it. Imagine walking into a status meeting knowing things are on track before anyone says a word.
Or coming back from vacation and seeing detailed project updates from a quick glance, before even checking email. This could be you! And what about when things (inevitably) go wrong? Know the moment a growing bug pile overtakes current velocity. Demonstrate which team members are critical to progress before they’re poached by another project. Let’s create a killer dashboard! Step 0: Create a new dashboard. Simple. Step 1: Add these five gadgets Start with the bare necessities: overall progress, work split by person or sub-section, and high-risk issues front and center. Filter ResultsCreated vs Resolved ChartIssue Statistics: add this one twiceRoad Map Once you’ve added all five, close the dialog.
Step 2: View progress at-a-glance Every morning you come in with a ‘feeling’ about how things are coming along. A Brief Introduction to Kanban. Kanban is another framework used to implement agile.
Back in the 1940s, Toyota optimized its engineering process by modeling it after how supermarkets stock shelves. Supermarkets stock just enough product to meet consumer demand, a practice that optimizes the flow between the supermarket and the consumer. Because inventory levels match with consumption patterns, the supermarket gains significant efficiency in inventory management and optimizing for the customer. When Toyota brought that idea to it's factory floors, teams (such as the team that attaches the doors to the car's frame) would deliver a card, or "kanban", to each other (say, to the team that assembles the doors) to signal that they have excess capacity and are ready to pull more materials. Although the signaling technology has evolved, this system is still at the core of "just in time" manufacturing today. Kanban does the same for software teams. Flexibility in planning. A Brief Introduction to Scrum: Scrum Process & Roles.
Scrum is one of the most popular frameworks for implementing agile.
So popular, in fact, that many people think scrum and agile are the same thing. (They're not.) Many frameworks can be used to implement agile, but scrum has a unique flavor. Agile Software Development.