Workable templates straight from the Business Analysis trenches.

See detailed document descriptions at

Business Case

  • Business Case Document - Build your business case to justify the project to your company. The business case will give your department/division the authorization to spend the time, money, and resources to execute the project. Its unlikely that a project will move forward without a strong business case. BUSINSS CASE TEMPLATE

  • Stakeholder Analysis - Clearly define the roles and responsibilities of everyone involved in the project. This ensures that the perspectives of all relevant parties are taken into account and that your project has the buy in that it needs to succeed. STAKEHOLDER ANALYSIS TEMPLATE

  • High Level Project Plan - A ballpark schedule estimate is needed for the business case. The high level schedule lays out the major project phases and the main activities for each phase to arrive at the estimated number of weeks that the project is expected to take. This schedule is normally the responsibility of the project manager, but the BA is sometimes expected to produce it. HIGH LEVEL PROJECT PLAN TEMPLATE

  • Cost Build up Sheet - A ballpark cost estimate is also needed for the business case. The list of items in this template should be taken into account when coming up with the cost estimate for the project. COST BUILD UP TEMPLATE

Select and Purchase Software

  • Market Survey - Figure out what software exists in the market, and compare them to one another to make a short list of qualified vendors/products for your project. [COMING SOON]

  • Request for Quotations (RFQ) - Now that you have your short list, get the best value by getting the vendors to compete for your business by placing bids on your project. The RFQ tells the vendors what your looking for. They will respond to your RFQ with a proposal/bid. [COMING SOON]

  • Vendor Product Evaluation Criteria Matrix - Once you've collected all the proposals/bids, compare the bids to one another to select the software/vendor for the project. [COMING SOON]

  • Reference Check - Before selecting the vendor, do a reference check to make sure your vendors have had past success. TEMPLATE

Requirements / Design

  • Detailed Requirements Document - Elicit, document, and analyse the detailed user requirements for the system. The functional requirements will come in the form of use cases. Detail out each of the use cases in the system to describe how the system will behave when interacting with the user. This document will become the project's "contract" with the customer specifying the details of what the project will deliver. DETAILED REQUIREMENTS DOCUMENT TEMPLATE

  • Business Process Flows - Document the business processes that the system will support. Use the process flow diagrams to discover the use cases that will be required for the system. The process flows will go into the requirements document. PROCESS DIAGRAM TEMPLATE

Testing / Rework

  • Test Plan - There are many questions that have to be answered when planning out the functional testing in a system. How will testing be divided up amongst the testers, how do you ensure that executing test cases do not interfere with one another etc. Use the test plan to make sure you have all your testing bases covered. [COMING SOON]

  • Test Cases - Expand your use cases into test cases by writing one or more test cases for each use cases. There is no predefined formula for how to go from your use cases to test cases. A good rule of thumb is to ensure that all the variations for each use case are covered by at least one test case. [COMING SOON]

  • Defect Register - If you dont have access to a defect register/bug tracking system, then this spreadsheet is a great tool to track the defects you find during testing. DEFECT REGISTER TEMPLATE

  • UAT Acceptance Form - Get formal agreement from your customer that the system can be implemented/rolled out. [COMING SOON]

Change Control

  • Actions / Issues Register - Outstanding issues and actions can be easily forgotten and lost when your in a busy project. Make sure you track and manage these items using the actions/issues register. Review this register with your stakeholders regularly so everyone knows what is expected of them. ACTION / ISSUES REGISTER TEMPLATE

  • Change Request Form - Any changes to the agreed upon scope or requirements should be taken through the change request process to prevent any cost/schedule overruns for the project. Use the change request form to absorb scope/requirements changes into the project. [COMING SOON]


  • Communication Plan - Let your stakeholders know how you plan on communicating with them throughout the system delivery life cycle and what is expected of them in items of communication. COMMUNICATION PLAN TEMPLATE

  • Sample Email Messages and Meeting Requests - It's sometimes hard to find the right words to send in some situations. The following email message templates will help you to communicate professionally and ensure nothing is left out. [COMING SOON]

| All site content is © |