Hello there, i am back and so today it is about the folks who actually get their hands dirty and bring a business vision to life,
So on this side we have the players categorized as follows:
1. The team that actually builds or develops the product based on the business vision you share with them
2. The team that will eventually hold the product and provide support to the end users on a daily operational basis
3. The team that validates if the developed product is as per user specifications
4. The teams that validate if the product being developed is as per best practices and the standards being followed in your organisation
5. External Suppliers of software or services
and this translates to,
1. The Project Manager
2. The Operational Support Team
3. Quality Team
4. Implementation SMEs
We have the Project Manager and his development/build/implementation team, as is obvious these folks develop the solution, the PM creates the Project plan, Work Breakdown Structures and the Activity checklists. The go-around document for this team would be the Low Level Design document or Technical Specifications document which is a byproduct of the Functional Specifications document that you share with the PM, User Training Sessions and Manuals are brought out by this team(the functional memebers of the team usually do this) and this team also transitions the functioning of the nuts and bolts of the product to the Operational Support Team, the support team takes over the maintainance once the product has stabilized and undertakes fixes and enhancements through Change Requests.
In between the product being developed and pushed into production, it is put under the scanner and ripped apart to check for flaws, disasters and catastrophes, i know you love this phase, yes the product is tested and depending on the functionality and other parameters like the probable number of users, internet facing or not etc, the product is subject to functional, load and other applicable types of testing, If the product under consideration involves a couple or more applications publishing data among themselves, a thorough System Integration Testing is carried out. Depending on how your organisation works, either the BA or the Quality guys write the Test Cases. Quality teams use the Functional Specification document and the Technical Specification document (in most cases) and maintain Defect Registers & Trackers.
Depending on how your organisation works, the Solution Architects, the DBAs, Usability Analysts, Change Consultants, Information Security experts et al are brought in either before the implementation starts or after the initiation and before the development commences. These guys use either the detailed Requirements Document or a Solution Approach document.
This outlines what goes on and around in a typical software development cycle, when a methodology like AGILE is followed and adhered to, the players , the process and the artifacts change, and more about that later……
So until next post, take care………