![\"shiny](\"https:\/\/www.finditez.com\/blog\/wp-content\/uploads\/2016\/10\/shiny-objects.jpg\")
<\/p>\n
One of the biggest challenge with each of these classic mistakes is they often go unnoticed, potentially even rewarded or encouraged by project leaders and project managers … until it is too late and the damage is done.\u00a0\u00a0 But why and how does this happen so often in our industry?<\/p>\n
Lack of transparency.\u00a0 <\/strong>This comes down to one thing.\u00a0\u00a0 Communication<\/em>.\u00a0\u00a0 In over 25 years of experience, I have observed that this is often a skill that many software developers simply have to work on as it does not come naturally.\u00a0\u00a0 Most software engineers are logical, introspective thinkers and very much focused on getting right to work problem solving.\u00a0 Generally, people of action and few words.\u00a0\u00a0 The problem is, software developers often have a tendency to jump right in and start “doing” without sharing or vetting their ideas, or taking the time to research all viable options before starting to change code. \u00a0 Communication, and full transparency are critical for cost-effective design selection and productive development phases.<\/em> Over engineering.<\/strong>\u00a0 This is a personal pet peeve of mine because I have been burned so many times by this mistake, both as a developer and project manager!\u00a0 WAY TOO MUCH time can be spent on creating an elegant, clever, over-engineered solution, especially when a simple direct approach is available, can be a huge time waster … and is often very costly!<\/em><\/p>\n As problem solvers, we enjoy technical challenges and like to avoid having to revisit code by\u00a0 (over) engineering a solution trying to anticipate when end users will change their mind … um I mean requirements.\u00a0 But in doing so, we may fail to realize or consider the unnecessary cost and effort involved.\u00a0\u00a0 Don’t fix what aint broke, yet! <\/strong><\/em><\/p>\n Often, complex solutions that may be considered by the creator to be “brilliant” and “ultimately flexible” can be poorly documented and extremely difficult to understand or maintain.\u00a0 Worse still, after hours of attempting to make these over engineered solutions work, the effort can prove fruitless and abandoned as unfeasible.\u00a0 Use the KISS principle … Shiny objects.<\/strong>\u00a0 In a word, distractions<\/em>.\u00a0\u00a0 In a software project, this typically manifests itself in scope creep.\u00a0 This, however, is scope creep that originates from within the development team … “hey, let’s do this too while we are in here”, or “wouldn’t this be cool?” \u00a0 These suggestions can often be encouraged and accepted by the Project Lead or Manager as a client “bonus” … as it comes from an enthusiatic developer team member who swears they can do it without affecting the delivery timeline. \u00a0 The PM may also accept these to get buy-in from the developer and to avoid discouraging this type of proactive behaviour for team building.\u00a0 However, these types of side-tracks, often combined with lack of transparency, can be a project killer.\u00a0\u00a0 Stay on track, stay focused, don’t get tempted by shiny objects.<\/strong><\/em><\/p>\n Change impact analysis tools by FinditEZ provide a full 360 degree view of your entire code stack.\u00a0 Produce more accurate estimates, identify the right resource skillsets required, quickly run “what if” change impact cost scenarios to confidently select the most cost effective option.\u00a0\u00a0 Transparent, easily distributed change lists for clear and simple communication.\u00a0 Perfectly engineered solutions.\u00a0 Find-it-EZ – Software change made simple.<\/em> ™<\/p>\n","protected":false},"excerpt":{"rendered":" Inexperienced and\/or over-eager technology workers often unintentionally increase the risk of software project failures due to three common mistakes: Lack of transparency Over engineering…<\/p>\n","protected":false},"author":1,"featured_media":508,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,25,26,27,28,17],"tags":[],"class_list":["post-492","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-boost-software-developer-productivity","category-pro-desktop","category-pro-server","category-365-enterprise","category-365-ultimate","category-software-estimating"],"jetpack_featured_media_url":"https:\/\/www.finditeasy.com\/blog\/wp-content\/uploads\/2016\/10\/shiny-objects.jpg","_links":{"self":[{"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/posts\/492","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/comments?post=492"}],"version-history":[{"count":0,"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/posts\/492\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/media\/508"}],"wp:attachment":[{"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/media?parent=492"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/categories?post=492"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.finditeasy.com\/blog\/wp-json\/wp\/v2\/tags?post=492"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n<\/strong><\/p>\n
\n<\/strong><\/em><\/p>\n![\"keep](\"https:\/\/www.finditez.com\/blog\/wp-content\/uploads\/2016\/10\/kiss-albert-einstein.jpg\")
<\/p>\n