A lot of people find release planning difficult and confusing in Agile. How can we plan out our releases when we don’t have fixed scope? When will we know something is ready for release? How do we use velocity in agile to help our planning? Are releases tied to iterations? I’m going to try and […]
Continue readingWhat is the difference between Agile and Lean? A lot of people are asking about the difference between Agile and Lean. Are they the same? Which came first? Which is better? Better for what? That depends a lot on your context. You also need to understand the background and purpose of each approach. This article […]
Continue readingRunning a restaurant business can be both exciting and challenging. The food market is highly competitive, so it’s crucial to employ effective methods of attracting and retaining clients. Whether you’re just starting out or have been running a restaurant for years, improving your marketing efforts will bring in more diners and raise your bottom line. […]
Continue readingScrum is a (pretty) good framework for managing requirements, how they move into and out of backlogs, and how we inspect and adapt the outcome of those requirements. But one of its weaknesses is it has basically nothing to say about engineering practices. (As opposed to say Extreme Programming). One of those engineering practices is […]
Continue readingI was reading a strange post on Linkedin Pulse about some wacky new system for story point estimation. The details of it aren’t interesting or important. What is interesting is the motivation behind it. The imaginary problem that many people think needs to be solved is that traditional managers, when moved (kicking and screaming) to […]
Continue readingCloud computing is an often misunderstood concept that fell victim to Gartner’s hype cycle in a pretty spectacular way. But it is a real thing and it is a game changer and it is here to stay. But there are plenty of blogs and books that can tell you that. What a lot of them […]
Continue readingWhy do people get split across agile teams? People sometimes get split across teams when working agile (or Waterfall, for that matter). You might hear things like “this team has two front-end developers, two back-end developers, a UX designer, a tech BA, and 50% of an architect”. Why 50%? There are usually two reasons: The […]
Continue readingI talked recently about technical debt and the importance of cleaning it up via regular refactoring. This article will explain the pricing of technical debt in an agile software context and why we should do it. Technical debt is crucial to manage or it can end up killing your products and demoralizing your teams. Most […]
Continue readingThere are many stories about Scrum-but, agile anti-patterns, and common agile misconceptions. If you’re wondering about the term, it comes from the idea “we’re doing Scrum, but we” [do something that is completely the opposite of what it says to do in Scrum]. Often this is because a firm doesn’t want to make changes when […]
Continue readingSo if you read my last post, you might be wondering, why not use velocity to compare teams? Some people do this, some people don’t. The agile software development community is pretty united in their recommendation here though. There are a number of problems with using velocity that way. So why not use velocity to […]
Continue reading