On an agile development team, multiple people share the responsibility of ensuring that the user stories in the backlog are desirable, viable, and feasible. At Atomic, our delivery leads, tech leads, and designers work together to prepare stories for the development team to work on. While our delivery leads are responsible for defining the stories […]
On an agile software project, we readjust plans daily. We pivot to respond to change, discovery, and feedback. Product owners and stakeholders, on the other hand, focus on longer-term planning — defining product roadmaps, release dates, and milestones. As a Delivery Lead, I have the challenge of balancing planning needs for the entire team. Fortunately, […]
If you’re a member of an Agile software team, you know that the routines of Agile can sometimes feel tedious. And it’s hard to know what to change. Do you need to change your meeting frequency? Can some routines be eliminated? Should you scrap Agile altogether? Rather than abandoning Agile, consider incorporating some simple design […]
As a Delivery Lead at Atomic, I sit between the client and the product team and one of my responsibilities is to enhance the client’s experience. What does that really mean? It varies depending on the makeup of the client team and the objectives for their project. However, a common element of any client enhancement […]
A pet peeve of mine is when progress on a story is blocked with a reason like: “Need code sample to add live chat feature.” Or: “Don’t have VPN access.” What needs to happen next? Does someone know they need to help unblock this? I’m sure I’m not the only one who would be wondering […]
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 […]