Skip to main content


Many people in the software industry have heard about Agile. It is ubiquitous and can't deny the fact that it is redefining the way of how software is developed.

But most of the people do not know what Agile is not. Software developers who have worked in AGILE have their own definitions. Rather, every company / organisation has their own definition for AGILE [which is good and bad at times].

Looking at the last two decades when the software industry had begun its maturity, there were few methodologies for developing softwares. These methodologies were based on Process and Principles. A lot of focus was given to documentation which led to excess and result in efforts as well as maintenance. In Agile focus is more on delivering smaller piece of software which requires very less documentation. This means AGILE is not an excuse to producing documentation. It can be in various forms such as user stories, Epics, meeting notes etc.

Software professionals often mistake Agile as a process driven method. It’s not! Agile is more of an iterative and adaptive approach as compared to the traditional waterfall where there are various stages where the software could see the light of the day after months of work without knowing if this is what customer wants.

The Waterfall method is notorious when it comes to changing requirements where as Agile is seen as the saviour, but that is not just what  Agile is. It eliminates the risk of changes in the last stages when the software is about to be delivered. It is more about collaboration with Customers and Team members

Popular posts from this blog

Do you really need a Business Analyst in your project ?

Do you really need a BA or a similar fulfilling role in your project?

My Aunt has been in a Real estate and construction business for long time. When I was a kid, I used to visit her to every now and then to spend some time. As a part of the visit, I was often told by my cousins that she is at the construction site. 
Building a small house over a chronological period I got to experience how the house was built from scratch. I saw how the construction workers did the job as they were guided by the contractor. 
I also experienced that when it comes to big buildings, there is always an architect who creates the blueprint of how the house is going to be, what dimensions the rooms are going to be.
Notice how this is an analogy for any system we build. Our systems can be small where you don’t really need a Product owner/Business Analyst or we need somebody exclusively who is just for gathering/writing the requirements.

 If you are building a mid to large-scale system, you do need to have a dedi…

User Stories Simplified!

User story writing guide
When I was introduced to the world of Agile, I kept on hearing the words  “User Story”. I couldn’t apprehend what it meant and how it possibly could be a fit for requirements management. This was all due to the traditional waterfall methodology which was omnipresent in most of the software projects. Early in my career we totally relied on creating massive amount of documentation which included but not limited to *Business requirements document Software requirements document High level design document Low level design document Use cases
 You can clearly see where the problem lies if you are planning on to maintain all these documents. On top of that, if you are working on mammoth projects, good luck with that!
How does user story  might prove to be user full?
First of all, User story is not a Silver Bullet but a convenient way to represent requirements. More precisely what a user intends to do.
In my case study, I am going to use example of “loremipsum” which is a social …

Product Management

Product Management

Once I had a conversation with one on my friends who just happened to join a startup. He said he worked as a Product Manager and was talking in general about roles and responsibilities .
What surprised me was that his roles and responsibilities differed from what I have seen in the market. Nothing wrong with it, this happens with other roles also. 
Product management roles vary depending on organisation to organisation. It is hard to define the roles and responsibilities. Though all have a common goal to making the product successful but vary depending in what department you are in or what phase part you are working on. Example : Some folks work in the analytics are Product Manager.

Talking about my friend, he was more into forecasting for the application, looking at the revenue growth. When asked about who builds the road map, his answer was that the tech team and the business decide.  A fairly common scenario. 
So what are the Roles and Responsibilities of a Product Ma…