{"id":32,"date":"2006-03-08T13:16:12","date_gmt":"2006-03-08T20:16:12","guid":{"rendered":"http:\/\/www.redmonk.com\/cote\/wp\/?p=32"},"modified":"2006-03-08T13:16:12","modified_gmt":"2006-03-08T20:16:12","slug":"scrum-and-ajax","status":"publish","type":"post","link":"https:\/\/redmonk.com\/cote\/2006\/03\/08\/scrum-and-ajax\/","title":{"rendered":"Scrum and AJAX"},"content":{"rendered":"<p>In writing up a longer post about continuing <a href=\"http:\/\/www.redmonk.com\/cote\/archives\/2006\/03\/notes_on_enterp.html\">the Enterprise Agile conversation<\/a>, I recalled an idea I had during an AJAX component company (eBusiness Applications) briefing a few days ago: <a href=\"http:\/\/www.mountaingoatsoftware.com\/scrum\/sprintbacklog.php\">the Scrum backlog<\/a> is a <i>perfect<\/i> application of a web bases spreadsheet.<\/p>\n<h2>Backlog?<\/h2>\n<p>A backlog, in Scrum, is just a list of things (coding and otherwise) left to do on a project, ranked with rough estimates of how much time is left for each. The reasons to keep a backlog are: (1.) knowing what to do, (2.) knowing what order to do things in, (3.) knowing how much time is left. It&#8217;s from the 3rd that you get the most valuable artifact that Scrum (and other Agile implementations) have to offer: <a href=\"http:\/\/alistair.cockburn.us\/crystal\/articles\/evabc\/earnedvalueandburncharts.htm\">the burn down chart<\/a>. (I&#8217;m gettin&#8217; so excited thinking about it that I&#8217;ve got to stop myself before I twist this post into more Agile talk ;&gt;)<\/p>\n<p>Whole companies have been built around creating a web application out of that spreadsheet. Those companies, <i>of course<\/i>, layer a much more on top of the spreadsheet. Nonetheless, 80% of the Agile teams out there <i>could<\/i> (if they took <a href=\"http:\/\/www.amazon.com\/gp\/product\/0321150783\/\">the lean knife<\/a> to their process) function with just the spreadsheet&#8230;or even a well maintained sheet of butcher paper. (See, what&#8217;d I tell you about getting all excited?)<\/p>\n<h2>The AJAX Scrum Backlog<\/h2>\n<p>Companies like <a href=\"http:\/\/tracker.jot.com\/\">JotSpot<\/a> and <a href=\"http:\/\/developer.ebusiness-apps.com\/technologies\/webdevelopment\/codeandcomponents\/ebagrid\/default.htm\">eBusiness Applications<\/a> have AJAX spreadsheets that would be perfect for implementing the Scrum backlog. One of the major benefits of moving applications like word processors and spreadsheets online is adding easier to use collaborative features, like tracking revision diffs and who edited what. More importantly, it&#8217;s multiuser out of the box: you don&#8217;t have to email around or file share .doc or .xls files, you just go to a URL.<\/p>\n<p>So, I&#8217;m hoping we&#8217;ll see one of the AJAX spreadsheeters take that on: it&#8217;d be a great freebie to give away in a <a href=\"http:\/\/www.redmonk.com\/sogrady\/archives\/000985.html\">bottom up marketing campaign<\/a>. Developers and dev managers would use the backlog spreadsheet, and those two are the ones who would buy the AJAX components and AJAX services.<\/p>\n<p><b>Disclaimer:<\/b> while eBusiness Applications isn&#8217;t a client, they did have <a href=\"http:\/\/blogs.ebusiness-apps.com\/dave\/?p=103\">some kind words for us<\/a> after a briefing we had with them last week.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In writing up a longer post about continuing the Enterprise Agile conversation, I recalled an idea I had during an AJAX component company (eBusiness Applications) briefing a few days ago: the Scrum backlog is a perfect application of a web bases spreadsheet. Backlog? A backlog, in Scrum, is just a list of things (coding and [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,7,13,36],"tags":[],"class_list":["post-32","post","type-post","status-publish","format-standard","hentry","category-agile","category-collaborative","category-ideas","category-the-new-thing"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/32","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/comments?post=32"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/32\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/media?parent=32"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/categories?post=32"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/tags?post=32"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}