{"id":19382,"date":"2017-04-14T11:28:01","date_gmt":"2017-04-14T11:28:01","guid":{"rendered":"http:\/\/www.challengedetroit.org\/?p=19382"},"modified":"2017-04-14T11:28:01","modified_gmt":"2017-04-14T11:28:01","slug":"reality-scope-creep-vitality-persistence","status":"publish","type":"post","link":"https:\/\/www.challengedetroit.org\/blog\/reality-scope-creep-vitality-persistence\/","title":{"rendered":"The Reality of Scope Creep and the Vitality of Persistence"},"content":{"rendered":"

Scope creep (also called requirement creep, function creep and feature creep) in project management refers to changes, continuous or uncontrolled growth in a project’s scope, at any point after the project commences. This can occur when the scope of a project is not properly defined, documented, or controlled. (per https:\/\/en.wikipedia.org\/wiki\/Scope_creep)<\/p>\n

Currently at the mid-point of our year as Challenge Detroit Fellows, one of the most vital lessons one will learn is the importance of avoiding scope creep. \u00a0When using human-centered design thinking, especially when faced with a fairly short time frame of which to work and produce a feasible prototype, one must carefully examine the the intersection of resources vs. time. \u00a0In addition, one must examine closely the answers received from empathy and engagement sessions and how this drives the the underlying design question proposed. “How might we… accomplish what we set out to do… most effectively in x<\/em> weeks?” \u00a0This perhaps maybe the question we area really asking ourselves at the core of most design questions, especially wherein we are looking to avoid scope creep.<\/p>\n

\"\"<\/p>\n

For the year, thus far, we have worked in teams on a total of four challenge projects now. \u00a0With one final challenge and a culminating Impact Partner Project<\/em> in the works, we have had time to refine our processes and approach when it comes to human-centered design thinking. Perhaps not ‘experts’ per say, but we have become quite familiar and far more effective, I think, in our understanding and approach to how human centered design applies to community development work. For instance, from my experiences so far, I have learned that you cannot always plan to have the most engaging stakeholders when doing empathy and outreach. \u00a0I have also learned that sometimes the ideation piece comes early, before empathy is complete, while other times the prototype may have fairly definitive aspects apparent before one even fully realizes what that prototype actually is.<\/p>\n

In all, the unforeseen should be embraced, and the only pertinent ingredient one must fully come to terms with becoming most comfortable with is the idea of persistence. \u00a0In community development, a design thinker must be persistent in communication, empathy, research, follow through, and refinement of ideas. \u00a0It is this persistence that allows one to see challenges through and develop truly useful models for solutions to design problems. \u00a0When the going gets tough, the tough continues to ideate, refine and design!<\/p>\n","protected":false},"excerpt":{"rendered":"

Scope creep (also called requirement creep, function creep and feature creep) in project management refers to changes, continuous or uncontrolled growth in a project’s scope, at any point after the project commences. This can occur when the scope of a project is not properly defined, documented, or controlled. (per https:\/\/en.wikipedia.org\/wiki\/Scope_creep) Currently at the mid-point of […]<\/p>\n","protected":false},"author":100,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,15,1],"tags":[586],"class_list":["post-19382","post","type-post","status-publish","format-standard","hentry","category-givedetroit","category-leaddetroit","category-uncategorized","tag-humancentered-designdetroit-scopecreep-persistence"],"_links":{"self":[{"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/posts\/19382","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/users\/100"}],"replies":[{"embeddable":true,"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/comments?post=19382"}],"version-history":[{"count":0,"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/posts\/19382\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/media?parent=19382"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/categories?post=19382"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.challengedetroit.org\/blog\/wp-json\/wp\/v2\/tags?post=19382"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}