Nandkishor KhidkikarProject Manager Engr/Technical Manager Currently Seeking New Opportunities| CSSGB & Applied Project Management at University of California Irvine GPA 4.0Norwalk, Ca, United States
Project deadlines are important but project quality is also equally important. Delivering a quality project meeting deadline is a challenge. I havd observed that the goal is achieved by compromising between the two. I would like to know your thoughts and ideas on this issue. Saving Changes...
Rajeev SharmaPrincipal Consultant | Strategy, EA CoE | Digital Transformation, AI and Gen-AI| Tech MahindraGurgaon, Haryana, India
Agree with all others quality first, follows deadline mitigation - could have other alternatives (project 2 project) instead of quality compromise ! Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The problem in that type of situations is organizations do not understand Three principal things: 1-the concept of quality and grade. 2-quality is a strategic matter to be defined at strategic level. 3-when shortest the time of delivery the higher the quality you need to achieve that. With all these on hand let me say: quality is never compromised because there is no definition of quality (and grade) then there is nothing to compromise. Is a misunderstanding when some people said "we are compromising quality to deliver faster". When you ask "ok, what is your definition of quality? which is what you are compromising?" you will find there are not answers. Or, at least, answers does not match with quality and grade definitions. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Quality is certainly a significant factor, though there may be a defined level of acceptable quality - requirements vs. non-requirements.
For example; The task is to build an input screen with 4 fields, submit and cancel button. The resultant functionally works, but the submit button actually says complete. The acceptance tests passes, but a defect is opened for the wrong text.
That said, purposefully reducing quality for speed is not acceptable. The root cause is back to poor planning somewhere. Saving Changes...
Suleander ZahnCo-organizer & Facilitator| Agile ConnectPorto, Porto, Portugal
Hi Nandkishor,
It reminds me the tale of the 3 constraints: "We have 3 ways of delivering your project (1 - Fast; 2 - High quality; and 3 - Low cost), but you can only combine 2 of them... Let game begin.
1 - Fast + High Quality = won't be low cost
2 - Fast + Low Cost = won't have quality
3 - High Quality + Low Cost = won't arrive fast
It is true that in real life we are always struggling to have the 3 options combined, and it is possible indeed. However, it requires huge efforts from all parts involved (PM, team, Sponsors and Clients) to dig deep down into the problem and reach out the most adequate solution.
Sometimes the client want it fast but it doesn't really need to have all the functionalities. So we can launch a first version quickly and them improve it. Other times the "deadline" doesn't mean death at all, so if we have a delay but deliver something with superior quality, the problem will be solved.
In both cases, "collaboration" between parts is the key to success. Saving Changes...
The iteration process is the most critical process prior to finalising project management plan in Planning Process Group which include schedule & quality definition. "Final" project deadline is agreed upon with mutually consented quality definition and acceptance criteria between Seller & Buyer. As such, negligence or failure to meet project deadline at the expenses of quality is nonsense. Under special circumstance (while other factors being constant), unless CR is approved to revise quality definition for improvement, enhancement or rectification, project deadline should not be altered at the expenses of quality originally defined in Contract.
Schedule compression method or implementing contingency reserve of schedule should be considered instead to meet project deadline. I wish to share beautiful quote on quality below:
Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.”...... Willa A Foster
PUI Saving Changes...
Tony DoanIT Project Manager| Cadillac FairviewScarborough, Ontario, Canada
I'd refer back to the triple constraints model. Sure we all want to deliver quality projects but at what cost to the company? What if providing a quality project meant excessive costs for missing deadlines. My point is the answer isn't so straight forward and easy as picking one over the other.
If I was in such predicament, I would layout the options (using the triple constraints model) to the project owner, provide my recommendation and then let them decide what they believe is the best course of action. Saving Changes...
