{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:25:49Z","timestamp":1750307149515,"version":"3.41.0"},"reference-count":5,"publisher":"Association for Computing Machinery (ACM)","issue":"6","license":[{"start":{"date-parts":[[2011,11,14]],"date-time":"2011-11-14T00:00:00Z","timestamp":1321228800000},"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":[[2011,11,14]]},"abstract":"<jats:p>Time boxing is a management technique which prioritizes schedule over deliverables but time boxes which are merely a self, or an outside, imposed target without agreed partial outcomes and justified certainty are at best, an expression of good will on the part of the team. This essay proposes the use of a modified set of Moscow rules which accomplish the objectives of prioritizing deliverables and providing a degree of assurance as a function of the uncertainty of the underlying estimates.<\/jats:p>","DOI":"10.1145\/2047414.2047428","type":"journal-article","created":{"date-parts":[[2011,11,21]],"date-time":"2011-11-21T19:54:36Z","timestamp":1321905276000},"page":"1-5","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":7,"title":["Time boxing planning"],"prefix":"10.1145","volume":"36","author":[{"given":"Eduardo","family":"Miranda","sequence":"first","affiliation":[{"name":"Carnegie Mellon University"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2011,11,14]]},"reference":[{"doi-asserted-by":"publisher","key":"e_1_2_1_1_1","DOI":"10.1109\/2.989933"},{"unstructured":"Stapleton J. DSDM Business Focused Development 2nd ed. London Addison Wesley 2003   Stapleton J. DSDM Business Focused Development 2nd ed. London Addison Wesley 2003","key":"e_1_2_1_2_1"},{"unstructured":"Berander P Andrews A Requirements prioritization. Aurum Wohlin (Eds.) Engineering and Managing Software Requirements Berlin Springer Verlag 2005  Berander P Andrews A Requirements prioritization. Aurum Wohlin (Eds.) Engineering and Managing Software Requirements Berlin Springer Verlag 2005","key":"e_1_2_1_3_1"},{"doi-asserted-by":"publisher","key":"e_1_2_1_4_1","DOI":"10.1016\/j.infsof.2003.07.002"},{"doi-asserted-by":"publisher","key":"e_1_2_1_5_1","DOI":"10.1109\/52.589239"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2047414.2047428","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/2047414.2047428","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T09:54:13Z","timestamp":1750240453000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2047414.2047428"}},"subtitle":["buffered moscow rules"],"short-title":[],"issued":{"date-parts":[[2011,11,14]]},"references-count":5,"journal-issue":{"issue":"6","published-print":{"date-parts":[[2011,11,14]]}},"alternative-id":["10.1145\/2047414.2047428"],"URL":"https:\/\/doi.org\/10.1145\/2047414.2047428","relation":{},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2011,11,14]]},"assertion":[{"value":"2011-11-14","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}