Visits ...

Wednesday, January 16, 2013

Requirement, user and developer ....


Irrespective to the improvement of software or hardware, what is crucial is and is to understand is, the challenge that need to understand to users, in terms of their requirement, what is currently receiving and what they expect more.
Software Development Life Cycle, in what ever application may be is the core basis for functionality any IT  Company. Outsourcing is an important part for the industry and heavy tendency in resorting to outsourcing significantly, complexity of the said process increases and naturally risk factor also goes up. Given the circumstances, developing an application outsourced, raise the importance of the Requirements, its gathering and design and not fall in not meeting user expectations when it is too late.
The most critical change, however, is the participation of a more sophisticated and unknown user: the consumer. He or she not necessarily be the front face of the organisation but an individual who will be the owner of the system, thus makes him the most unusual individual: he/she does not participate as part of an internal organization, or external client, rather a transactional force at the beginning and later the owners that comes in and out of the application with an enormous amount of uncertainty and constant change in behaviors and needs. Organisations rely on these individuals in determining the viability of the system to proceed with.
It is imperative that we expand analysis and design through SMART requirements in to provide developers from inside and outside the business to clearly understand what is needed thus enabling them to deliver the required.
Applications need to change more often, so that object-based design is no longer an alternative, rather a necessity to allow organizations to continually evolve and mature their abilities to serve their clientele.

Wednesday, January 2, 2013

Sealing the deal!

Every project has different stake holders. it is difficult to find projects which has single stake holder you can count on.
success of a project lies on the implementation to its fullest, which is basically fulfilling the needs of all the users who are going to use it.
we may not be able to fulfill and as a matter of fact we may not be able to figure out all the users as well.
but every project is run by set of users, we could easily categorize them effective users, whom are front faces    of the project. getting their acceptance is naturally considered as the final.
The lesson will be learnt, if we lean into a set of users and do not cater needs of another sufficiently. Now you may put your faith on your favorite users, but when comes to official stamping off the project, users will be looking for much more than the favoritism shown to them.
So the rule is identify your effective users and make sure testing is done by all those users and their signatures are collected as evidence.