Business Analyst working methodology

business analyst
Anyone trying to pursue a career in analysis of the company must have heard of terms such as waterfall, agile, scrum etc. These software development life cycles are named differently since the method adopted to reach the solution is significantly different from the other. The life cycle phases are essentially more or less the same in each of these different methods. So the important question to ask is if the phases of the life cycle is the same then what is the need to appoint the different life cycles? What do these names mean to me as a business analyst? What things should I do if the different lifecycle stages are essentially similar?
To start each life cycle requirements analysis, software design, implementation, verification, and maintenance phases. Which differs essentially is how these steps are performed in each lifecycle. Let’s talk more about the methodology of the waterfall. It is one of the most classic of building the software means. It is a sequential design process where each phase of the needs analysis through implementation are completed before the next phase can begin. Sequential phases have less or minimal, if any, overlap or “splatter” back waves. The waterfall methodology works well enough for any project that is six months or less. Well what I do not mean that the project is of longer duration and the waterfall methodology can not be applied to software development. It is important to understand that a project of longer duration will also have a myriad of requirements that will change over time. Thus, when the solution finally released, there is a high probability that most of the requirements may have changed. Contrary to this methodology are incremental methods. Incremental method can also be iterative. Now, what is the net difference between incremental and iterative methods complementary?
The incremental method to do work can essentially be best understood as clubbed together of several water drops. By this I mean that the project is divided into small increments. Therefore, needs analysis, design, implementation, verification or testing is performed for each small increment of the project and then the team goes to the next. The important thing to note here is that all the conditions are met before the start small increments. While the iterative cycle is a style where the software is developed incrementally on short iterations and this gives a lot of latitude to take into account changes that are part of any project. The requirements met just before the iteration, they are being developed. With this lifecycle chances of making incorrect assumptions is minimal. It is currently the most preferred because the life cycle of the unique feature of having a working software all the time of each iteration. There are several variations of this method otherwise also known as Agile such as Kanban, melee, the development of dynamic systems. There are several other lifecycle methods, as well as the code and fix, adaptation, incremental and iterative, evolutionary.
See the IIBA BABOK Guide for detailed information on the SDLC lifecycle.