Agile adoption failure stories are abundant, especially in large organizations. There are many vague reasons and lame excuses for this: "Our culture doesn’t support change initiatives." "Our leadership won’t adopt an agile mindset.” "Our change order process can’t integrate with an agile process." And so on. Here are some concrete things you can do or […]
Every Agile project needs user stories. But where do stories come from? I’m not asking who types the description into your backlog, I’m really asking how a team works together to create the definition of features that developers should complete.
Estimating work is helpful for managing teams and planning for the future. But working through every nuance to provide an estimate can cause frustration and be time-consuming.
Documentation means a lot of different things to different people. I’ve also found it’s one of the top five topics to cause a developer to cringe. If you’ve used a waterfall software development process, you’re all too familiar with documentation. From requirements to systems architecture to design, you’re creating documentation at every step of the […]
Finding and maintaining balance is a major theme of life—between work and leisure, time alone and time with others, eating healthy food and enjoying a treat. Software projects also involve a lot of balancing. One big facet (highlighted by conversations around Agile vs. Waterfall) is the balance between spending time to build precise plans in […]
There’s a saying that what’s done is done. Done is straightforward, clear-cut. It’s absolute. So when we talk about user stories being done, why is it so difficult to agree what that means?
The demo is one of the most important aspects of the sprint ceremony. At this point, your client has already seen the visual design of new features, but this is their first chance to see features in action. I’ve been a part of some very successful feature demos, and some that haven’t gone so well. […]
Monitoring accounts receivable (AR) is something that all companies do. Generally, this is a function of the accounting department. The challenge is: Who is responsible for following up when AR is past due?
So you have your product backlog chock-full of sprintable items. User stories, dev chores, a few bugs—all estimated, of course, right?!? Your team is ready to rock, so where do we start? We start with my favorite scrum thing: the Sprint Planning Meeting.
We’ve all been there—that moment when you realize you’ve bitten off a little more work than you can handle. Interestingly, the more you increase your skill level, the more often you find yourself in this situation. It stands to reason; people like to assign work to competent and talented people.