Monday, 14 April 2008 09:09

Failing to Plan is Planning to Fail

Written by  Nilesh Raje
Rate this item
(22 votes)
There is a popular adage often attributed to Benjamin Franklin, the father of time management, "Failing to plan is planning to fail," The quote may sound like music to your ears but planning for business analysis work is a key area which tries to zero in on the importance of planning in a software development project. Sadly, it is a step that is often overlooked.

The absence of proper planning can detrimentally affect timely meeting of the on-going project deliverables. To avoid such a failure it is vital that a project manager ensure that the requirement planning activity is given due importance, so that everything is under complete control.

So, how can a project manager ensure that a business analyst (BA) is given the power of execution to get the things delivered with the required level of quality and within the defined time frames. Let's examine some of the key pointers essential to effective business analysis planning.

The Planning Stage

The planning stage gives a high level understanding of the intended software product. It gives the project team a pulse of the current systems and processes, while evaluating the existing deficiencies and identifying the key objectives that need to be addressed in the proposed software development activity.

The planning stage also helps the stakeholders identify the risks that may be associated with the project. Over time, the business requirements keep growing in an attempt to enhance the existing functionality. The objective of the planning stage is to make it absolutely clear - working in partnership with the client and the development teams - what full range of functions and content will be addressed.

The Kick-off Meeting

The kick-off meeting is the opening play of the project. It is an ideal occasion for the project team and the client to introduce them selves and set the project expectations and milestones. The meeting should identify the team roles across the entire spectrum of project related activities, in order to ensure that these activities get completed smoothly.

Requirements Tools and Templates

The business analyst analyses, documents, manages and presents the project requirements for review and approval to the client in a comprehensible manner. As part of the planning process, and early in the project, the BA should communicate to the customer the standard templates and requirement management tools they will adhere to, in order to document the requirements specifications.

For projects large in size and complexity, it is important to make use of requirements management tools to manage version change, track requirement status, communicate with stakeholders and reuse the requirements wherever possible.

Define Points of Contact and Escalation Hierarchy

Should there be any queries or concerns regarding any aspect of the planned project activity, it is important to define a clear process to identify the key points of contact in the project engagement with proper escalation mechanism.

The steering committee is responsible for advice on strategic direction, overseeing planning and implementation, resolving open issues, achieving the project deliverables and milestones, and for preparing a weekly project status report giving updated and accurate information as the project progresses.

The Requirements Sign-off: A Project Milestone

It is imperative that every project participant understand what the Requirements Sign-off means, and its associated impact on the project. Clients should not dismiss sign-off as meaningless, but rather consider it as an important project milestone.

Requirements sign-off means a formal agreement with the project stakeholders, stating that the contents of the requirements document, as drafted, are complete to the final projections and that there are no open issues left to be addressed.

Obtaining a requirements sign-off is typically the final task within the framework of Requirements Communication, which is an expression of the output of requirements gathering to all those concerned with the project.

Conclusion

A holistic approach is absolutely essential and indispensable for the success of the project. It takes effort to leverage and climb the ladder of success. The journey is indeed rewarding and also a voyage of discovery.


Nilesh A. Raje is a Sr.Consultant (Functional) with SYSTIME Computer Systems Ltd. SYSTIME (www.SYSTIME.net) is a leading global business provider delivering reliable, high-quality, cost-effective IT solutions and services. Nilesh has extensive experience in Business Analysis. He has a Bachelor's Degree in Engineering and is also pursuing his Master's in Business Administration. He has also been published earlier with International Institute of Business Analysis, a leading association in the world of business analysis, as well as in a previous issue of Project Times. In 2007, Nilesh represented his country as "The Youth Icon of India" in Brussels at the First CCS World Youth Forum in the European Parliament. Nilesh can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it..
Read 20671 times Last modified on Tuesday, 27 March 2012 12:46

Comments  

0 # wardah sana 2011-03-22 03:24
Requirements keep on changing then why sign-off?
Reply | Reply with quote | Quote
-1 # Rachana 2012-04-15 01:35
Hi Nilesh,

Thanks for such an informative article! How about an onsite co-ordinator/BA who acts as an mediator, what strategies this person should follow to achieve project goals? (I understand that some of the above strategies are applicable to onsite co-ordinator)

~Rachana
Reply | Reply with quote | Quote
-1 # Sujit Kulshresta 2012-08-13 22:54
Hello Nilesh,

Which customer scenario are you referring here? Is it some perfect customer who signs off requirement and concludes that there are no issues... Is it some NASA project or some missile construction company you are referring to? Come to some realistic terms and talk about these theory in reality.

How many customers you have worked which are perfect as per your story? I'd like to know your real life stories. Do write.

Sujit
Reply | Reply with quote | Quote
0 # Janet 2012-11-20 23:39
FYI ... is not Benjamin Franklin ... Winston Churchill during WWII
Reply | Reply with quote | Quote
0 # Sharma 2013-01-17 04:34
Lots of cliches here... poor article
Reply | Reply with quote | Quote

Add comment


Security code
Refresh