Author name: Sparsh Goyal

A passionate IT professional, Sparsh Goyal boasts of 4.3+ years of experience. He has worked for various projects under AWS, Google Cloud Platform, Spring Boot, Python, Microservices, RESTful, RESTFUL APIs/SOAP, Scripting, Shell and JAVA. He is also working towards gaining proficiency in Oracle Cloud PaaS, DevOps, SaaS and Docker/Kubernetes. His primary and secondary skills validate his relentless pursuits of expanding his horizon and developing more as an IT person. He boasts of the following certifications: *Google Professional Cloud Security Engineer. *AWS Cloud Solutions Architect Associate. *Oracle certified JAVA programmer.

Tracking the Value delivered in the agile world

Tools to track the value delivered: How do we track the value delivered to the customer in the Value-driven delivery? Below are some of the ways to achieve the same: Kanban or Task charts Burn down charts Risk management and risk burn down charts. Earned value management Burn down charts: What are burndown charts? Burndown charts measure the work done by having the time represented on x-axis and the work to be done in the y-axis in a chart. You can measure them either using story points or hours as measuring units. The burn down chart depicts whether the team […]

Tracking the Value delivered in the agile world Read More »

How to calculate value in value driven delivery

The methods to calculate value: The value in monetary terms can be calculated using many terms: Simple schemes – rank the requirements from high to low. Present Value: The process of calculating the value today on future amount and can be calculated using the formula PV=FV/(1+i)n where PV = Present value, FV=Future Value, i=interest rate, n=number of periods. Internal rate of return (IRR): It is the discount rate at which the project revenues and project costs are equal. The project with the maximum IRR is selected. MoSCoW prioritization: This is based on the category prioritization where everything falls under any

How to calculate value in value driven delivery Read More »

DSDM – Principles and approaches abiding the principles

Dynamic Software Development Method (DSDM) works with 8 principles basically abiding by its philosophy. The ultimate goal is the completed and successful project. Business requirements are the main focus Timely delivery Collaborate High Quality Standards Incremental approach in developing the software Develop iteratively Communicate continuously and clearly Good control on the overall process. DSDM follows the 4 processes to achieve the project objective abiding by its philosophy throughout. Feasibility Foundations Evolutionary developments Including the pre-project and the post project there are totally 6 phases in a project life cycle. Feasibility gives a nod on whether we should continue with the

DSDM – Principles and approaches abiding the principles Read More »

Dynamic Software Development Method

DSDM is a software development methodology which believes in abiding by the strategic goals of the project and delivering value to the customer early. Best practices proven successful over the years in the industry are recognised and recommended by DSDM in the agile software development world. DSDM is a vendor free methodology where the best practices prescribed can be applied using any tools and software. It builds quality into Rapid Application Development (RAD) approach by providing tested methodologies over the years. DSDM believes in something called as ‘Enough Design Up Front’ (EDUF) where the initial design is minimalistic and it

Dynamic Software Development Method Read More »

Agile Software Development – Methodology

The agile software development is an umbrella containing a set of methods and ways to achieve the principles mentioned under the Agile Manifesto. All these methodologies abide by the principles of frequent collaboration between the teams, frequent delivery to the client, self-motivation etc. The methodologies currently being followed are Extreme programming(XP) Dynamic System development method(DSDM) Scrum Agile modelling Agile unified Process Agile Data method Essential Unified Process(Ess UP) Feature Driven Development Open Unified Process(Open UP) Lean Software Development Crystal Methods. Selecting what methodology to use depends on what the project is. There should be a proper thought process on how

Agile Software Development – Methodology Read More »

Agile Software Development – Approach

Agile development methodology – Approach In the Agile methodology, each project is broken up into several ‘Iterations’. All Iterations should be of the same time duration (between 2 to 8 weeks). At the end of each iteration, a working product should be delivered. For example, in the agile approach the project will be broken up into ‘N’ releases (assuming each iteration is set to last 4 weeks). Then the team will decide the basic core features that are required in the product and decide which of these features can be developed in the first iteration. Any remaining features that cannot be delivered

Agile Software Development – Approach Read More »

Agile Software Development – Manisfesto

Agile software development methodology is a process for developing software. This is a model where the software is developed in rapid and incremental mode. This is an alternative to traditional software development. The importance is given to the working software than the documentation. Every iteration ends in a working software which is a business value to the customer. The Agile Manifesto In February 2001, 17 software developers met at the Snowbird resort in Utah to discuss lightweight development methods. They published the Manifesto for Agile Software Development, in which they said that by “uncovering better ways of developing software by doing it and helping others

Agile Software Development – Manisfesto Read More »

Stakeholder Engagement in Project management

Who is a Stakeholder? A Stakeholder is person, or group, or organization that is impacted by your project. How do you manage stakeholders? Stakeholders are very important for your project success and they can make or break your project. You cannot be more than careful while handling stakeholders. The most important part of stakeholder management is communication with the stakeholders. As an agile team, we have to always think and communicate with stakeholders.  First and foremost we have to classify stakeholders into: Internal External Supporter Resister etc.  Stakeholder classification is typically based on the following criteria: Impact on the project

Stakeholder Engagement in Project management Read More »

Minimum Viable Product or Minimal Marketable Feature

So, how many of us understand these terms.   We are sure most of us have heard these terms but yet know nothing or very little about them. Lets us explore these terms: Minimum Viable Product or Minimal Market Feature are synonyms means the baseline of a product that contain enough features that it can showcased to the client as first raw cut. It will have the basic skeleton of the business case that the product stakeholders are trying to solve.  The product itself will have the bare minimal feature working but it will be able still solve the main gist

Minimum Viable Product or Minimal Marketable Feature Read More »

Project Charter and its usefulness in Agile

So how many of us know Project Charter? Most Project managers will say they do.  Most developers will say that they don’t.  I didn’t till one has to look deeper into this in one of Agile project. Lets us discuss the technical aspect and then discuss how I used it in my daily life. Definition of Project Charter from PMBOK® “ A formal document that authorizes the project into existence and allows the project manager to use organization resource to project activities” What is Project Charter? This is most important document that will allow us to  help identify the scope,

Project Charter and its usefulness in Agile Read More »

Scroll to Top