See enhanced version of this (https://www.slideshare.net/ujjwaltrivedi/prd-template-for-product-managers). A sample product requirement document draft for mobile apps. It can also be used for quick wireframing and estimates of any kind of software. It should generally be a useful tool for business analysts, product managers, pre sales consultants. It is modern, complete and agile.
<Company Name/Logo> Internal Use Only1. ObjectiveThis document provides understanding of the client’s requirements for the creation of new smartphone app for whatsoever purpose. It also categorizes the scope into smaller feature modules forease of visualization, estimation and creating wireframes.2. Client RequirementsThis is a list of requirements shared by the client on email/call and brief commentary after highlevel analysis of the same.Client Specifications CommentsSecure Login Token based/https/Captcha/Social etc. 2
<Company Name/Logo> Internal Use Only3. AnalysisWhich applications were analyzed? What features should be added, modified, removedfor better usability/performance/security/acceptance.4. Target UsersClass of users, Work profile of users, Age groups, Gender bias (if any) 3
<Company Name/Logo> Internal Use Only5. Non Functional Requirements5.1 Security Encryption required?5.2 Performance Standard/Real time5.3 Scalability Expansion plans and Scalability requirement – Low/Medium/High5.4 Internationalization Languages? Locale?5.5 Orientation Landscape/Portrait/Both 4
<Company Name/Logo> Internal Use Only6. Functional Requirements6.1 Application briefAdd highlights of application from engineering/marketing perspective.6.2 Application flow (Wireframes and Use Cases)- 6.2.1 Iconasdf- 6.2.2 Splash Screenasdf- 6.2.3 Home screenasdf- 6.2.4 Screen1asdf- 6.2.5 Screen2asdf- 6.2.6 Screen3asdf- 6.2.7 Settings screenasdf- 6.2.8 About ScreenAsdf o About text asdf o Emailing text asdf 5
<Company Name/Logo> Internal Use Only9. Reference ScreenshotsFollowing screenshots are attached, illustrating the functional modules listed above, for referenceonly. They do NOT indicate exact UI or functionality of mobile app. Login Screen 6
<Company Name/Logo> Internal Use Only10. Project EstimatesThe effort estimates as per the given scope in attached document is discussed inthis section. These estimates are also based on assumptions stated in thedocument.Following is the module wise categorization of features for pure developmentestimates on all mobile platforms. These efforts include only coding and do notinclude efforts for designing, managing, testing the app: Development Estimates (in Person Days)Features Platforms iOS Android Windows Blackberry Symbian J2ME Phone 7RegistrationUser profileLoginVerify availability ofDelivery to user’slocationOrdering andpaymentUIMenu and PricingOrder TrackingStore locatorOffersComplaints andFeedbackTotalFurther adding overheads to the development estimates: 7
<Company Name/Logo> Internal Use OnlyBusiness Analysis – requirement gathering and documentation a%Design/UI creation – Creating design assets b%QA – Testing for functionality, usability, performance c%Project Management – managing the team and taking care ofInformation Security, Business Continuity Plan, Traceability matrix, d%Project Plan, Release Management etc.Total e%Business analysis will be partly common for all platforms X% of maximum effort:NN Person daysBased on the aforementioned overheads the total effort estimates per platformwill be as follows Complete Effort Estimates (in Person Days) Windows Platforms iOS Android Blackberry Symbian J2ME Phone 7 TotalFinal Effort estimates are NNN Person – Days.Final Cost is USD NNNNNN. 8