Quality Assurance and Project Management:

software implementation

1

April 21, 2010  7:18 AM

Software Development Project and Rework



Posted by: Jaideep Khanduja
business analyst, Project Development, project implementation, project management, project requirement, project rework, project team, requirement analysis, requirement study, software development, software implementation, Software Project, software requirement, software rework

As per study software development team on an average spends almost 40% of their time on rework. The rework requirements may arise by way of – development team revisiting their code and finding out some lacunae; Quality control test/ bug report; or requirements fine tuning at customer end during...

October 12, 2009  10:00 AM

What customer type you are?



Posted by: Jaideep Khanduja
business requirement, change management, code, customer requirement, software, software implementation, software product, Software Project

One customer type focuses on current requirement, rightly built, with more flexibility towards the business requirements built-in in the database rather than in the code. They believe that if the software meets their current requirements well, the future requirements will be built in at the need of...


July 15, 2009  10:00 AM

Who owns the Q-Tag in a software development company?



Posted by: Jaideep Khanduja
Bug, bugs report, business analyst, development team, implementation team, product approval, project implementation, project management, project management framework, project methodology, project team, Q-tag, QA, QC, quality assurance, quality control, Quality-tag, re-testing, software build, software implementation, Software Project, stakeholder, team, test report, testing, testing team

In any software development and implementation company there is always a need of quality assurance and quality control people who own the responsibility of setting the right methodology and framework for development and implementation (QA), bugs identification and product approval (QC). Usually...


June 8, 2009  10:00 AM

Five pitfalls if you are leaving a scope of software development at customer site



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, quality assurance, quality control, software development, software implementation, Software Project, software quality, technical lead, tester, testing

Ideally, 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 3, 2009  10:00 AM

How to prepare for Post Project Implementation Review?



Posted by: Jaideep Khanduja
post implementation review, project closure, project completion, project feedback, project management, project manager, project sign-off, software implementation, Software Project

Both 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

Ten Components of a post implementation review



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 management

What 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...


May 29, 2009  10:00 AM

Post Implementation Review – When, ldeally?



Posted by: Jaideep Khanduja
post implementation, post implementation review, product performance, project acceptance, project board, project closure, project management, project sign-off, software implementation, software performance, Software Project

When is to perform a post implementation review? A witty answer could be – obviously after implementation. Ha! Definitely a successful closure of implementation could declare a project closure with a formal project acceptance report or project sign off. So shall we have a post implementation...


May 11, 2009  10:12 AM

Two aspects in Change Management in Software Project



Posted by: Jaideep Khanduja
business critical change, business requirements, Business Rules, business study, change management, customer management, customer requirements, project cycle, Project Development, project implementation, project management, project manager, project team, software development, software implementation, Software Project, software requirements

Change management is a subset of project management. In any software project change is to be managed during the whole cycle of development and implementation. Requirements once specified by customer at the business requirements study phase does not mean that there will be no change in requirements...


April 27, 2009  10:06 AM

Project Overrun – what is crucial – time, money or both?



Posted by: Jaideep Khanduja
domestic project, overseas project, project implementation, project management, project manager, project monitoring, project organization, project overrun, Project Plan, Project Planning, software implementation, Software Project

A classic scenario happened in an organization recently as told to me by a project manager of that organization engaged in software development and implementations. It is related to project overrun. A new project started with a set of requirements from a customer for development and...


April 17, 2009  10:03 AM

Role of vendor project manager at customer site during implementation stage



Posted by: Jaideep Khanduja
implementation plan, project implementation, project lead, project management, project manager, project team, Risk Management, Risk Plan, software implementation

The vendor project manager has to work as a consultant to the customer project manager rather than taking the full command at customer site during implementation phase. From vendor side, it is the responsibility of the project manager to highlight the risks (in terms of user’s availability,...


April 16, 2009  9:40 AM

Responsibilities of project manager during project implementation phase



Posted by: Jaideep Khanduja
implementation plan, project closure, project lead, project management, project manager, project team, software acceptance, software implementation, Software Project

Project managers (the customer end and the vendor end) have to work hand in hand during the implementation stage of a software project happening at customer site. The key responsibility of both the project managers working on the project is to ensure successful implementation and project...


April 13, 2009  10:01 AM

Project Manager’s vision has to be perfect 6/6 for project implementation



Posted by: Jaideep Khanduja
project implementation, Project Lifecycle, project management, project manager, software development, software implementation, Software Project, software testing

No project manager can claim there was not a single problem in any of his projects. But then he is to tackle them. To tackle them he should be aware of them. To be aware of them, he has to have an ability to foresee them than to overlook them. The earlier he envisages those problems, the more time...


April 10, 2009  9:59 AM

Application developed, tested and built well does not ensure successful implementation



Posted by: Jaideep Khanduja
Application development, application implementation, application readiness, post implementation, project director, project management, project manager, project sponsor, project vision, software development, software implementation, software project manager, software testing, stakeholder, successful implementation

It is not only the project manager but all stakeholders who get affected by the project over-run or failure. It could happen due to any reasons. One of the major reasons that have emerged is the lack of vision of the project manager, project sponsors, project directors and other stakeholders to...


March 9, 2009  10:28 AM

20 points for organizational self evaluation to check where it stands in Software Project Management



Posted by: Jaideep Khanduja
1. organizational self evaluation, Code repository, continuous improvement, customer expectations, customer feedback, customer request, empowerment, innovation process, off-site project, on-site project, organizational goals, post implementation, process integration, product release, project implementation, project management evaluation checklist, Project Management Methodology, project manager, project metrics, project overrun, project team, Risk analysis, Risk Plan, roles and responsibilities, software bug, software development, software implementation, software project management, software testing, test case repository

  • 1. Does a formal Project Management Methodology exist in your organization? 2. Are you using some metrics to check if this is the right methodology? 3. What is the degree of improvement required in your current methodology to meet your customer expectations? 4. What are your...


  • November 26, 2008  10:11 AM

    New Release for testing – a tester’s paradigm



    Posted by: Jaideep Khanduja
    Bug, quality assurance, software, software implementation, software qa, software quality, software quality assurance, software release, software requirement, Software testers, software testing, software testing tips, softwaretesting, tester

    A new software release for testing could be a new product or major changes in the existing software. In either case the bugs report should have a new version number for control purposes. Although in case of a new release of existing software, the existing bugs can be referred to but that does not...


    November 14, 2008  10:30 AM

    SDLC-IV: Software implementation/coding



    Posted by: Jaideep Khanduja
    SDLC, software, software coding, software implementation

    Based on software requirements, business process, business rules, software design and customer specifications, the software coding begins. Project manager distributes the coding among the development team members with clear time frame instructions. Coding will begin in two manners – phased or...


    1

    Forgot Password

    No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

    Your password has been sent to: