Project Based on Friend Relation

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.

I will meet my CEO today and i have plan to make my CEO understand with the fact and documents i have and i will ask him to decide what is more important friendship or benefit. But, i still not so sure he want to take the risk that my company suffer looses from this kind of project because for this small IT project, my client want to open the scope and requirements until the year of 2018 (this project is just less than 30 mandays)

But after all thanks for your suggestion, i really appreciate it and agree on you

- How to manage your relationship with the CEO, that is your friend? As I've written in one of my blog entries, friendship and colleagues sometimes it's not easy to manage, because usually, you'll lose the boundaries. Please feel free to check the blog entry. https://www.projectmanagement.com/blog-pos...or-Colleagues-- -- Very interesting topic that you write, thanks for sharing

- IT Project Size, this should not be an issue, as before was pointed by Anupam and Sergio. Big and Small depends on the company and organization, most important is apply correctly the project management principles. -- I agree

- As I've understood, the client is not happy, then, here is the real topic, and the point that you have to put all your efforts. What was the issue? Why isn't he happy? And remember...document the lessons learned for next project. -- Yes, of course i will document the lesson learned because i believe my company will take this kind of projects in the future since it is the nature of my company right now (i was new consultant here, so i just collect EEF and OPA of my company)

Good luck and keep us informed about the development of the situation. -- Thank you for your support, really appreciate it and i will update my situation after i meet my CEO today

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.

Sisca,

Good job with the CEO meetings. Remember to keep boundaries between both. Good luck with the client meeting.

Thank you for sharing,

I aware of the difference between low context and high context cultures, that's why in the next meeting i will less writing, and more concern about what the client "really need".

I really appreciate your support and input :)

Hi Muhammad, thank you for your notes, but only one comment, be careful with Wikipedia...sometimes information is not accurate.