BA Training Online Methodologies
I have knowledge of various software methodologies like Spiral, waterfall, Agile, RAD, RUP. But I have practically worked on Spiral and waterfall.
It is a newer adaptive method of SDLC and it is iterative –the work activities are repeated. This method believes in “build a little and test a little” principle and the project cycles through development activities over and over again until the project is complete. It is a series of waterfall models and is a hybrid of the waterfall and the prototyping methodologies. Just like waterfall we have planning, analysis, design, and implementation phases. In this methodology, the requirements are developed in a number of releases and at the end of each and every release a fully functional model or a prototype is developed and this prototype is enhanced with new features in the subsequent releases and the product is delivered incrementally.
After every release, the gaps are identified and the business feedback is taken and accordingly, the next release is planned. For e.g.; I work on the development of an e-commerce website in which in the first release, the basic features like an online catalog, feature to subscribe to the newsletter, contact us page, etc. were developed. Later in the next release new features were enhanced in the website.
BA Training Methodology
The advantages of this BA training online methodology are:
Estimates of budget, schedule, etc. become more realistic as the project progresses because important issues are discovered earlier. Change management becomes easy as the new modifications can be incorporated in the next release. The client, who is involved in the development of each section, retains management over the direction and implementation of the project. In addition, the client’s knowledge of the project grows as the project grows, so they’ll interface effectively with management Disadvantages include:
Risk of not meeting budget or schedule Costs may go up when new requirements are added. Risk of getting contradictory requirements from the client.
I am very much comfortable with the waterfall methodology as I worked on this methodology in one of my projects. To begin with, Waterfall methodology is the oldest SDLC method and it has been around for nearly 30 years. In fact, it is the foundation for many current methodologies that are in practice today. As the name itself suggests that this methodology is like a waterfall i.e., linear and sequential where one phase leads to the next phase. It has 4 phases planning, Analysis, design, and implementation phases. It is almost similar to the basic SDLC methodology but only a difference is that a couple of phases are combined and formed into a single phase.
Design and development phases are combined and made into the Design phase in the waterfall and similarly, the testing and operations and maintenance are combined into the implementation phase of the waterfall. This method assumes that the client knows all the business requirements upfront. In this method, the requirements freeze too early. Once a phase is completed there is no chance to go back to the previous phase and rectify the mistakes done in the previous phase.
Then there will be only two options either to continue with the errors or scrap the project. Hence this method allows no chance to incorporate changes. This methodology is a well-documented process and procedure, involves extensive verification, validation and process improvement. Advantages of the waterfall: It is easy, simple and if done properly yields huge benefits. It allows the project manager to stick to the timelines and budget and deadlines. It allows for departmentalization and managerial control. Each phase proceeds in strict order without any iteration. If the business doesn’t want to take the risk then this method is best suited. Disadvantages: Mistakes done in one phase cannot be rectified and there is a possibility that the resources get wasted. The business has no control in some phases. Changes cannot be incorporated and hence is not flexible.
How is the agile methodology different from Waterfall methodology? Does it make any difference to the responsibilities of a BA training online?
Agile methodology differs from a waterfall in a variety of ways.
The demarcation between the phases: In agile methodology, there is no clear demarcation between the phases. As soon as the project begins the requirements are gathered by conducting scrum meetings and simultaneously the developers start developing and QAs start testing the piece of code that has been completed by developers. Whereas in the waterfall we have a very clear demarcation between one phase and the other. Unless a phase is completed the next phase cannot begin.
Documentation: In agile methodology, importance is given to the quick development and not on the documentation. In the waterfall, the concentration is on documentation and meeting the deadlines.
Requirements gathering: In agile, the requirements are divided into a sprint and each sprint is developed in 4-6 weeks’ time. Whereas in the waterfall all the requirements are gathered at once and then moved onto the design phase.
Flexibility: Agile methodology gives the flexibility to incorporate changes as new changes can be implemented in the next sprint. Whereas in a waterfall, changes cannot be made once the requirements gathering phase is complete. Agile is very flexible and the waterfall is very rigid and strict.
User stories: In agile we write simple user stories for the requirements and in the waterfall we write an extensive BRD, SRS, and related documents.
Meetings: In agile, we have a sprint planning meeting, sprint retrospection meetings, daily scrum meeting, and sprint review meetings are conducted. In waterfall, review meetings are conducted at the end of each phase.
Responsibilities of a BA:
In agile: Conducting JAD or facilitation sessions to quickly elicit requirements A very simple scope document is prepared by a business analyst online training. An extensive business requirement document is not prepared by BA writes simple 3 sentence user stories which are in the format “As a customer, I should be able to search the product by keyword so that I can get my desired product fast.” BA training online methodology doesn’t draw any use case diagrams or use cases. Detailed test cases are not written but the user stories are modified into the test cases and UAT is carried out.In the waterfall: Extensive BRD, use cases, use case diagrams are written by the BA. Extensive test cases documents are prepared to conduct UAT Spending hours to fine-tune the business requirements having long document review sessions.