<p>There are numerous <a href="http://en.wikipedia.org/wiki/Agile_software_development" rel="nofollow noreferrer">Agile software development</a> methods. Which ones have you used in practice to deliver a successful project, and how did the method contribute to that success? </p>

[{'answer_id': 6581, 'author': 'SQLMenace', 'author_id': 740, 'author_profile': 'https://Stackoverflow.com/users/740', 'pm_score': 3, 'selected': False, 'text': "<p>Scrum because it shows where the slackers are. It also identifies much faster that the business unit usually doesn't have a clue what they really want delivered</p>\n"}, {'answer_id': 6588, 'author': 'Matt Sheppard', 'author_id': 797, 'author_profile': 'https://Stackoverflow.com/users/797', 'pm_score': 4, 'selected': True, 'text': "<p>I've been involved with quite a few organisations which claimed to work in an 'agile' way, and their processed usually seemed to be base on XP (extreme programming), but none of them ever followed anywhere near all the practices.</p>\n\n<p>That said, I can probably comment on a few of the XP practices</p>\n\n<ul>\n<li><p><strong>Unit testing</strong> seems to prove very useful if it's done from the start of a project, but it seems very difficult to come into an existing code-base and start trying to add unit tests. If you get the opportunity to start from scratch, test driven development is a real help.</p></li>\n<li><p><strong>Continuous integration</strong> seems to be a really good thing (or rather, the lack of it is really bad). That said, the organisations I've seen have usually been so small as to make any other approach seem foolish.</p></li>\n<li><p><strong>User story cards</strong> are nice in that it's great to have a physical object to throw around for prioritisation, but they're not nearly detailed enough unless your developer really knows the domain, or you've got an onsite customer (which I've never actually seen).</p></li>\n<li><p><strong>Standup meetings</strong> tend to be really useful for new team members to get to know everyone, and what they work on. The old hands very quickly slack off, and just say things like 'I'm still working on X', which they've been doing for the past week - It takes a strong leader to force them to delve into details.</p></li>\n<li><p><strong>Refactoring</strong> is now a really misused term, but when you've got sufficient unit tests, it's really useful to conceptually separate the activity of 'changing the design of the existing code without changing the functionality' from 'adding new functionality'</p></li>\n</ul>\n"}, {'answer_id': 6621, 'author': 'Jeff Donnici', 'author_id': 821, 'author_profile': 'https://Stackoverflow.com/users/821', 'pm_score': 2, 'selected': False, 'text': '<p>Scrum.</p>\n\n<p>The daily standup meeting is a great way to make sure things stay on track and progress is being made. I also think it\'s key to get the product/market folks involved in the process in a real, meaningful way. It\'ll create a more collaborative environment and removes a lot of the adversarial garbage that comes up when the product team and the dev teams are separate "silos".</p>\n'}, {'answer_id': 33609, 'author': 'codeLes', 'author_id': 3030, 'author_profile': 'https://Stackoverflow.com/users/3030', 'pm_score': 1, 'selected': False, 'text': '<p>I\'ve been working with a team using XP and Scrum practices sprinkled with some lean.  It\'s been very productive.</p>\n\n<p><strong>Daily Standup</strong>- helps us keep complete track of what and where everyone is working on.</p>\n\n<p><strong>Pair Programming</strong>- has improved our code base and helped remove "silly" bugs being introduced into the system.</p>\n\n<p><strong>iterative development</strong>- using 1 week iterations has helped up improve our velocity by setting more direct goals which has also helped us size requirements</p>\n\n<p><strong>TDD</strong>- has helped me change my way of programming, now I don\'t write any code that doesn\'t fix a broken test and I don\'t write any test that doesn\'t have a clearly defined requirement. We\'ve also been using executable requirements which has really helped devs and BAs reach requirements understandings.</p>\n\n<p><strong>kanban boards</strong>- show in real time where we are. We have one for the Milestone as well as the current iteration.  At a glance you can see what is left to do and what\'s being done and what\'s done and accepted.  If you don\'t report in your daily standup something pertaining to what\'s on the board you have explaining to do.</p>\n\n<p><strong>co-located team</strong>- everyone is up to speed and on page with what everyone else is doing. communication is just-in-time, very productive, I don\'t miss my cube at all.</p>\n'}, {'answer_id': 130221, 'author': 'colivier', 'author_id': 1999, 'author_profile': 'https://Stackoverflow.com/users/1999', 'pm_score': 2, 'selected': False, 'text': '<p>Having regular retrospectives is a great way to help a team become more effective/agile. \nMore than adhering to a specific flavor of Agile this practice can help a team identify what is working well and adapt to a changing environment.</p>\n\n<p>Just make sure the person running the retrospective knows what he/she is doing otherwise it can degenerate into a complaining session. </p>\n\n<p>There are a number of exercises you can take a team through to help them reflect and extract value from the retrospective. I suggest listening to the interview with <a href="http://www.se-radio.net/podcast/2008-07/episode-105-retrospectives-linda-rising" rel="nofollow noreferrer">Linda Rising</a> on Software Engineering Radio for a good introduction.</p>\n\n<p>Do a Google search for "Heartbeat retrospectives" for more information.</p>\n'}]
['https://Stackoverflow.com/questions/6579', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/-1/']