We’re interested in software planning processes at Bayside. Earlier this week we published the last in a series of posts covering some of the tools and practices we’ve found useful on software projects. All three posts are now up and available to read at your convenience.
Spec’ing the specs series
Hopefully these posts will make you think a little about your own team’s software development process. None of our suggestions are miracle fixes. And most can be tested out separately from the rest. So jump in and give one or two a try. See what works in your organization.
Speak up with your own suggestions and reactions in the comments.
In two other posts we’ve covered both how to craft and how to capture a plan when approaching a software project. In this third and final post of the series we’ll talk a bit about our approach to following that plan when it comes time to execute it.
Collaboration has emerged as the common theme for us in designing and developing software. For any plan to have a chance at successful execution, the people charged with building it, the people who will use it, and the people who have expert knowledge about the business behind it need to work together from start to finish.
Collaboration certainly shouldn’t stop once developers start writing code.
(more…)