*** IIBA Certification Exam Prep starts July 20th ***

The Business Analysis Doctor
  • Sign In
  • Create Account
  • Bookings
  • My Account
  • Signed in as:
  • filler@godaddy.com
  • Bookings
  • My Account
  • Sign Out
  • Home
  • Courses
  • Self-paced courses
  • Services
  • BA Techniques
  • BA Quotes
  • About the Doc
  • Find Jobs
  • Contact the Doc
  • Recommended Tools
  • DOC'S STORE
  • Coaching Inbox
  • More
    • Home
    • Courses
    • Self-paced courses
    • Services
    • BA Techniques
    • BA Quotes
    • About the Doc
    • Find Jobs
    • Contact the Doc
    • Recommended Tools
    • DOC'S STORE
    • Coaching Inbox
The Business Analysis Doctor
  • Sign In
  • Create Account
  • Bookings
  • My Account
  • Signed in as:
  • filler@godaddy.com
  • Bookings
  • My Account
  • Sign Out

Signed in as:

filler@godaddy.com

  • Home
  • Courses
  • Self-paced courses
  • Services
  • BA Techniques
  • BA Quotes
  • About the Doc
  • Find Jobs
  • Contact the Doc
  • Recommended Tools
  • DOC'S STORE
  • Coaching Inbox

Account

  • Bookings
  • My Account
  • Sign Out
  • Sign In
  • Create Account
  • Bookings
  • My Account

Business analysis quotes

Every project starts with the need, if the need is not clearly defined, it can lead to a lot of frustration and potentially a product that the customer is unhappy with.

  • Every project starts with the need, if the need is not clearly defined, it can lead to a lot of frustration and potentially a product that the customer is unhappy with.
  • A skilled BA possesses the ability to present requirements in different formats, to different audiences, while also creating a common understanding of the need amongst them all.
  • While the sponsor and project initiation documents are great starting points for identifying stakeholders, various other techniques such as document analysis, process mapping, business model canvas and observation can be utilized to ensure a complete list of stakeholders.
  • If a business analyst cannot transform complex information into requirements that are clearly understood by stakeholders with various levels of context on the situation, then the BA may need to analyze the information at a deeper level in order to achieve this.
  • Decision-making skills facilitate the ability for a business analyst to make recommendations to stakeholders with decision-making authority.
  • Regardless of doing Waterfall or Agile, we should always ensure that requirements are thoroughly vetted (confirmed, validated and verified) before designing a solution from them.
  • Business analysts can help define the solution design by ensuring that the proposed designs can be traced back to the approved requirements and will actually deliver value to the stakeholders.
  • There is nothing worse than spending your time building a product that no one uses. A cultural assessment will evaluate if the enterprise is willing and capable of adapting to the change.
  • The start for any project is to understand why it is needed. This is discovered by analyzing the current state.
  • A clearly defined solution scope facilitates the management of risk, prioritization, change requests and also keeps elicitation on the right track.
  • A testable requirement is broken down to the lowest level (atomic), is unambiguous and provides an outline for clear and observable test cases.
  • User stories for the system need to be further elaborated in the form of TASKS for the user story. User stories are for end user needs and benefits.
  • Paying close attention to key customer pain points via observation and focus groups can lead to revelations that can be GAME CHANGING!!!
  • Any significant change needs a measure of success in order keep everyone on track and to determine if the effort was successful upon completion.
  • Developing a solution without fully defining the business requirements (needs) can lead to products the customers don't want or use.
  • Some stakeholders can be so familiar with their day-to-day activities that it can be difficult for them to clearly explain their processes to others.
  • Considering who requirement recipients are and how they will use the information enables us to provide the appropriate amount of detail.
  • Understanding why a requirement exists is essential to ensure that the right product is delivered. A useful technique for this is JOB STORIES.
  • Many times BAs will need to execute multiple requirement techniques. Techniques for analysis are not always understandable to stakeholders.
  • Education is just the lessons learned from other peoples' mistakes. When combined with lessons learned from your own, you will become a professional.
  • As BAs, we assess the situation and ask the right questions to uncover the actual business needs. The 5 whys technique can help facilitate this.
  • The value of a good mentor can exceed that of a formal education and is realized much faster than experience gained through trial and error.

Copyright © 2018 Business Analysis Doctor  - All Rights Reserved.

  • Home