Software is never done—there are always more features and functions you could add. So how much should you budget for a custom software project? Some companies keep throwing money at the project without any budget at all. But they can miss out on early client feedback and end up wasting money on the wrong things.
Have you ever wanted to play “what if” games with a project backlog? Or a budgeting spreadsheet? If so, the SUMIF spreadsheet function is a handy little tool you should try.
When you’re trying to get started on your first agile/scrum project, it’s easy to find arguments about why it’s a good approach. But it’s a lot harder to find clear, step-by-step explanations of the tools and processes you need to succeed. I’m trying to fill that gap by answering the question: How do you estimate […]
Estimating a custom software project is a difficult necessity that usually occurs before the project kickoff (what we like to call the “point of maximum ignorance”). And getting estimates right can have a significant impact on the overall success of a product.
When we’re running a client’s project using our Atomic Process, our team will assign an estimate of points to each item in the product backlog. In general, we classify backlog items into three buckets: Features (new or enhancements) Chores (dev work not resulting in tangible product changes) Bugs (fixing unexpected behavior or regressions)
We work with clients to define custom software proposals and create a responsible budget. In this task, we’re always going to be in a position where there are unknowns. For example, a project may need to integrate with a third party service we’ve never used before. We have to assume the service works as advertised. […]
Atomic Object builds custom software for our customers. Because of the complexity involved in building a great software product, software development projects are always more difficult to price than a product. As a result two different strategies for pricing services, such as building software, have traditionally been used by most companies. These are called “Fixed […]
I’ve been at Atomic Object for approximately 8 years, and during that time I’ve had the opportunity and the challenge of managing relatively large software projects. I’ve learned quite a bit from fellow Atoms and picked up a few tricks of my own throughout the years. One of the best practices I’ve picked up is […]
Estimating a new project is hard and time consuming. Why? Because when you start a new project, you are at the point of maximum ignorance. In most cases there is a solid idea, but the required functionality is ambiguous. The business is depending on you — the engineering team — to identify a high-level timeline. […]
When you are developing initial requirements for a new software product development project, you may find yourself questioning the appropriate level of detail to provide for specifications. You may feel compelled to provide a high degree of specificity so the development team can create an accurate estimate of cost and time to build the defined […]