This course refers to the Project Management Institute (PMI)®. PMI is a registered mark of the Project Management Institute, Inc.
- [voiceover] There's some good stuff out there if you're seeking guidance or want to reference a standard. The Institute of Electrical and Electronics Engineers, often simply called IEEE, has a standards organization subcomponent, that develops global standards in a broad range of industries. To create these standards, experts from all over the world collaborate in an open, balanced and fair manner to reach consensus for each standard. For instance, they have over 50 standards on software development.
Three of which are specific to requirements. Much of the guidance, advice and templates that can be found in these standards, can easily translate to any other industry, even if they were formulated for a software or system environment. They have standards that address everything from strategic business requirements, feasibility, user capabilities and system characteristics, to technical design requirements. Project Management Institute, also known as PMI, recently began offering a certification as a professional in business analysis.
You can find out more about their certification at pmi.org. Then there's International Institute of Business Analysis, also known as IIBA, and they've written a standard guiding the requirements process called, A guide to the Business Analysis Body of Knowledge, often called the BABOK. For this course, we will draw primarily on IIBA's, A guide to the Business Analysis Body of Knowledge. IIBA is an independent, nonprofit professional association serving the growing field of business analysis.
They were founded in 2003. They're headquartered in Toronto, Canada. They have members in over 100 countries and their guide provides generally accepted best practices in business analysis, or the building and managing of requirements. For more information, you can check out their website at iiba.org. The Business Analysis Body of Knowledge defines a business-analysis standard rather than a methodology. It describes knowledge areas, activities and skills in a reference format, stating no prescribed sequence or order of these activities.
And it applies to all project sizes, types and development methodologies. The Business Analysis Body of Knowledge shares information on six knowledge areas. First, business analysis planning and monitoring. This knowledge area helps you in determining activities needed to complete a business-analysis effort across the project life cycle and governing performance of all other business-analysis tasks. Typical activities include, identifying key stakeholders; selecting appropriate business-analysis techniques and defining the process for managing requirements.
Second, the elicitation knowledge area is about gathering and collecting requirements for the business from the stakeholders about the solution and the transition. Typical activities include, identifying stakeholder needs and concerns; describing the organizational environment; defining methods for gathering requirements and ensuring requirements are complete, clear, correct and consistent. Third, the enterprise analysis knowledge area is about capturing a view of the business, providing context and understanding of the organization.
Typical activities here include, identifying, refining and clarifying business needs; defining solution scope; performing problem definition and analysis; developing the business case and building feasibility studies. Fourth, the requirements analysis knowledge area is about progressively elaborating stakeholder and solution requirements. Typical activities here include, prioritizing solution requirements; analyzing, structuring and specifying stakeholder needs; defining solutions that meet stakeholder needs and verifying and validating the resulting requirements.
Fifth, the solution assessment and validation knowledge area is about ensuring the solution meets stakeholder objectives, is throughly tested and is implemented smoothly. This step typically occurs after the solution design is agreed upon. Typical activities here include, evaluating proposed solutions to determine the best fit; identifying gaps and shortcomings in proposed solutions; determining workarounds and changes to the solution and assessing project success after solution deployment.
And the sixth, the management and communication knowledge area is about ensuring stakeholders and the project team remain in agreement on the solution's scope. This occurs across the project life cycle. It builds maturity, repeatability and clarity into a project methodology to link your process to a well-respected and recognized standard. Typical activities here include, managing conflicts, issues and changes; deciding when and where requirements communication needs to occur and maintaining knowledge for future use.
Which standard does your organization lean on for developing your project requirements? IEEE, PMI or IIBA.
- Differentiate among enterprise, stakeholder, and requirement analyses.
- Summarize the elicitation process.
- Explain the importance of avoiding assumptions.
- Describe how to prioritize requirements.
- Identify techniques for conducting requirements analysis.
- Recall how to create a well-formed requirements checklist.
- Explain the guidelines for conducting technical reviews.