tag:blogger.com,1999:blog-168828253523263225.post4079994759625229846..comments2023-08-01T08:31:54.659-04:00Comments on Sharing Technologies: Agile: SCRUM is Hype, but XP is More Important...Dom Derrienhttp://www.blogger.com/profile/15197441189507302313noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-168828253523263225.post-28325289943967776942014-06-30T03:44:00.208-04:002014-06-30T03:44:00.208-04:00This is such an informative article on scrumand v...This is such an informative article on <a href="http://www.scrumstudy.com/" rel="nofollow">scrum</a>and very clearly written. Every single thought and idea is direct to the point. Perfectly laid out. Thank you for taking your time sharing this to you readers. - Anonymoushttps://www.blogger.com/profile/05787683989611817287noreply@blogger.comtag:blogger.com,1999:blog-168828253523263225.post-23267990583198289622010-08-17T01:44:31.212-04:002010-08-17T01:44:31.212-04:00Just linked this article on my facebook account. i...Just linked this article on my facebook account. it’s a very interesting article for all.Scrum Processhttp://learnsoftwareprocesses.comnoreply@blogger.comtag:blogger.com,1999:blog-168828253523263225.post-53210999961451404722009-04-17T11:01:00.000-04:002009-04-17T11:01:00.000-04:00@James:
You're right: in typical waterfall organi...@James:<br /><br />You're right: in typical waterfall organizations, it's easier to have top management accepting Agile development methods by implementing Scrum first, because it gives them monitoring tools. These organizations implement what Joel Spolsky called “The Command and Control management method” [1]. Waterfall-type managers are often control-freaks because they don't trust the development teams. The burn down chart can help them delegating low-level management while still controlling the work progress...<br /><br />In this post, I complain about Scrum from the developer point of view, when managers are mainly using it as a monitoring tool. My point is about using XP practices to balance some Scrum side-effects.<br /><br />The success is in a balanced combination of Scrum and XP, combination we both agree on ;)<br /><br />A+, Dom<br />--<br />[1] http://www.joelonsoftware.com/items/2006/08/08.htmlDom Derrienhttps://www.blogger.com/profile/15197441189507302313noreply@blogger.comtag:blogger.com,1999:blog-168828253523263225.post-81547939963429351772009-04-16T11:54:00.000-04:002009-04-16T11:54:00.000-04:00I agree and understand Dom's points here - I know ...I agree and understand Dom's points here - I know where he is coming from. That said, I do not bevelie Scrum is hype. Scrum, if actually applied correctly, is a huge step for the large enterprise that previously employed waterfall processes. I think that is a much larger step than going from well structured scrum to XP or even just most of the XP practices.<br /><br />Now - if you can employ Scrum, and then work in some of the engineering practices at the same time, you have better enablers for successful agile. In fact, the engineering practices shoudl come first if at all possible... specifically the ones that Dom has highlighted from XP.<br /><br />- JamesJames Korotneyhttp://www.linkedin.com/in/jkorotneynoreply@blogger.com