Wednesday, 28 July 2010
In these first two exercises we will explore the importance of knowing your key end-users and why you need to enlist their help. We will also look at the start of gathering requirements and how crucial that is in the process of making a decision as to whether 'To Build or Buy'.
1. Are you going to be a key end-user of the new application? If yes, great! Please carry on. If no, if you're not sure, or if you are only one of a handful or more of key end-users, you will need to consider who may be involved. Enlist their help sooner rather than later in the requirements gathering process starting in Exercise 2. Not to do so could mean your investigation is already on shaky ground and here's why....
The Importance of Different Perspectives
Get other key people on board as soon as possible and consider enlisting the help of a software development Business Analyst (BA) or Certified Project Manager (CPM).
2. As a key end-user, can you list the purpose, objectives and key functions of the application including how it will act (features) and how it will look (user interface or UI)? Whether you use an electronic spreadsheet and list features with their associated actions, or draw pictures on loose leaf representing what happens when you click a particular button - if you can do this for your entire application, you are doing amazingly well! Carry on.
Start with Independent Requirements Gathering
The Cost of Re-work
Have you been through a simple or complex requirements gathering process? How did it work for you? Our readers would love to hear your experiences and insights!
1SSQ Staff, Software Quality News, Beating the odds: Managing a successful software project:
Tuesday, 27 July 2010
Have you ever struggled with this age-old I.T. question: whether to build a custom software application or to buy one off the shelf? This blog series was motivated by my recent conversations with both current and prospective customers and it really hit me - we are all facing this issue more and more often as we increasingly rely on technology to enhance productivity, to connect our computer and web-based applications, and to work smarter overall.
As we are driven 'to do more with less', our new productivity tools need to be effective, and we need to have done our due diligence investigating all the options, otherwise, we may end up duplicating our work effort down the road, having spent valuable time and resources on a solution that is simply not viable - and no one can afford that.
My aim with this blog series is to provide food for thought for anyone, in any position or industry, seeking a software solution to improve productivity. I have referenced the articles and tools where I utilized them, should you desire to dig deeper than I have. Please note, we neither endorse nor profit from any recommendations made.
These exercises will require some investment on your part, but doing some homework now could save you a bundle of time, money and effort (not to mention aspirin and antacids) in the long run.
In this blog series I will cover exercises on the topics below, so check back tomorrow for the first 2 Exercises to get you started on whether 'To Build or Buy'.