Dating senerios on video

Let us now get into a detailed analysis of how an SRS walkthrough happens, what is it that we need to identify from this step, what pre-steps we need to take before we begin, what are the challenges we could face etc. The next phase of the SDLC is “Design”- this is where the functional requirements are translated into the technical details.

The dev, design, environment and data teams are involved in this step.

Getting your team onboard on the day-to-day decisions is crucial for the smooth running of the project. However, software projects are not ‘one-man’ shows. Imagine a team of 4- if each one of them decides to review one module of the software requirements specification each. Templates don’t have to be complicated or inflexible.

Step #6: As a byproduct, a list of queries where some functionality is difficult to understand or if more information needs to be incorporated into functional requirements or if mistakes are made in SRS they are identified.

Team leads are generally responsible for providing all the items listed in the section above.

However, team members’ inputs are always important for the success of this entire endeavour. Wouldn’t it be better to assign a certain module to someone interested in it than to a team member who is not?

Wouldn’t it be nice to decide on the target date based on the team’s opinion than thrust a decision on them?

Leave a Reply