Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

Do you have the right steps in your project life cycle?

Posted on: 06 May '11

Today software is either a part or is completely involved in all things around us, be it dental implants or television remotes.  Building and deploying these software solutions are moving from intense programming to clever assembling of application logic. Established frameworks and ready to use products are gradually replacing the need to reinvent the basic programming constructs. While this change seems to be for good, the challenge is shifting to managing the life cycle of “new” projects.

While developing applications with general purpose programming languages(GPL), we follow the well established Requirements to User acceptance steps(see the graphics below); but these steps and sequence of activities may not be valid while dealing with projects based on standard frameworks, software as a service, off-the-shelf solutions or possibly any project that does not use GPL for ground up development.

Custom software development using GPL

To make my point let me apply the above activities to an Off-The-Shelf (OTS) Web Content Management implementation where customers are being introduced to the Web Content Management for the first time. Chances are that the requirements workshop will not yield fruitful results because customers don’t know what they don’t know. In such situations, the first step in the Project Life Cycle is not Requirements but Deployment (of the Off-The-Shelfproduct). Just the Deployment is usually not sufficient because Off-The-Shelf products are built generic, some amount of configuration is required to bring the application closer to customer needs, therefore we now have to do follow Design and Implementation based on what we call “implicit needs”. Once all of this is done we will be ready to show the customer what Web Content Management can do for them, then from that understand the specific changes that they would need – Requirements.  So the project life cycle for Off-The-Shelf Web Content Management implementation will be as below.

OTS implementation

Below is another example, for a hosted solution where the notably missing step is Deployment.

Hosted solution implementation

Why is it important for us to know the Project Life Cycle at such a high level?  Experiential patterns coming from repeated implementation of certain type of projects have taught us meaningful sequencing, planning and staffing projects based on the technologies involved. Wrong choice of Life Cycle will lead to unproductive steps that will affect downstream activities.

Jana Reddy

Jana Reddy is Program Director of The Digital Pumpkin and brings 15 years of IT experience in Digital Transformation. Jana's professional background is in the area of packaged software implementations from eCommerce to Digital Marketing solutions. His current portfolio in The Digital Pumpkin is to bring IT and Business organizations together for conceptualizing Digital Solutions of future.

  • Vaibhav

    sounds interesting one… i think these things only hapning in real world senarios… it seems very useful for me as i m student of final year… Thanks for this…

  • Kumar Raushan

    Requirement analysis is a process to understand the exact requirement of the customers and it’s a very important stage of software life cycle. If we will keep the customers requirement in the mind then only the developed software will fully fulfill the customer’s requirement.

    The main goal of the requirement analysis is to weeding out the INCOMPLETENESS and INCONSISTENCIES of the developed software. Once software is developed then it’s a difficult task to change it according to the customer’s requirement because relative effort of development of a software product to its maintenance effort is in the 40:60 ratio then also we need to do the Perfective maintenance, which is the process of improving the implementation of the system and enhancing the functionalities of the system according to the customer’s requirement.

    If we will follow the suggested approach to develop a product then we will achieve our goal of requirement analysis phase and in this way we will be able to reduce the work load of maintenance phase also. If we will successfully do this then definitely we will satisfy the customers/users requirement.

  • Ravikumar More

    while developing the software first of all the need is that customer requirement the as per the requirement design process is done. then implement the requirement issue and then go for testing because whether the design showing proper result or not. then go for deployment and then user acceptance within time with full fledged requirement. after user acceptance we can add more requirement with proper module.

  • Normally I do not read article on blogs, but I would like to say that this write-up very compelled me to check out and do so! Your writing taste has been surprised me. Thank you, very great article.