LiveCode and SCRUM tools

[Mark Wilcox]

>> I watched the videos on Scrum and Kanban.  I realize they are very short<br/>>> overviews and I may be missing something but neither one of them appears to<br/>>> include the concept of a critical path.  Not sure how a project management<br/>>> tool can function correctly without that.<br/><br/>If you're doing agile iterative development correctly then you're supposed to build vertical slices of functionality and as such you don't get a traditional waterfall style critical path. Of course there are still dependencies between tasks but you handle that by prioritising them so that the dependencies get built first. Most software is pretty malleable and this works out OK but I can't see it working for safety critical systems and a lot of types of project outside the software industry.<br/><br/>In my experience you also get problems of this nature in much larger software systems where lots of teams doing iterative development have to take input from other
 teams to make sure dependencies get built on time. The Scrum folks propose scaling across a large organisation like this by having a "scrum of scrums" and even higher order meetings if the development organisation is large enough. In practice I've never seen this really work.<br/><br/>Mark<a href="http://overview.mail.yahoo.com?.src=iOS"><br/><br/>Sent from Yahoo Mail for iPad</a>