InQuestra is the world’s first and finest e-learning company focused exclusively on online courses, testing and assessment tools for Business and Systems Analysis.
InQuestra courses are professionally designed and developed by industry experts.
Our products cover the range of e-learning from on-line web-based training to CD-ROM computer-based courses.
And you will find InQuestra courses extremely competitively priced.
InQuestra courses are practical, non-theoretical e-learning of the highest quality. There are many courses that are good at teaching software engineering theory. Many courses explain the pros and cons of various methodologies. InQuestra courses incorporate these theories and research but provide the learner with a specific standard process to follow, techniques to use and skills – all based on industry standards and proven, successful best practices.
Showing 1-23 of 23 results
The purpose of this tutorial is to expand on the role of the Scrum Product Owner and outline the roles played and deliverables produced in the various stages of the Scrum process.The Scrum Product Owner role is vitally important as they are the only person that determines and prioritizes all the features of the product.
describing all the Scrum Team roles with particular focus on the Scrum Product Owner
what User stories are and how to create User stories that are ‘Agile”
how to build and prioritize your first and subsequent releases
using the Relative Value Scoring, Relative Weighted Value Scoring and the Risk-Value
how to build and interpret Sprint and Release burndown charts
how the Product Owner participates in the in the Sprint Demo and Retrospective
how the Scrum Product Owner role is a natural fit for the IT Business Analyst.
The agile value system and how it impacts strategy and tactics
Scrum – what are the fundamentals of this agile methodology
Roles of Scrum Master – who plays this role, and how does this role improve management of the project
Role of Product Owner – Who plays this role, and how does this improve stakeholder communication of needs in the process
Role of Team Member – Who plays this role and how does this develop a collaborative environment between business and IT
How do the roles work together to gain greater commitment to timetable and functionalities
Where do traditional roles of Analyst and Project Manager fit within these role definitions
What does the Scrum process look like
What makes effective user stories
How do you build commitment on sprint planning and defining ‘done’
How do key techniques like burndown charts, daily scrum, and release burndown work
How do you bring the critical elements together to maximize performance
Since the introduction of Use Cases by Ivar Jacobson, Use Cases have been misunderstood, misrepresented and misused. This is further complicated because people throw the Use Case term around without defining what type of Use Case they mean.
Have you struggled with questions like these?
What is the real purpose of Use Cases?
Specifically, how is the Essential Business Use Case defined, documented and described?
How and where do Business Rules fit?
What is and when is the best time to do Use Case Diagramming?
What are the Pro’s and Con’s of Use Cases?
This tutorial is intended for those who are relatively new to the Use Case world and want to do it ‘right the first time’, or those who wish a quick refresher in clear unambiguous terms. This course focuses on ‘Essential Business Use Cases’ which are the foundation to any further development. At the end, you have the opportunity to test your level of understanding through an interactive quiz feature. A Use Case template is also included.
What does it take for a Business Analyst to successful on an Agile project? The first thing to realize is that there is no title/role/function of Business Analyst in any of the Agile methods, whether they by Scrum, XP, FDD or Lean. However, that is not to say there is not the need for 'business analysis skills' as an integral member of a cross-functional agile Team. Your tasks can range from leading, guiding and shepherding product features/epics/themes; user stories; iteration and release planning/mapping and modeling through participation in GUI, data definition and testing activities.
Developing A.G.I.L.E. User Stories using Best Practices
Learning three (3) ways to apply Risk Value to Use Stories
Building an Iteration & Release Plan
Mapping the Agile BA Traits to the Essential BA skills
Understanding the Inhibitors to Agile Analysis
Transitioning to an Agile Coach
Enhancing Your Agile Skills
Unlike other methodologies, Agile methodologies and in particular Extreme Programming, commonly known as XP, have only been around for 10 years or less. Their principles are changing our industry’s collective thinking about developing application systems. However, all is not evolving as expected and struggles with discovering, defining and documenting User Stories are surfacing.
Have you struggled with questions like these?
How do I put User Stories in their proper context?
How detailed should each User Story be?
How do I write User Stories consistently?
How do I determine the dependencies between User Stories?
How do I deal with contradictory and ambiguous User Stories?
What is the Extreme Programming Development Cycle?
This tutorial is intended for those who are relatively new to the User Story and Extreme Programming world and want to do it ‘right the first time’, or those who are experienced and want to pick up some tips and techniques before tackling their next XP project.
This tutorial is intended for those who wish to gain an understanding of the BA Body of Knowledge (BABOK)ä without having to navigate the full 300+ pages of the current version. You might be a Business Analyst interested in obtaining your IIBA Certified Business Analysis Professional (CBAP)ä designation. Maybe you are a Manager trying to gain a sense of what knowledge areas your people need to be focusing on. Or, perhaps you are just interested in keep abreast of the latest developments in the industry and BA Community.
This tutorial introduces the learner to the six BABOKä Knowledge Areas: Enterprise Analysis, Requirements Planning & Management, Requirements Elicitation, Requirements Analysis & Documentation, Requirements Communication and Solution Assessment & Validation. It also includes the fundamental principles and structure that support each Knowledge Area. At the end, you have the opportunity to test your level of understanding through an interactive quiz feature.
This tutorial is intended for those Managers who want to gain an understanding of Project Management Concepts and the role that a Manager might play in projects.
This tutorial introduces the learner to the four major Project Management process groups:
Control and Closing.
It also reviews the roles and responsibilities of the primary stakeholders in projects including the Sponsor and Project Manager. It also reviews the role and responsibilities of a Functional Manager in all process areas that contribute to project success. When you have finished the course, you have the opportunity to test your level of understanding through an interactive quiz feature.
Many organizations are starting to reap the rewards
from Agile methods to their development practices.
Lean what Project Managers and Business Analysts need
to know to define requirements in Xtreme Programming
This article introduces the reader to the Business
Analyst role, provides a description of required BA
core competencies, provides content for the
development of BA position descriptions and suggests
some tips to build strong BA capabilities.
The goals of this paper are to:
1. provide you with an analysis strategy that defines
clear, concise, consistent and
unambiguous user stories.
2. minimize the release planning spike which saves
time, money and resources.
We're all looking for the "top performers" the guys
that will deliver the 40% increase in productivity
relative to that average Joe. This paper is about how
to accomplish this goal.
Are you looking for a way to prove your skills are excellent? Are you an employer that wants to make sure candidates are qualified to play the pivotal role of Business Analyst in your company?
From a pool of over 850 "cognitive domain" questions, InQuestra’s innovative testing software will randomly select 250 questions – weighting these to provide insightful feedback in 13 vital areas of Business Analyst Competency.
This online assessment is intended for those:
1. Job Seekers – To attach a Skills Certificate to your resume
2. Professional Analysts – To help target career development needs.
3. Hiring Managers – To baseline skills.
4. Human Resource Managers – To assess training impact or improve the hiring process.
5. Recruitment Firms – To differentiate your candidate screening for clients.
You've studied the IIBA® BABOK® v2.0 for hours. You may have taken a 'prep course' and joined a 'study group'. What's left to do? Be absolutely sure that all your hard work will pay off by taking our practice (simulation) exam.
This online exam is intended for those Individuals who are considering sitting for the IIBA® CBAP® v2.0 exam and for Study Groups that want to simulate the IIBA® CBAP® v2.0 Exam. This is not an IIBA® CBAP® v2.0 prep course. This is a practice exam that tests your knowledge of the IIBA® Body of Knowledge (BABOK® ) version 2.0 with the same number of questions, the same weightings as the actual IIBA® CBAP® Exam and the same time duration. From a pool of over 300 questions, the software will randomly select 150 questions that correspond to the BABOK® v2.0
InQuestra is the worldï¿½s first and finest e-learning
company focused exclusively on courses for IT
Business and Systems Analysis. Consists of (8) web-
based and CD-ROM courses, includes a BA certificate
This course is a high-level overview of the entire Requirements Elicitation Process. It introduces the learner to all the steps in the process, along with terminology, modeling tools and techniques.
Imagine being able to walk into any business area and be able to elicit your client’ business requirements, completely, accurately & consistently, regardless of the amount of experience you have in that subject area, regardless of the years of IT experience or your education level. Imagine being able to communicate with your clients in business terms and language that they understand and relate to using non-threatening, non-technical techniques. And perhaps most important of all, imagine being able to obtain their agreement that what you are modeling is truly what they want and need, immediately securing their buy-in. That’s what this course is all about.
This is one in a series of courses that focus on the phases of The Requirements Discovery Process. This course is intended to take the participant through a process of discovering, describing and documenting your client’s business objectives.
Establishing high quality objectives is essential to the success of your project. If you don’t set specific, measurable, achievable, results oriented and time-bounded objectives, how will you ever determine the success of your project? On the surface, setting project objectives seems to be a straight-forward exercise - one that is often taken for granted, overlooked or simply ignored. Establishing high-quality objectives is an essential component to the success of your project. If you do not set specific, measurable, achievable, results-oriented and time-bounded objectives, how will you know if your project is successful? This course is intended to help you do just this.
The descriptions of key business processes that you create during this phase of your project provide the context for all work that follows. For the requirements team, breaking the system into activities helps to focus discussions on smaller areas. For your business partners, it is easy to achieve consensus and buy-in at an activity level. For the project manager, organizing the system into activities allows the project manager to identify cohesive work packages. The detail gathered at this stage enhances the product description and confirms the project scope. For the design team, this discussion of business process at an activity level ensures the integration of the functional and data requirements and provides the basis for the software system specifications. And finally, for testers, activity descriptions provide the basis for meaningful test scripts that reflect actual business usage.
This course is intended to take the participant through a process of describing and documenting the scope of your project. Scope defines what is, and is not, part of our system.
The course teaches techniques to identify the in and out-of-scope business activities, objects, interfaces and variations as a fundamental first step to scoping the product functionality.
Elicitation methods are covered that involve subject matter experts and representatives from other systems and departments.
The discussion of scope also introduces the project team to methods of modeling the high-level scope and ensuring an appropriate level of detail is specified that will enable a fast and accurate start to a project. And we’ll be applying best practices along the way so that your definition of scope will contribute to the definition of business requirements that conform to industry best practices standard deliverables.
This is one in a series of courses that focus on the phases of The Requirements Discovery Process. This course is intended to take the participant through a process of describing and documenting business information or data needs for your project, regardless of the corporate system development methodology, or technical platform implementation.
For those who are relatively new to data modeling concepts, we have simplified the rules of normalization and business rules that give you a jump-start on your next project. If you are more experienced in data modeling, you will see the ease of obtaining the object definition, relationships, cardinality and modality from your clients which enable you to build a solid conceptual data model, based on true business needs. Additionally, you'll have the context for data usage for each business process. And we'll be applying best practices along the way so that the resulting requirements you specify will conform to industry best practices.
This is one in a series of courses that focus on the phases of The Requirements Discovery Process. This course is intended to take the participant through a process of discovering, describing and documenting your client's business requirements completely, accurately and consistently regardless of your subsequent system development efforts.
This means that whether you are specifying these requirements for a web-enabled application, object-oriented, client-server, legacy system or a combination, true functional business requirements are independent of technology. This is beneficial because you won't need to go back and change the business requirements as the technology changes (which is often).
And we'll be applying best practices along the way so that the resulting business requirements you specify will conform to industry best practices in this particular area.
This course is intended to take the participant through the aspects of capturing and documenting Business Requirements completely, accurately and consistently regardless of your subsequent system development efforts. In fact, the skills that you will learn in this course can be used to capture discussions that are completely unrelated to developing systems.
Whether you are an experienced analyst, or new to the field, at the end of this course you will be able to:
walk into any requirements meeting and synthesize the information from your subject matter experts and document their true business requirements in the context of how they are needed;
compose business requirements that are clear, concise, complete and unambiguous that any developer or client and others can understand and use; and
organize and package the requirements in a deliverable or work product quickly and use it as the source for subsequent development, RFP or build/buy decisions.
Industry gurus such as Inmon and Kimball have recognized that the models and methods to design a Data Warehouse are unique and different than traditional data modeling practices.
This course covers the How-To's of performing quality business requirements analysis for data warehousing projects.
Identify, validate and document your Client's Requirements for a Data Warehouse, Data Mart or Decision Support System with confidence
Ensure that raw business data harvested from legacy transaction processing systems and other data sources is transformed into powerful Business Intelligence
Learn the latest practical techniques & best practices for specifying DW systems
Work directly and interactively with business clients in defining project requirements
Finally, there exists proven and practical techniques - which can be easily applied to your DW projects - to gather and prepare quality specifications for Data Warehouses, Data Marts and Decision Support Systems.
This program is geared towards the serious Business Analyst and organizations that desire a recognized
professional designation in the area of Business Analysis. Consisting of 8-courses it complements and
tests your current business analysis competencies.
At the end of each course the candidate is required to pass that course’s specific exam. All eight courses must be successfully completed to be considered for graduation.
Once the candidate successfully completes the program requirements (where an individual course certificate is generated), submission of those ‘proofs of completion’ must then be sent to the InQuestra corporate office. The Registrar will validate the application and, if approved, an official “Business Systems Analyst Certificate” returned to the graduate. The graduate has then earned the right to affix the BSAC initials to business cards, resumes and other documentation where applicable.