top of page
hand-businesswoman-touching-hand-artificial-intelligence-meaning-technology-connection-go-

Understanding the IT Methodology


“Always there will be a ladder you can climb to progress, likewise there will be always an opportunity to improve any process & methodology.”




Any improvements to a process would be based on the following factors;


  • What we Learn

  • What we Practice

  • What we Teach

  • What we Lead


What is Methodology:


A methodology is a particular procedure or a set of procedures that are being followed.


IT Software development life cycle:


Software development will have the same basic framework.








Types Of Methodology


Well known methodology that organization use in software development as follow;


  • Waterfall

  • Agile

  • Lean

  • Feature Driven Development


Two Most Common Methodologies


The two most common methods used in an IT organization are WATERFALL & AGILE.


WATERFALL


As the name suggests the work, flows like a long journey in this method. It has a structured way the work is executed.


  • Plan driven

  • Complete level

  • Complete Documentation

  • Change Management

  • Long time to see the result


The only drawback in the waterfall methodology is that it could take from 6 months to a year to see and test how the final product is working. This may potentially cost or impact the project capital when the result is not as per expectation for the business or users.


AGILE


Agile is a different from waterfall approach, which focuses on delivering features iteratively rather than the entire solution at once.


A road map is created at the beginning of the project, based on what is known at the time, which includes desired features to be added in the solution. This road map is revisited and refined in constructive time, when more information is discovered.


  • Plan Enough

  • Documentation 

  • Change Driven

  • Deliver in small increments


WATERFALL vs AGILE

WATERFALL

AGILE

Cascading layers fully described


Water has a focus on planning and anticipating every aspect of the project before the analysis begins.


Dozens of Cards described just enough


In 2001 the Agile manifesto was created ,This includes a focus on delivering business values, the team driving decisions, delivering pieces of the solution and evaluating feedback focuses on delivering business value along the way.

Workflow


Analysis states complete requirements, design and validation and finally delivers a solution all at once.

Workflow


The cycle is repeated until the full solution is implemented.

Wholesome Delivery


Projects have been done by waterfall fashion for decades and it is still used in many organizations.

Delivered in parts


Agile has a backlog of work items described just enough and delivered in small sections.

Pros and Cons in Waterfall


Pros                                                                          Cons


1.Value in planning the whole project.                        1. Teams are separated.

2. Minimizing rework.                                                   2. Business changes often.

3. Delivering a full solution at once.                             3. Long time to deliver.


Pros and Cons in Agile


Pros                                                                         Cons


1.Value in planning just enough.                                 1. Minimal Documentation.                 

2. Working together.                                                     2. Less Team structure adaption.

3. Delivers parts of the solution.                                   3. Change in work culture.

4. Delivers just enough.                                                4. Rules not transparent.


Both Waterfall & Agile has its own pros & cons, even though Agile has been adapted in most organizations, since it can add value to business & delivers the product iteratively in most viable manner.


Type of Agile frameworks:


Let us see the type of agile frameworks that are practiced widely;


  • SCRUM

  • KANBAN


SCRUM


  1. Team and roles-People play specific functions of roles and responsibility in a team.

  2. Ceremonies-There is prescribed ways to work daily, weekly, monthly or quarterly in ceremonies that the scrum team conducts.

  3. Time box-Scrum has a specific timeframe to complete the work. Parts of works are grouped in sprints where the sprints are usually 2-3 weeks that represents the work items that need to be coded, tested and delivered in that time frame. Requirements will be completed before the new sprint begins.


KANBAN


The word Kanban originated from Japan which means a visual signal.


  1. Visualization-Creating visualization on each step and minimizing the number of items that are worked on at any given time.

  2. Continuous Flow-The work gets completed in a flow.

  3. Pull work- Employees will pull their work when they're ready and by limiting the number of items in progress in any given time where more work will be getting done.



Scrum Structure


As scrum is the most widely used method in the organization.


Sprints-Time boxing

Scrum focuses on time box delivery, typically 2-3 weeks. Work items are grouped in things called sprint and the team commits to deliver them in that timeframe, where at the end of the sprints there will be a review to provide feedback on the sprint to provide in to planning of the next sprint.


Ceremonies

A Strict structure to be followed in specific ceremonies. These revolve around the sprint and the work items.


  • Sprint Planning - Team will make the effort for the work items and plan the sprint based on the work the team can complete.

  • Daily Scrum -  Which is sometimes a daily stand up call, Which is a quick meeting usually less than 15 minutes to report on progress today, tomorrow or any blockers to  complete the work.

  • Sprint Review - Demonstration of the work in the sprint, which is a valuable opportunity to receive feedback from the business right away and that is delivered.

  • Retrospective - This is the lesson learnt in conversation ,that went along in that sprint. What is going well on the team and things that the team needs to improve.


Roles and Responsibilities

                  The defined roles and responsibilities include a Product owner and a Scrum master and all the other members are referred to as a development team.


Scrum team organizing


  • Backlog - It represents all the items that need to be considered for work.

  • Work in progress(WIP) - The items being worked on for definition for the sprint.

  • Ready for Development - Work items will be organized into sprints.


Conclusion


I believe this information would have given a brief idea and the methodology that has been followed widely in IT or any organization. Also I would like to quote “ Software development can follow the methodology that are most convenient and adoptable based on their own business nature. Nothing is right or wrong!! ”


References







54 views2 comments

Recent Posts

See All

2 Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
Guest
Feb 17
Rated 5 out of 5 stars.

Very helpful and easy to understand for someone new in IT and to understand the difference of traditional waterfall & Iterative Agile scrum methodology.

Like

Guest
Feb 16
Rated 5 out of 5 stars.

Easily understandable.

Like
bottom of page