The retro is seems like the first meeting to get cut from the normal sprint cadence. But don't give it up! Everybody benefits, whether they know it or not.
Each Atomic team role has different responsibilities, but every person engages in every part of the project. That’s why we can all see the big picture.
Every consultant must learn to say no — to special cases, cool new ideas, extra responsibilities, etc. It's your duty to protect your project. And yourself.
If your recent project taught you a lot, consider giving a company-wide project retrospective. Here are a few things to consider as you plan and present your findings.
Learning during projects is usually incidental, a happy accident—but that's a huge wasted opportunity. By being intentional, you'll be surprised what you can learn every day.
Before you simply drop the client right into the mix, invest some time in the relationship between your new client and their team. Think about what they need to know. Listen to the
Scope projections should be developed early and updated often, until the team has a fully-defined and estimated backlog. Here's a simple method for scope projection I've used to ma
Working remotely for long periods might not be ideal for software development and consulting wok. This likely depends on the work being done, but a week or two is probably safe.
So, your product development engagement with Atomic Object is nearing an end. You now have three distinct options for how could continue working with us.
