Summary: In project management, a death march is a project where the members feel it is destined to fail, or requires a stretch of unsustainable overwork. The general feel of the project reflects that of an actual death march because the members of the project are forced to continue the project by their superiors against their better judgment. ~Wikipedia Will and BJ discuss the troubles and tribulations of the death march. They are typically characterized by heavy turnover, burnout, and timelines that are too aggressive to actually meet. Death marches usually come about though poor management or a disconnect between developers and other departments like sales. Rapid growth may also lead to a death march. Growth of the team or growth of the company if it is a startup. It is best to avoid working for companies or projects that have death march potential. To do this ask upfront what the expectations are regarding hours, overtime, and comp time during the interview. Remember you are choosing the company as much as they are choosing you. Links <a href="http://iotworldnews.com/2015/11/beecham-research-slams-pie-in-the-sky-predictions-for-iot/" target="_blank">IoT is Over-hyped</a> <a href="https://en.wikipedia.org/wiki/Death_march_(project_management)" target="_blank">Wikipedia Definition</a> <a href="http://death-march.urbanup.com/2740314" target="_blank">Urban Dictionary</a> <a href="http://www.portableapps.com">Portable Apps</a> Special Note Excerpt of The Imperial March (Darth Vader's Theme) by John Williams used in the discussion about the Episode VII was taken from <a href="https://www.amazon.com/gp/product/B004EYRIBC?ie=UTF8&keywords=starwars%20soundtrack&qid=1449629135&ref_=sr_1_4&sr=8-4" target="_blank">The Music Of Star Wars: 30th Anniversary Collector's Edition</a> .
