Project Based on Friend Relation

Agile

Sisca Yuliharyani Sr. PM Consultant | Chief Strategy Officer| Indonesia Bandung, West Java, Indonesia

I assigned to manage small IT project, which is i did not have any experience for small IT project that held based on friend relation (not professional relationship). I try to apply my knowledge as PM of large IT project but in the end the client was not happy because i apply my knowledge as PM like i did in large IT Project. My development team were very grateful on how i manage that project because i make the plan and requirements clear but the client try to gain benefit with disagreeing in the feature that agreed before. Actually i have a lot of prove that what i did was true because i always speak with data and documentation. my question is how to make my CEO understand that the client is the people who was not sure what he want (the client is close friend of my CEO) and not my team's fault that the client was not happy?

Posted: Jan 4, 2017 4:36 AM

Sort By:

< 1 2 3 >

Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States

This is not a rare phenomenon. Based on my understanding of your situation, you could not have done much different. I tend to create a parking lot list of features for the 'next phase', recommending and explaining to the customer, based on experience, that it is natural to fine tune as you go along, but to focus on the core framework of the product, ensuring scalability, allowing for the refinements to come from the user base. Striving for the perfect product will be an endless exercise. Many times there is the conversation with the customer to remind them of the original goals and intent of the project, and what the original vision of the product was, the original problem and solution statement.

Its a partnership. Put their trust in you that your focus is to get them where they need to be. You are there to assist them through the 'jungle' to get to the beach :)

Good Luck!

Posted: Feb 17, 2017 6:13 AM

Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina

Jan 04, 2017 7:17 PM

Replying to Sisca Yuliharyani

...

First of all, is not a matter of large or small projects -- i agree, that's why i apply my knowledge like i always did in large IT Projects.

The Matter is firstly i can't "lock" the requirements no matter i try to use kinds of documentation (the client agree before and even sign the document), but in the next meeting, he will ask the different. So, i apply my knowledge and technique to prevent that behavior/risk will exist again, and i thought i was success on locking the scope, because he said that my product (software) is very satisfying and he accept all the feature. When my company wants to invoice his company, he ask to meet my CEO and told to my CEO that he was not sure he need that software because i lock the requirements which he was not sure he need that kind of feature.

Once again, is a matter of process. If your CEO agree with your client comments about the requirements then she/he has "to pay" for that. The only way to "lock" requirements is to have a project change control process in place where you and your team are accountable to create all the information needed and give it to the group that will decide on the change. If your CEO is in the group then she/he will decide. And you have to execute the change. Change are always wecome. But somebody must paid for that. And to pay does not mean money only.

Posted: Feb 17, 2017 7:18 AM (Updated by author: Feb 17, 2017 7:18 AM)

< 1 2 3 >

Please login or join to reply

Project Based on Friend Relation

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters