{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:43:53Z","timestamp":1750308233130,"version":"3.41.0"},"reference-count":0,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[1984,7,1]],"date-time":"1984-07-01T00:00:00Z","timestamp":457488000000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[1984,7]]},"abstract":"<jats:p>\n            Once upon a time I thought there was a fixed amount of energy that a development team could put on a project in any given period of time, and I simply had to allocate that to productive and non-productive tasks. Woe and behold, Dick Orgass corrected me. He noted that projects which write large papers about their design get far less done than ones which keep their non-productive tasks under stricter control, even with the same amount of resources.This is a paper about\n            <jats:italic>why<\/jats:italic>\n            .\n          <\/jats:p>","DOI":"10.1145\/1012339.1012343","type":"journal-article","created":{"date-parts":[[2004,10,7]],"date-time":"2004-10-07T17:39:09Z","timestamp":1097170749000},"page":"58-60","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["My accordian's stuffed full of paper"],"prefix":"10.1145","volume":"9","author":[{"given":"Dave","family":"Brown","sequence":"first","affiliation":[{"name":"Alternatives Ltd., Toronto, Ontario Canada"}]}],"member":"320","published-online":{"date-parts":[[1984,7]]},"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1012339.1012343","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1012339.1012343","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T16:31:42Z","timestamp":1750264302000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1012339.1012343"}},"subtitle":["or why we did so badly in the design phase"],"short-title":[],"issued":{"date-parts":[[1984,7]]},"references-count":0,"journal-issue":{"issue":"4","published-print":{"date-parts":[[1984,7]]}},"alternative-id":["10.1145\/1012339.1012343"],"URL":"https:\/\/doi.org\/10.1145\/1012339.1012343","relation":{},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[1984,7]]},"assertion":[{"value":"1984-07-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}