COEPD – Center of Excellence for Professional Development Happy Learning
- Can you explain SRS and its Key Elements?
– SRS Means Software Requirements Specifications. Which includes Functional Requirement and technical requirement.
This is very simple and most important process in requirement specifications. It will help to provide basic cost of product and what will be the risk for product in future. It will help to endues or new user to operate things in proper way with guidance. This requirement specification forms basis of an organizations entre project. It will create set of all frame work which need to follow by all development team. It will provide critical information to all team members all things such as- development, operation, quality assurance and maintenance. Need to ensure the teams are in agreement. We can say that there are three types of requirements – 1. Functional Requirement. 2. Non- Functional Requirement 3. domain requirements
The key Elements of SRS are:
1. Keep it organized – start with a template
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
2. As per user point of view-
It will help to know how an organizational system can be used as user points from different stakeholders. The document should have a conceptual grasp of the system. It will also help illustrate high-level threats to a proposed system or situation. This helps and identifies the vague capabilities of a project before it even begins and gives a more clear and specific technical basis that will make it more successful.
3. Write implementation-
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
4. Analyze, Refine, Decompose Requirements
Here we need to analyze after analyzing need to rework if required and after that we need to decompose requirement with all proper manner to meet all requirements from end user view.
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
5. Need to Make requirements testable at high level
This is a very common and standard and even then organizations fail to meet the criteria. High-level requirements often not meet inspection or user testing, Here we need to check requirement with high to low level.
6. Evaluate documentation with stakeholders from start to end
After all process has been documented we need to evaluate the final documentation in proper manner before development begins. After all we need ensure that satisfaction is reached across the teams and increase the probability that the requirements will meet their needs.
This is very simple that we have to define the future of the company and products. Before starting any document we need to start with simple template. To be perfect in all the document. All the documents should be cut short and properly organized to be more efficient.
7. Manage requirements changes
Need to manage all requirement changes in proper manner with all excepting changes. the situations and project requirements are always developing or ever-changing. Requirements can change for plenty of reasons. Its quite lengthy process to do changed in all documents as per requirement.
- What is RACI Matrix in Project Management?
Ans – RACI means responsible, accountable, consulted and informed. This RACI chart is a matrix of all the activities and decision making authorities undertaken by an organization set against all the people and their roles. We use this to clarify all employee roles and responsibilities for each single task, with milestone and all decision that takes place throughout a project. We design this to ensure clear communication and smooth workflows across all parts of a team with all team members. A RACI chart is a way to identify your project teams’ roles and responsibilities for any task or single task, milestone, or project deliverable.
1. Responsible- who is Doing The Task with proper management
This means the person who is directly responsible for each and every task in this RACI matrix. He is in charge of taking the all kind of initiative and need to make sure that all tasks are completed. In each task we need at least one member who produces marketing materials and technical documentation.
2. Accountable- who is Owning the Task with all responsibilities
This person gives their approval to the finished product. In this we can say the person with all final authority over all the successful completion of specific task or any particular project. Each task need to be must have single accountable party who will not always PM. Here if someone not doing their task with all proper manner this accountable person can monitoring the overall tasks completion
3. Consulted-Assisting with Information & Knowledge to all team members
Here we can say that someone who with unique insights the team will consult. This means the person who is directly responsible for each and every task in this RACI matrix. He is in charge of taking the all kind of initiative and need to make sure that all tasks are completed. In each task we need at least one member who produces marketing materials and technical documentation.
4. Informed- need to Keep Awareness of all things
They most likely don’t participate in any other part of the deliverable. Here we can say we need to keep information for all things. In this people are not required to be consulted and included in the decision making process. This is the individual or group of people that is informed or included in of informed of the status and completion of the work.
RACI Matrix Rules-
- It will help to avoid multiple levels of oversight and one level is enough.
- Always help to do teamwork within deadline.
- Make changes as needed in all kind of document and let people know when things change.
- It will help to assign only one Accountable per task as per information.
- Ensure Accountable assignees have authority to ensure the task is complete.
- One task for one person.
- User friendly.
- Easy to work and understand.
Below are Benefits of the RACI model
- It will help to Clarifies all kinds of roles and also helps to eliminates all confusion regarding work.
- RACI model helps to Keeps projects on track and ensures nothing falls through the cracks all things should on track.
- It helps to Ensures smooth transitions and handoffs when there is turnover need to explain.
- This model will help to Prioritizes communication between teams and stakeholders.
- User friendly.
- Easy to work and understand
