I’ve been thinking lately about how important it is for a company to have a well-defined process for the Software Development Life Cycle, or SDLC as we like to call it. I’m going to do a series a blogs to share our SLDC process.
Partnet’s SDLC employs industry-best practices in accordance with Agile principles and methods. Our approach ensures that the right product is delivered in the required time frame, while providing visibility into the solution’s development. As part of our Agile Development approach, we employ both Scrum and Kanban methodologies.
Partnet’s SLDC is a multistage process. The first step in the SDLC is to make sure that each development projects start with stable, well-defined requirements. Our Requirement Managers use industry-best requirement management practices as defined by the Business Analysis Body of Knowledge (BABOK).
The requirements manager coordinates and schedules requirements gathering activities with each stakeholder group. These activities may take the form of interviews, video teleconferences, requirement workshops, questionnaires, or other forms of outreach. In some cases, multiple rounds of requirements gathering activities may be required as the results are documented and consolidated.
This step ends with the preparation of a formal requirements package. The requirements package describes desired outcome(s), assumptions, and constraints associated to a given business requirement. A requirements package may be presented in any number of formats, including but not limited to:
- Functional specifications
- Screen mockups and page wire frames
- Flowcharts, sequence diagrams, data flow diagrams and other visual models
- Data dictionary
- Use cases and scenarios
- User Roles
- Goal or desired outcome
- Benefit to the customers and stakeholders
The Partnet team completes the Requirements Step by meeting with the customer and other stakeholders to conduct a formal System Requirements Review. This involves distribution of the requirements package(s) for stakeholder approval. Signatures are collected from stakeholders, the Customer, and Partnet representatives to formally approve the solution requirements.
Part 2 of this blog series will cover how to handle new and emerging requirements once the formal requirements package has been developed. I hope that you have enjoyed our Part 1 of our Blog Series, the Importance of a Defined Software Development Life Cycle. If you would like to see any more of our blogs, check them out at partnet.com.