Many organizations, including Project Management Institute (PMI), have performed studies to identify main reasons behind challenges and failures in projects. Although very often low quality of requirements as well as stakeholder management were among the top causes, the main reason behind all of them is ineffective communication.
Business analysis is a critical component for successfully implementing organizational change. When business analysis is properly planned for and incorporated into the work performed to support portfolio, program, and project management, research shows that success rates soar. Yet many organizations underutilize their business analysis resources leaving those performing the work a bit frustrated and desiring to demonstrate their value further.
PMI’s September 2017 Pulse of the Profession Report® ‘Achieving Greater Agility’ states that organizations who demonstrate high agility are those who utilize a variety of project delivery approaches and develop agile skills. In this presentation you will learn how to adapt your analysis skills to support the changing needs of project teams and organizations.
Why has project failure become the industry standard? How can projects deliver business value? What stands in the way of meeting stakeholder needs?
As published in PMI’s Pulse of the Profession Reports, poor requirements is consistently one of the top reasons why projects fail. Whether it be missing requirements or incorrect requirements, some of the blame can be attributed to poor elicitation practices.
In exploring the lifecycle of product development, we generally begin with business requirements that then further evolve into stakeholder requirements, solution requirements, and finally, our final deliverables. Along the way, in between many of the work products, test plans are created. This can be a complicated process with many different elements.
Needs are arguably the most important input to any business analysis effort. It is the “anchor’ domain in PMI’s The Guide to Business Analysis (Includes the Standard for Business Analysis), providing inputs to every other domain.
Solution evaluation is the often‐forgotten task. If you look at any diagram showing relationships of business analysis Solution Evaluation is always at the end. There are typically arrows showing the connection to the needs of a project or product. Still, poor solution evaluation always finds itself at the end.
There are many myths surrounding the discipline of business analysis: the myth of gathering requirements, the myth of the user, the myth that the business knows what it wants and so forth. What distinguishes the successful business analyst from others is the successful business analyst recognizes the myths and does not succumb to them. This presentation addresses these and other myths and how to overcome the mindset of business analyst myths.
Defining and elaborating requirements is especially important when you think about your projects, your IT strategy, or your business strategy. It is all about product requirements because you have to propose the solution which will satisfy all consumers. But how could you know what kind of characteristics the product must have? This presentation will propose the approaches and practices of creating a successful project perfectly from the start as you define and elaborate requirements.
|
"I'd rather be a failure at something I love than a success at something I hate." - George Burns |
