With this post I would like to turn to colleagues who are as well working with IT projects.
I am currently preparing for a new Project and as a leading PM a I have the right to describe project management methodology.
There are quite many templates for IT Story (Narrative), I would like to hear to your recommendation what you prefer the most.
As in the Project goal we copy&upgrade a system, however, with some some slight changes - I do not want to over administrate descriptions but on the other hand want to have all key information written & aligned Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Aside from the Project Charter, you could incorporate a Narrative which describes the Overview, Problem Statement, Solution Statement, Business Value, Business Justification, etc. Try to keep as a one-pager with a clean and concise story. The Narrative would then serve as the project's 'elevator pitch'.
Additionally, put some working agreements, established with the team, in place along with the communication plan. These are two important aspects to the project. Saving Changes...
Alexandre CostaScrum Master| Integer Consulting - Pictet technologiesLoures, Portugal
There are many templates for the effect you desire, and I am assuming with narrative that you want to build a kind of product backlog or storing mapping. No matter the case as Andrew refered in the point of view of the product owner the story should have a name , a brief description, a business value ( this is important for prioritization) , you should have a time field prioritization also , it would be nice also to have a field with the risk associated to the story, a field to indicate to which release it will belongs , should use MVP ( minimal viable product) to classify the stories to be planned in the first release, a field with notes. I think this is more than enough, the stories should be further detailed in the next steps like the release plan or iteration plan, including estimation, acceptance criteria, constrains etc. You can also order by feature prioritization and below the feature use some of the fields that indicated earlier and make a story mapping. Depends on what you think is better to the project and I am assuming that is an agile project. Saving Changes...
