Handling Missed Requirement
As the deliverable arrives, we were able finally to test it out after the long await. Unfortunately, we found out that a side functionality was only using at the address instead of both the account & address.
After talking to the consultant, we found out they were surprised that we were expecting to include the account key … It was a completely missed.
The miscommunication started from requirement definition due to the complexity of various scenarios. Although when the specification/design document arrived, all of the business & IT staff reviewed it & still missed the scenario … when we reviewed the document, we missed what was not in the design on the particular scenario.
Honestly in general, the code was correct expect for that missed item … so this missed requirement will be seperately managed by a change request.
As much we try to prevent it, miscommunication/misunderstanding/mistakes happen. We need to accept it, fix it & move forward.
Here are the process I followed this time to reduce any potential further delays:
1. Acknowledge the Problem (Don’t Blame):
If a process was miscommunicated or misunderstood, the issue will trickle down into the work that is being done. It could have been caused by client miscommunication, vendor misunderstandings OR both.
It doesn’t matter anymore, it happened … state what was missed & move forward.
2. Analyze the Impact:
This will also become your justification for the extra time it took for the fix. For my current issue, the impact would of cause a good set of end-customer not receiving a rebate/refund … due to the monetary impact to the bunch of future customers … this would be set as a priority issue.
3. Re-Determine the Specification/Conditions/Scenarios:
For example, the issue we found was big enough, but after redefining the conditions.
We find we only need to update one of the key condition to include the account #, instead of just the address to solve the issue/gap
4. Collaborate on Solution:
Oh, please write it down as well.
5. Document it:
At this point, unless you want to hide the issue … just document it or setup a change request. Misunderstanding & Mistakes happen, just make the fix official (if needed, get it approved).
6. Let the Vendor Handle it:
Although makes sure you make it clear to the vendor that question & feedback are welcome … this way you will get what you need & confusion is minimized … also it will cut down on time to redevelop it again.
As discuss in the
I don’t know about you, ideas & solution come to me everyday, but it seems hard to implement any of those ideas. Which is why i’m learning project management.
As I dig through my old e-mail & to-do last friday, I stayed behind again to close out some of the pending task that got lost in priorities for the week.


This week I personally had 2 good days & a bad day. I noticed the difference in results I was able to deliver between it.
From my previous post on 
Like all soft skills, project management can’t just be learnt on an manual. It must be nurtured through experience to gain the skill sets.
Even though IT is more technical than most departments, we still need to work well with others. There are a lot of soft skills required to be the best person for the job. Here are some that I found useful: