Who is supposed to write FSD (Functional Spec Document)
Discussion
Who is supposed to write FSD (Functional Spec Document)? Is this a BA's job or developer should be writing it?
In my organization, BA's are useless. They just put few lines of requirements in the TFS card and developers have to go back and forth millions of time before they have a full requirements.
Now the new manager is asking developers to provide FSD but on the other hand requirements are not complete.In my experience, its a BA's job to provide FSD.
What should be the write workflow here?
In my organization, BA's are useless. They just put few lines of requirements in the TFS card and developers have to go back and forth millions of time before they have a full requirements.
Now the new manager is asking developers to provide FSD but on the other hand requirements are not complete.In my experience, its a BA's job to provide FSD.
What should be the write workflow here?
Edited by sdyson31 on Sunday 10th November 13:50
Sounds like the perfect example of why it shouldn’t be an either / or thing, with the requirements being slung back and forth over the fence between the two “teams”.
Requirements definition, whether that’s starting with user stories, working in true BDD with acceptance criteria under a framework like Gherkin or more traditional approach, it’s a team effort and should involve a mix of BA, Lead Developer, Test Lead and Product Owner, facilitated by the Scrum Master. Daily stand up should identify areas where more clarity is required, with the relevant people swarming on the issue to create sufficient information for development to proceed.
Requirements definition, whether that’s starting with user stories, working in true BDD with acceptance criteria under a framework like Gherkin or more traditional approach, it’s a team effort and should involve a mix of BA, Lead Developer, Test Lead and Product Owner, facilitated by the Scrum Master. Daily stand up should identify areas where more clarity is required, with the relevant people swarming on the issue to create sufficient information for development to proceed.
The Devs give the content of the TSD and the BAs/PMs usually rewrite it as the Devs cant write for s
te, this contains all the non functional aspects of the system.
The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
te, this contains all the non functional aspects of the system.The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
Du1point8 said:
The Devs give the content of the TSD and the BAs/PMs usually rewrite it as the Devs cant write for ste, this contains all the non functional aspects of the system.
The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
Conversely, I’d say that it your PM thinks that the PM should be writing requirements then you are up the creek already. te, this contains all the non functional aspects of the system.The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
miniman said:
Du1point8 said:
The Devs give the content of the TSD and the BAs/PMs usually rewrite it as the Devs cant write for ste, this contains all the non functional aspects of the system.
The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
Conversely, I’d say that it your PM thinks that the PM should be writing requirements then you are up the creek already. te, this contains all the non functional aspects of the system.The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
Du1point8 said:
The Devs give the content of the TSD and the BAs/PMs usually rewrite it as the Devs cant write for ste, this contains all the non functional aspects of the system.
The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
Pretty much this...te, this contains all the non functional aspects of the system.The BAs/PMs usually write the FSD as its what the system is doing functionally and if your BA/PM dont know that you are up the creek already.
Gassing Station | Jobs & Employment Matters | Top of Page | What's New | My Stuff