Anuradha SatthiyamoorthiProject Manager Technical| Tata Consultancy ServicesProspect Heights, Il, United States
Can anyone please share a template in Excel for capturing requirements and acceptance criteria? Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Anuradha - Along with a web search, there are several templates available in the 'Templates' section. Have you searched, but not quite found what you're looking for? What was missing? May provide a nice opportunity to formulate your own template. Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
Refer to this website!!!! Saving Changes...
Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Hi,
Well honestly, I prefer to build my owns artifacts, just in that way they can meet my expectations. Anyway, I guess in the "templates" section, here at projectmanagement.com Saving Changes...
I prefer to build my own artifacts too. I build that with the helping of guide like PMBok and using the results of analyse my company/project needs with the team members. Saving Changes...
Just out of interest, why do you want to use Excel as opposed to any of the low cost free requirements tracking solutions available such as JIRA?
Since you are using the term "acceptance criteria", I'd assume you are using user stories as a means of discussing requirements with your customers, so it is usually advisable to move from an approach where all requirements are in one document and can only be worked on by one person at a time to an information repository which supports updates by the entire team.
I think the templates can be a good start to get your ideas flowing, but they often have to be tailored according to your specific situation in order to get what you need. I looked briefly through the templates here and didn't see anything that had a good connection between the requirements and the acceptance criteria from my cursory review. They stop at verification methods.
Relation to acceptance criteria can be tricky as in some cases, a customer or peer review can be the means of verification making them very subjective, while for others like a test program, the acceptance criteria are often very objective.
Broad or not easily quantifiable requirements can be quite challenging to formally define acceptance criteria. For vague regulatory requirements like 'Don't do anything unsafe', there may be other documentation which you point to for how that is reviewed and accomplished. You would refer to those documents in your requirements traceability matrix. For instances like test acceptance criteria, I recommend having a high level test summary that outlines both the procedure and the specific pass/fail criteria. Those are maintained separately, and pointed to in your matrix.
The actual problem you are describing is a significant focus of Systems Engineering and the difficulties of managing it are a big part of the new information age field of Model Based Systems Engineering or MBSE. That moves from a document based system with federated requirements to digitally linked information.
. Saving Changes...
Yes Jira can help, but we can't undervalue of the good Excel spreadsheet. Saving Changes...
Todd OsbornDirector of Security Operations and Emergency Management | Jackson National LifeWilliamston, Mi, United States
Many templates are available. I do recommend that before any significant work be completed that a clear definition of the need and/or problem(s) to be solved has been completed. Additionally success criteria and metrics identified. Saving Changes...
