Do you have an upcoming development project that will require detailed specifications? Take advantage of two decades of experience in documenting software requirements at both enterprise and small-business levels.
When you're going to invest significant time, resources, and money into an application development project, framing the business objectives and functional requirements for the desired solution establishes expectations for all stakeholders. Together we'll describe the problem (or opportunity) and how the end result should address it.
SMBworks takes the approach of starting with high-level objectives: what internal and/or external needs are to be met. It may include a glossary of terms so all participants in the project share a common vocabulary. The requirements document then gets more specific about features and functionality that meet those needs listed earlier. It could include screen mock-ups and other helpful resources in an appendix. The goal of the document is to describe the scope and specifics of the project to both the client who pays for the development and the development team executing the plan.
Typically, the documentation will be the product of a series of elicitation sessions. Any or all of these sessions may be conducted on conference calls or video conference, to save on travel. At each phase, we will manage change requests and other artifacts as the collective works that drive development.
Prefer a more agile development process? We can get started with a project framework and a dynamic new-next-now prioritized listing of tasks to get from start to finish—and then repeat the process for subsequent updates. We'll cover the tools (Jira, Trello, or otherwise) in discussing methodology.
Whether the scale of the project yields 10 pages or 100+ pages of technical specifications, the document describes what business purpose the product is meant to serve, and what it should do, for whom. Early in our discussion, we will determine together what specific content helps drive development.
SMBworks owner Mark Bernhardt has worked with clients and their internal or contracted development teams, documenting the project requirements, and then either staying on as a project manager or stepping back until the next major development. If you're looking for an experienced liaison between business and technical teams, you've found him.