Understanding business needs is the first step to making the decision between build and buy. Before any organization can/or should make the decision to purchase, it must understand the business requirements at the smallest level.

Tool

Use this tool to estimate SharePoint development/customization TCO, whether you are outsourcing development, doing all the work in-house, or taking a hybrid approach.

Video

SharePoint is vastly underutilized due to the challenges associated with customized solutions, and SharePoint 2010 is no different. To get the expected return on your SharePoint 2010 investment, understand the planning, customization, expertise,...

Note

Info-Tech recently conducted several surveys for our research projects. This document is a high level summary of those results and an introduction to the resulting research.

Note

A strong communication capability between the business and IT ensures the alignment of business requirements with delivered IT functionality and value. Use this storyboard to understand common barriers to effective requirements management,...

Video

In requirements gathering, the role of the Business Analyst is critical in helping the business articulate their needs and wants, capturing the information and translating it into common language for both the business and IT. This video will...

Solution Set

IT needs to understand the needs and requirements of the business in order to deliver value.

Template/Policy

Requirements may change throughout the project lifecycle. Documenting and tracking these changes ensures accuracy when addressing the requests for change. Use this template to track the status of all requirements change requests.

Template/Policy

Requirements may change throughout the project life cycle. Documenting and tracking these changes ensures accuracy when addressing the requests for change. Ensure that the accurate assessment and impact of the change are documented whenever a...

Template/Policy

Gathering comprehensive requirements can mean the difference between a project's success and failure. There are a number of quality considerations that may need to be addressed within the scope of any project. To establish the quality of service...

Template/Policy

A Use Case Model describes the proposed functionality of a new system. A Use Case represents a discrete unit of interaction between a user (human or machine) and the system. This interaction is a single unit of meaningful work, such as Create...

Template/Policy

This document captures the business requirements of a proposed system or application. These requirements represent the problems that are to be solved by the proposed project.

Job Description

The Business Requirements Analyst's role is to elicit, analyze, specify, and validate the business needs of project stakeholders, be they customers or end-users. This includes interviewing stakeholders and gathering and compiling user...

When gathering requirements for software procurement decisions, enterprises need enough information to narrow the field of candidates. Too much detail, however, can rule out potentially viable candidates. Narrow the field without developing...

Requirements gathering is a critical part of custom software development and the procurement of commercial applications. Poor requirements gathering can lead to costly rework, expensive workarounds, and/or poor purchasing decisions. Learn the...

Requirements elicitation techniques are critical to the requirements gathering phase of software development and procurement. Choose the right elicitation techniques by understanding the strengths and weaknesses of each approach.

The identification of end-user and business needs is essential to choosing or developing the right software. However, stakeholders aren't always aware of their needs or able to communicate them effectively. Bring requirements to the surface with...

A thorough business requirements gathering process can spell the difference between project success and failure. Follow Info-Tech's nine steps to gathering good business requirements up front.

Template/Policy

A requirements document represents the problems that are to be solved by the proposed project. Capture the business requirements of a proposed system or application by using this document template.

Template/Policy

Gathering comprehensive requirements can mean the difference between a project's success and failure. For qualities of highly usable requirements and for further guidance on requirements gathering and documentation efforts, use this checklist

Tool

Documenting and storing all requirements in a single, centralized repository will help minimize confusion and complexity, especially for larger projects. To record and track requirements during the gathering stage, use this template.

Template/Policy

Apply this project plan template to help you draft the scope, purpose, individual responsibilities, deliverables, and timeline of a given project.

Template/Policy

IT projects often fail because the parties involved don't fully understand what work needs to be done, or how success will be measured. To mitigate this risk, use this Statement of Work template.

No clear definition of application provisioning exists, yet products promising to provide application provisioning are increasingly appearing on the market. IT managers must understand what application provisioning means to avoid buying...

In application procurement or development, requirements management encompasses all of the tasks that go into the feasibility, scoping, and definition of a new system. IT leaders must manage the politics of requirements during the procurement or...