This is the fourth post in a series about hidden project changes: things that affect scope but are easily overlooked. The topic for this post is third party APIs.
You often have to rely on third parties to finish a project. Having a dependency on third party code is a big commitment though, and you should consider it carefully.
If you have no choice but to use a certain API (perhaps it is a requirement by the customer or the only one available) reviewing it is especially important to provide accurate time estimates and properly analyze associated risks.
