Estimation. Agile retrospectives « 3months Blog. 3months Innovation Promotion Posted by on 21 November 2013 | 69 Comments 3months wants to encourage cool web ideas to become real so we are putting our money where our mouth is.
In our experience many valuable web application ideas don’t get off the ground either because traditional IT business case processes kill them or because its hard to communicate web stuff without showing your decision makers your idea working. If this rings any bells, then this new innovation programme that should interest you. 69 comment(s) | Read the full post 3months Christmas Presentations Posted by on 10 January 2013 | 40 Comments. Mike Cohn's Blog - Succeeding With Agile® Leading Agile. Agile Techniques Content on InfoQ. Software Development Directory - Programming, Testing, Database, Agile Tour 2009 à Toulouse, supports des présentations - SigmaT. XPlanner Home. Agile Project Management, Scrum, and Agile Development Tool. Results of Agile Adoption Survey 2008. In February 2008, Dr.
Dobb's ran a survey on the adoption of Agile software development techniques and gathered statistics from 642 respondents. The surprising part of the survey was the the adoption rate which was same as last year at 69 percent. Other statistics, however do show change. Scott Ambler mentioned that in 2006 the adoption percentage was 65 which grew to 69 percent in 2007 and was 69 percent again in 2008. Scott added that he did some number crunching to understand the reason behind the peaking adoption rate. When I analyzed the adoption rates by role, I found that only 61.4 percent of developers thought they were doing Agile, whereas 78.2 percent of IT management thought so, the exact opposite of what I would've expected to see if stealth adoption was occurring.
There were other interesting results from the survey. Most responds preferred shorter iterations, which were between one and four weeks. Software Development Poll: Programming, Testing, Open Source, UM. Adoption of Agile Methods After a similar poll in 2005, Methods & Tools looked again in 2008 at the adoption of agile software development approaches.
The question was: At what stage is the agile approach (XP, Scrum, FDD, ...) adoption at your location? Participants: 512 (232 in 2005) Ending date: February 2008 Comparing the 2008 and 2005 results, we could notice that the level of ignorance of the agile movement has decreased, as only 13% of the organizations are ignorant of it. Disadvantages of Agile Software Development. Don’t get me wrong. I’m a big fan of agile development. If you’re a regular reader of my blog, you’ll know that :-) Agile planning in real life. "We're agile, we do iterations.
" You hear this statement often from teams claiming to do agile development. But there's a lot more to being truly agile than doing your development in iterations. Traditionally, development teams have specific releases with pre-determined content and pre-determined dates. At the start of each release, the management team meets with the development team for the ritual arm-twisting for commitments on both the release date and the content. The challenge in this scenario is that management is trying to dictate both the release date and the content, while the development team's belief is that they can achieve one or the other.
This article serves as a roadmap that can help you overcome this difficulty and move your team from doing plain iterative development to agile development. Suggestions for helping your team transition to using agile planning.Guidance on iterations. Easing the transition Here are some things to consider before you start to transition: Redev 2008 - Agile - Agile Planning Beyond the Next Iteration - ScrumWorks - Scrum Project Management Software and Tools. The Zen of Scrum 1.1. Henrik Kniberg's blog. I debug, refactor, and optimize IT companies.
And jam alot too. Friendly Guide to Climate Change (and what you can do about it) I’ve spent ALOT of time the past few months trying to understand climate change and global warming, and how to effectively contribute. I’ve dug through 1000-page scientific reports, talked to experts, and basically tried to digest as much information as possible. I was surprised by how little I knew before. So here’s a short animated video summarizing the whole issue. Please help spread it as widely as possible! I hope this video will inspire many people to make small changes, and a few people to make big changes. Read more Effective carbon offsetting – what we’ve learned and what we’re doing Flying causes global warming. Fly as little as possible.
Scrum and XP from the Trenches. The tricky part to agile software development is that there is no manual telling you exactly how to do it.
You have to experiment and continuously adapt the process until it suits your specific situation. This book aims to give you a head start by providing a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time. Under the leadership of Henrik Kniberg they experimented with different team sizes, different sprint lengths, different ways of defining "done", different formats for product backlogs and sprint backlogs, different testing strategies, different ways of doing demos, different ways of synchronizing multiple Scrum teams, etc. They also experimented with XP practices - different ways of doing continuous build, pair programming, test driven development, etc, and how to combine this with Scrum. Denis Dollfus' Blog: Développeurs, déterminez votre niveau.
On parle tellement en ce moment des méthodologies Agiles (eXtreme Programming, Scrum, Lean, ...) qu'on finirait presque par se croire tous Agiles.
Voici un petit test qui vous permettra d'évaluer votre niveau d'agilité personnel, de faire la part entre l'agilité idéale et les pratiques mises en oeuvre au jour le jour par vous et les autres membres de l'équipe. Ce test n'est pas une évaluation formelle mais un test plutôt ludique qui vous aidera à vous situer par rapport aux canons des méthodes agiles, à la manière des tests de magazines. Comme j'ai remarqué une certaine indépendance entre les pratiques agiles de gestion de projet et les pratiques agiles de développement, le résultat de ce test vous sera présenté sur ces deux axes, management et ingénierie.
[Mise à jour du 26/01/2009 : les résultats sont publiés ici -- ce qui ne vous prive pas pour autant d'y répondre pour connaître votre score...] Agile Software Development. Transforming the World of Work. Control Chaos. Agile Alliance: Agile Alliance Home. Agile Software Development: How To Implement Scrum In 10 Easy St. So you’ve got your backlog in order , estimated your backlog , clarified your requirements , planned your sprint and created a collaborative workspace . You’ve sprinted to achieve your sprint goals , run daily stand-up meetings and tracked progress with a daily burndown chart . Now you’ve come to the end of your Sprint and finished when you said you would . All that’s left to do now, is Review, Reflect and Repeat… At the end of the Sprint, hold a Sprint Review meeting.
Invite the whole team. Review what was delivered in the Sprint. The purpose of the Sprint Review is three-fold: It allows team members to show what they’ve achieved and demonstrate their contribution to the product. It allows all key stakeholders to see what’s been done, and provide valuable feedback on a regular basis, while there’s still time to take it on board.