June 25, 2009 10:00 AM
Posted by: Jaideep Khanduja
offloading,
project management,
project outsourcing,
Software Project,
stakeholder,
third partyOutsourcing is neither bad nor good. It is a strategic decision based on certain parameters taken by an organization to offload some projects or part of a project to a third party. Offloading certainly comes with many boons and many banes. Offloading should be managed very carefully as the project...
June 22, 2009 10:00 AM
Posted by: Jaideep Khanduja
build phase,
project management,
project manager,
project phase,
project quality,
project team,
project walkthrough,
quality,
Software Project,
stakeholder,
User ManualAs already has been discussed, User Manuals play a crucial role in any software project and are the solid bonding between product, users, customer management and vendor project team. The stronger this bond is the more comfortable and happy each stakeholder will be. Each player has to play a crucial...
June 19, 2009 10:00 AM
Posted by: Jaideep Khanduja
FAQ,
project management,
quality,
Software Project,
User Management,
User ManualSix major key points that should be kept in mind while preparing User Manuals can be as listed below:
1. Simple – Never expect your product users to be as knowledgeable about your product as you are. Remember when you first time tried working on this product, how ignorant or untrained you...
June 17, 2009 10:00 AM
Posted by: Jaideep Khanduja
analytic,
business scenario,
durability,
feel and look,
implementation team,
key user,
live run,
post implementation,
product support,
product training,
project implementation,
project sign-off,
project support,
project team,
reliability,
report,
sign-off,
Software Project,
software project management,
software training,
stability,
stakeholder,
training team,
usability,
user feedback,
User ManualThe product owners or stakeholders might be many in a software project, but the real frontrunners who drive, run and use the software product post implementation are the key users and other users. It is their feedback that matters most. They must be the most comfortable lot on usability,...
June 15, 2009 10:00 AM
Posted by: Jaideep Khanduja
change management,
employee engagement,
Employee retention,
employee satisfaction,
opportunity to grow,
project management,
resistance to change,
Software Project
+ Do
X Don’t
+ Single constant in business is Change
X Single constant in business is resistance to change
+ Change means shifting to a better comfort zone
X Change means shifting away from comfort zone
+ Recruit well in advance before the project start time
X ...
June 12, 2009 10:00 AM
Posted by: Jaideep Khanduja
project management,
project manager,
project performance,
software development,
Software Project,
software quality10. When you start getting increased number of bugs as compared to earlier releases
9. When your developers stop thinking about quality in code
8. When bugs pass through QC unnoticed
7. When you stop acknowledging quality efforts and start giving more importance to speed and volume of...
June 10, 2009 10:00 AM
Posted by: Jaideep Khanduja
business analysis,
business analyst,
business requirement study,
change management,
developer,
implementation phase,
implementer,
key user,
project director,
project management,
project manager,
project organization,
project phase,
project sponsor,
requirement analysis,
requirement gathering,
Software Project,
technical leadIn the previous post we learnt what all could a software project could lead to in presence of higher scope of software development at customer site during implementation phase. Let us see what all factors are responsible of insufficient requirement gathering during business study phase of a...
June 8, 2009 10:00 AM
Posted by: Jaideep Khanduja
functional lead,
on-site development,
project completion,
project delay,
project implementation,
project management,
project organization,
project quality,
project team,
QC,
quality,
software development,
software implementation,
Software Project,
software quality,
technical lead,
tester,
testingIdeally, in a software project, for an offshore customer, the requirement gathering phase should be given an extra care to understand to a maximum extent so that the product developed and tested when ready for implementation at customer site requires no development. Practically, it is very...
June 5, 2009 10:00 AM
Posted by: Jaideep Khanduja
post implementation review,
project management,
Software ProjectThe Post implementation review is usually filled collectively by customer project team and signed by the project sponsor, who is usually one of the senior members of management. This form is to be submitted back to vendor (after filling) to serve the purpose of – sharing experience, product...
June 3, 2009 10:00 AM
Posted by: Jaideep Khanduja
post implementation review,
project closure,
project completion,
project feedback,
project management,
project manager,
project sign-off,
software implementation,
Software ProjectBoth vendor and customer have to understand that the real journey of a product starts only after a successful implementation of software at customer site. The challenges get a new meaning once the project team leaves the customer site after project sign-off. Both the managements can celebrate the...
June 1, 2009 9:00 AM
Posted by: Jaideep Khanduja
key user management,
post implementation review,
product acceptance,
product building,
product development,
product friendliness,
product maturity,
product usefulness,
project effectiveness,
project implementation process,
project requirements,
Risk Management,
risk perception,
software business,
software implementation,
Software Project,
software project management,
team managementWhat is post implementation review? When it should be done? Why is it required? All this has been discussed in last three posts. Let us now understand what ideally would be the components of a post implementation review. As discussed earlier, some components can be answered immediately at the...
