Introduction Product Backlog Vs Sprint Backlog In agile ways of working, backlogs play a crucial role in organizing the work and prioritizing tasks. Backlogs are the only source of truth that helps the development team understand the list of activities / work that it needs to undertake for successful delivery of the project. Backlogs provide…
Introduction to Agile Coach vs Scrum Master The Information Technology Industry since its inception understood the essence of agility as the user requirement continuously evolved due to the rapid advancement in technology and the associated ecosystem. This got further impetus with the digital transformation wave that touched almost all sectors along with an overwhelming need…
Introduction to Agile Implementation Challenges In today’s fast changing environment of software development, Agile has become the go to mode of working to be more flexible, efficient, and improve continuously. With its benefits of delivering quality products faster and adapting to changing requirements, most of the organizations have moved towards agile ways of working . …
Introduction to Agile Manifesto and Principles In the early 1990s, software development was going through something called “the application development crisis.” People started to notice a significant lag in the delivery of new software development applications. It was taking them too long to deliver the projects, and often when the projects were delivered, they were…
Introduction to Agile Team Structure Agile is one of the most widely accepted ways-of-working to approach a project in recent times in the industry. Organizations are choosing agile over other approaches to reap the benefits of increased customer satisfaction, responding to market changes, and staying relevant in the VUCA world. Agile is a different way…
Introductions to Agile Principles In today’s environment, continuous evolution, responding to change and ever increasing demands are must for every organization. Agility in practice, both at organizational and individual levels, thus becomes very important and key to giving an organization a competitive edge. Agility in its simplest sense is nothing but continually moving in the…
Planning and initiation is a key part of any project be it a traditional project or an agile project. While traditional project delivery includes planning everything up front and then moving to design and other phases, agile planning involves a concept of “Just enough”. Why does Agile recommend ‘just enough planning’? In this VUCA world,…
Traditional projects had requirements in the form of work breakdown structure which were written as features (Ex: login feature, search feature). With this type of requirement writing, development teams wrote code while keeping in mind the specifications written by the business analyst. However, a single project had multiple personas involved with each likely to use…
“Two-thirds of the Earth’s surface is covered with water. The other third is covered with auditors from headquarters.” – Norman Ralph Augustine Sarcasm is also an intent in mentioning the above quote and at the same time, it is to showcase the wide presence of auditors in today’s corporate world who are primarily responsible for…
Any project involves Planning, Doing, Checking, and Acting/Adjusting as part of the delivery (the all-familiar PDCA). We start with requirement gathering, move to planning followed by designing, and then proceed with development, testing, and deployment in that order. These are the basic steps involved in the development of software or basic steps to follow for…
