Would you rather a family member married a traffic warden or a millionaire con artist? Would a Martian know a beautiful woman if it saw one?
The Guidebook Committee, often on their own personal time, developed the following wikibook over two years in an effort to provide a "how to" guide that could be used in combination with the IIBA's Business Analysis Body of Knowledge. As co-chair of the Guidebook Committee, I would like to thank all of the committee members for Pi and id flowchart and narrative knowledge, drafted sections, and passion in putting this terrific resource together.
This would not be possible without your commitment and experience. For a list of initial contributors, please go to the Noted Contributors later in this book.
As a PM Director, I find that projects with a dedicated BA are far more efficient and effective than those without one. This wikibook is dedicated to all the Business Analysts out there helping their business units meet their goals, day after day, project after project!!
They are responsible for ensuring that all Stakeholders share a common understanding of requirements and project or operational deliverables.
This is accomplished by: This includes tasks associated with participation and leadership throughout the Project or Application lifecycles. When we initially envisioned this Guidebook, we had grand plans of not only developing this book, but also developing training and a companion mentorship program to help grow Business Analysts in NYS Government.
Won't you join us on this journey? Helping us Edit The Book[ edit ] You will note there are a few section headings and notes within this wikibook that are blank or reference things to come.
We felt that to gain acceptance of this guide as a NYS standard--we would be better served having NYS help us put on the finishing touches together.
We would like this to be a collaborative effort that we can all use and follow. While we will happily accept any and all feedback and edits--we strongly encourage you to set up a wiki account and make your edits logged in.
This will be helpful to the Committee as we review and modify the book going forward. It will also prevent your IP address from being publicly exposed while you make edits. We look forward to your collaborative contributions to define a common approach for Business Analysis work in New York State!
What is a Business Analyst?
Some examples of different types include: Business Analysts have very strong business skills and understanding of the business domain. Their key role is to analyze business processes, procedures, architectures, etc. These analysts are more involved in what the IIBA defines as enterprise analysis and are likely to be involved prior to the initiation of an information technology IT project.
IT Analysts are focused on requirements elicitation and analysis, and solving problems using information technology solutions. This analyst serves as a bridge between business and IT and generally begins work after a project has been initiated.
Systems Analysts are an IT information information system analysts who are more focused on system design and the technical aspects of the solution.
The most important element is the business focus; ensuring business needs are understood and communicated so that problem solutions meet the business needs and goals. Solutions may be IT related, non-IT related, or some combination of the two.
The business analyst is responsible for eliciting the actual needs of stakeholders not simply their expressed desires and often play a central role in aligning the capabilities delivered by information technology with the needs of business units.
It was at this point that some effort was made to better understand what exactly a Business Analyst is, and what BA responsibilities should include. These definitions will ensure that staff can focus on BA activities and are allocated only to those tasks, rather than as an addendum to the responsibilities for other jobs within an Agency.
Working together from the beginning, they set the stage for success by accurately planning and clearly defining the expected outcomes.
Each role provides specialized capabilities and is responsible for a different set of tasks. The PM keeps an eye on the management of the project, ensuring the project delivers on time, on budget and with the full scope of the requirements met.
The BA focuses on understanding and aligning the planned solutions with the needs of the stakeholders.
The Project Manager owns and manages the execution and completion of project deliverables. The Business Analyst owns the development and elaboration of the business requirements, from understanding the business need to ensuring that the delivered solution meets the identified need.
This approach ensures that the result deliverable will be successful, adding the intended value to the organization. On some projects one person is required to act as both the PM and the BA. This is often the case on smaller projects. For the individual, the challenge is to be aware of the overarching project management activities and manage the balance between those activities and the BA activities that must also occur.
For larger projects playing both roles puts the project at risk for either rushing requirements elicitation and analysis tasks and missing important requirements or spending too much time working on requirements and jeopardizing the project schedule.
It is imperative that a BA gets access to and involvement of stakeholders during the life of a project, but especially at inception. Since the final product usually a system is geared towards the end-user, it is vitally important to have them for areas like helping to drive the usability and usage of the end-product, helping to define the business rules, performing User Acceptance Testing, etc.
This will also go a long way in the effort of modeling the system.Creating a Storyboard using Microsoft Word. For some, storyboarding may seem like a tedious extra step in the process of digital storytelling. However, we believe that creating a storyboard is a valuable step in the digital storytelling process.
It allows the user to lay out all of the important elements of the digital story, including. Life of Pi Life of Pi Frame Narrative What is a Frame Narrative?
In a nutshell, a frame narrative is a âstory within a storyâ Examples of Frame Narratives Titanic (the movie) The story of âOld Roseâ revisiting the site of the Titanic âbookendsâ the love story of Jack and âYoung Roseâ onboard the ship in Forrest Gump Forrest (in the present) is telling his life story (of Forrest in.
WAT/GD/PI Preparation I broke my preparation into two parts - Personal questions and current affairs questions. For personal questions I wrote some 50+ questions, building a flowchart.
PI and ID Flowchart and Narrative The following information provides two flow charts and then a comparison of the information.
These charts are performance improvement flow and the ADDIE model. Performance Improvement and Instructional Development are tied together with a few likes and dislikes.
PI and ID Similarities and Differences PI and ID Flowchart. Flowchart Maker Org Chart Software ER Diagram Tool A data flow diagram can dive into progressively more detail by using levels and layers, zeroing in on a particular piece.
DFD levels are numbered 0, 1 or 2, and occasionally go to even Level 3 or beyond. The necessary level of detail depends on the scope of what you are trying to accomplish.