Mail The Captain:
Subscribe
Tags
5s 2009 2011 backlog bug change management Chris Matts coaching collaborate conference culture defect design ego elephant empowerment enterprise goal information radiator Kanban leadership lean manifesto music oubliette pairing pattern peer review performance pirate priority question scrum simple tdd team technical debt test Theory Of Constraints thinking TOC user value waste WIP-
Recent Posts
- Portrait Vs Landscape
- You Are Not A Lathe Operator
- Story Points are Only for the Team
- The Flat-Pack User Experience
- The Hidden Dangers of an Independent Quality Organization
- Rapunzel’s Ivory Tower
- Post #Agile2011 Playlist
- Where’s My Tools?
- Piratical Management (Pirarticles)
- Transactions for Managing Technical Debt
- The Point of Maximum Learning
- Improving Your Retrospectives
- 5S Your Scrum Board – (Part 2) – In depth
- 5S Your Scrum Board – (Part 1) – A Place for Everything
- Dietary Manipulation (Part 3) – Coffee
- Have We Started Yet?
- Arrrr – Thar Be Treasure in Cambridge!
- Swimlane Sizing – Complete & Fast Backlog Estimation
- Acting on Difficult Advice
- Dietary Manipulation (Part 2) – Carbo-Caution
- Black Holes & Revelations
- Yellow is the new Green
- Intellectual Humility
- The Joy of Peer Reviews (Part 2 – Documentation)
- Agile Is Just A Means To An End
- Express Your Real Motivations
- Escaping the Oubliette (Part 4) – The Litter Patrol
- Distributed Management and Work-Life Integration
- Escaping the Oubliette (Part 3) – Bug Blitz
- SMART Goals and The Elephant Test
- Priority Fatigue
- Building a Case for Change
- Patterns For Collective Code Ownership
- Escaping the Oubliette (Part 2) – Tailing
- Escaping the Oubliette (Part 1a) – Debt Prevention
- Your Baby Might Be Ugly
- Escaping the Oubliette (Part 1) – Topping
- The Joy of Peer Reviews (Part 1 – Code)
- Your Leaders Are Not Gods
- The Oubliette
- Stop Working With Blunt Tools
- Dietary Manipulation – Pizza
- Are You Empowered?
- Freedom To Vent
- Lessons in Application Performance (Part 2)
- Lessons in Application Performance (Part 1)
- Your Leader Sets The Tone For Your Team
- The World Needs Ditch Diggers Too
- Nobody Thanks the Drummer
- Soylent Green Is People
- Why The Manifesto For Half-Arsed Agile Software Development Is Actually Important But Not Enough
- Readiness to Serve
- Blame
- Software Is Just A Means To An End
- Writing Code is NOT a Value-Add Activity
- Cultural Balance
- Stop The Bleeding
- The Egoless Daily Stand-Up
- Learning to Say “No”
- Captain, You’re Wrong!
- Breaking The Seal (Part 2)
- Red Cards
- Agile 20xx – It Takes a Team
- Breaking The Seal (Part 1)
- Communicating in Patterns
- 10 Minute Test Plans
- What’s on Your Radar?
- Just Enough Design
- I’m Drowning in Confetti
- Don’t Open More Barrels Than You Can Consume
- A Decade of What?
- Creative Freedom & Product Ownership
- Ahoy!
Blogroll
- Adrian Wible
- Arlo Belshee
- Bas Vodde
- Carl Bruiners
- Chris Matts
- Clarke Ching
- Clicktricity
- Cory Foy
- Dan North
- Dean Leffingwell
- Edge of Chaos
- Eric Willeke
- HBR
- Henrik Kniberg
- Innovation Games
- Israel Gatt
- James Lewis
- James Shore
- Joel on Software
- Juergen Appelo
- Liz Keogh
- Luke Morgan
- Mark Dalgarno
- Mark Levison
- Martin Fowler
- Mike Cohn
- Mike Pearce
- Naresh Jain
- Pat Kua
- Rajeev Singh
- Rich Mironov
- Richard Durnall
- Rob Brown
- Simon Prior
- The Rally Team
- XP 123
- Your Brain At Work
Tag Archives: tdd
Where’s My Tools?
Most of the really big successes and game-changers I’ve seen in my career have been initiated through individuals seeing a problem and fixing it themselves rather than waiting for others. If you need something done that isn’t already happening, nobody … Continue reading
Posted in People, Project Management, Simple Tools, Technical
Tagged empowerment, tdd, test, tool
Leave a comment
Patterns For Collective Code Ownership
Following the somewhat schizophrenic challenges of dealing with person issues on collective code ownership, here we focus on the practices and practical aspects. How do we technically achieve collective ownership within teams? We’re using the “simple pattern” approach again. For each … Continue reading
Posted in People, Simple Patterns, Technical
Tagged bug, collaborate, collective ownership, defect, ego, feature, pairing, pattern, peer review, tdd, technical debt, test, training
Leave a comment
Escaping the Oubliette (Part 1a) – Debt Prevention
This is a partial re-post of Escaping the Oubliette (Part 1). I’ve split the article into smaller readable components. Great, I’ve got my incoming defect strategy nailed, Now how do I prevent defects and debt in new code? In 5 … Continue reading
Posted in Planning & Estimation, Project Management, Simple Patterns, Simple Tools, Technical
Tagged acceptance criteria, build, craftsmanship, design, oubliette, pairing, peer review, simple, tdd, technical debt, test, thinking, WIP
Leave a comment
10 Minute Test Plans
Struggling to introduce TDD or Acceptance Testing? Here’s a really powerful simple first step that you can perform immediately - How to get your development teams ”thinking” about tests and how to test with little or no negative impact and a few … Continue reading
Posted in Simple Tools, Technical
Tagged acceptance, atdd, pairing, plan, quality, quick, simple, tdd, test
Leave a comment