- Do you want to get an interesting and promising position of a Business Analyst, but do not know where to start?
- Are you already working as an Analyst or with requirements (even though you are not calling yourself an Analyst), but are not sure whether you are doing it right?
- Are you just planning to move to IT, and business analysis seems close to you in spirit?
- Do you plan to create your own product, but are confused because you are not familiar with the process of describing the idea?
- Have you lost faith in training courses that force-feed you theory, which you forget the next day?
It is for you that we created a practical Business Analysis Big Bang 3.0. It will answer plenty of questions related to the requirements for software and business analysis in IT, and will guide you onto the path from theoretical knowledge to practical use of analytical techniques and world practices.
We created this course in order to prepare a Business Analyst and immediately after the completion of the training, you can start a successful practice.
This course is filled with only those techniques that we actually use ourselves in daily work, and which will help you confidently carry out business analytical tasks on your own projects, confirming your reputation as a professional.
How is it going to be organized?
The training format: theory online => homework => practice off-line => weekly online testing - lectures and practical seminars, twice a week for 2 hours in the evenings within 2 months in 19 lessons (10 theoretical, 8 practical, 1 lesson with a recruiter!)
Starting from October 17, 2017
Theoretical part are taught on Mondays at 19:00, practical ones on Wednesdays, or Thursdays at 19:00 not far from Shulyavska subway station.
- Only proven and real working business analysis techniques,
- A foundational theory that can be applied as soon as tomorrow
- Practical work with real examples
- The opportunity to go through all stages of the Analyst's work, from identifying stakeholders to supporting the development and independently preparing all the most important analytical documents
- Homework and a joint discussion of the results
- Testing your knowledge weekly
- Preparation for an interview and advice on creating a BA resume from professionals - practicing Business Analysts and IT recruiters
- An individual approach in every meeting
- Use of the most widely marketed JIRA and Confluence tools for performing analytical tasks
Our course is going to help:
- Those who are not yet working in IT, but really want to get into the sphere and understand that the analytical mindset will help them enter the profession much quicker
- Those who already work in IT, QA Engineers, Developers, Support Engineers and Managers who understand that business analysis is exactly what they want to do
- Those who are interested in business analysis skills, and who want to properly understand how business analysis works
- Analysts who want to have an awareness and experience of business analysis in international companies and learn how to apply practices from around the world
1. Introduction. General information about the software development process and the place of the analyst and the requirements in said process
- The life cycle of software development (SDLC)
- Distribution of roles in the software development project
- Definition of terms “business analysis" and "a Business Analyst"
- The software requirements and their levels
2. The main Business Analysts’ responsibility – communication and interaction with a customer (communication with a customer)
- Acquaintanceship, setting up productive and maintaining good relationships.
- The beginning of the analysis phase is a root cause analysis and stakeholder analysis. Why is it so important to start with identifying the causes and stakeholders and how to implement it effectively?
- Customer Journey map
- AS IS / TO BE analysis
- Methods for Stakeholder Analysis
- Requirements elicitation is daily analytical work. How to do this work qualitatively and effectively?
- The Stages of Requirements Elicitation Process.
- The technics to elicit requirements: an interview, brainstorming, observations, requirements workshops, etc.
- Customer sales and presentation skills.
3. The creation of analytical artifacts - software requirements documentation
- Documentation of various levels and formats:
- High-level requirements: a product vision, business requirements document, technical specification according to the best practices samples.
- Requirements specifications: user stories, use cases, functional and non-functional specifications, software requirements document (SRS) according to diverse samples.
- Modeling requirements with UML
- User Interface prototyping
4. Communication with a development team and software development support
- Task breakdown into components
- Effort estimation required for analytical work and participation in the labour estimation for software development.
- Accompanying the daily work of the team, communication with the client and team in the development process.
- Managing requirement changes
5. Continuous improvement of business analysis process and business analyst’s work.