Download PDFThe best way to guarantee success of any type of project is to have a strong experienced Project Manager and strong, experienced Business Analyst. These two individuals, working together from the beginning of the project, set the stage for success by accurately planning and clearly defining the expected outcomes. Both roles are necessary because they are each responsible for a different set of tasks and they each possess a set of skills that complement each other. The two roles are closely tied, but exactly what are the similarities and differences, and why does a project need both?
This course discusses the role of Business Analysts and the business analysis skills that a Project Manager should also possess. The business analysis skill set includes critical thinking skills, elicitation techniques and requirements analysis and management. Experienced project managers may already possess some of these skills, but may apply them differently than BAs. Understanding the complexity of the business analysis role will allow the PM and BA to work seamlessly and increase the project efficiency.
Scoping is one of the most critical areas on which the PM and BA should work together. In addition to the project scope, as defined in the PMBOK™, the BA is responsible for defining the scope of business analysis. When these two components of scope are combined they define the entire boundary of the project. In this course, Project Managers will learn how Business Analysts define the scope of the area for which they will be performing analysis. This is just one example of a task with separate roles for the PM and BA. Understanding their unique roles is critical to project success.
- Scope and analyze the area of analysis to clarify the complexity of the business analysis effort
- Define an excellent requirement and the difference between business and functional requirements
- Learn the four core components necessary to analyze a business area
- Be introduced to the most commonly used analysis techniques
- Discuss alternatives for traceability of requirements
- Plan an approach for analyzing, categorizing, and managing requirements
- Determine the level of formality required and consider options for documenting and packaging requirements based on project type, priorities, and risks
- Identify techniques and documentation options appropriate for the various software development approaches and project types (COTS, maintenance, business process improvement, new development, etc.)
- Understand how validating requirements impacts the project and the components of software testing
- Review business analysis requirements to improve the quality of your deliverables