{"id":38308,"date":"2016-11-08T10:14:00","date_gmt":"2016-11-08T16:14:00","guid":{"rendered":"https:\/\/kenscourses.com\/tc1019fall2016\/?guid=97e0487b663fce08bf1cb10471257fe6"},"modified":"2016-11-08T10:14:33","modified_gmt":"2016-11-08T16:14:33","slug":"implementing-software-3","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/implementing-software-3\/","title":{"rendered":"Implementing Software"},"content":{"rendered":"
Well, just implement it! Right?<\/span><\/span><\/div>
Title might seem too self explanatory (I thought that too), but no. Not necessarily. There\u2019s more to this than what you might assume by just knowing what it\u2019s called.<\/span><\/div>

<\/div>
<\/span><\/div>
image obtained from <\/span>http:\/\/www.bugbash.net\/archives\/comic\/2005\/07\/the-high-level-view.html<\/span><\/a><\/div>

<\/div>
For what I\u2019ve come to learn, correct me if I\u2019m wrong, when you talk about software implementation you\u2019re talking about the challenges a development team faces when implementing software. This, in terms of making the team work as one and that all code seems to have been written by the same person. This makes it a whole easier to understand what another member of your team is doing, how you can contribute, and measure the overall progress of your team because you all basically have the same way of organizing yourselves.<\/span><\/div>
Let me go deeper into this\u2026<\/span><\/div>

<\/div>
These challenges I mentioned before are among these classifications:<\/span><\/div>