Diary of a Fence Sitting SOA Geek
In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.
- SOA,
Tracking change and innovation in the enterprise software development community
Posted by Mark Levison on May 20, 2008 07:58 AM
What factors influence the length of your sprint? When you're trying to pick a length between two days and six weeks what factors should you take into consideration? Ash Tengshe, Agile Coach at Capital One, suggests that choosing a sprint length is a matter of balancing forces that want to shorten vs. lengthen the sprint.
Forces that tend to Shorten
Forces that tend to Lengthen
Perhaps most importantly Dmitry Beransky reminds us that all of the forces still subservient to the team and what they find works for them.
Agile Development: A Manager’s Roadmap for Success
The Future of Software Delivery According to visionaries Grady Booch & Erich Gamma
Five Ways to Fail When You Scale
Agile Tools: The Good, the Bad and the Ugly
The Agile Business Analyst: Skills and Techniques needed for Agile
So what's the next question?
Clinton ;-)
I've worked in projects with sprints anywhere from 1 to 6 weeks and haven't really observed any issues that can't be overcome, with any length.
I suppose the general rule should be "As short as you can manage" simply to allow yourself more opportunity for feedback and correction. But I wouldn't reject the idea of a 6-week sprint just on the basis of that alone.
Bruce - I think that Dmitry hit the nail on the head. Whatever works for your team.
However I would be concerned with sprints that were longer than **three** weeks that they might devolve into a mini-waterfall. I've seen cases where there was a handoff to QA within the sprint.
In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.
Platforms need interoperability. In this article Flex interoperability with JSON and XML is explored including direct mapping to chart and grid components.
Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He presents the factors which contributed to the success of BMC's Agile adoption.
In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.
David Laribee discusses the purpose of ALT.NET, its mission and future.
Ruby on Rails has become a popular Ruby framework for creating web applications in recent years. An aspect of creating a web application is the need to repeatedly create the same base functionality.
Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.
Shaw and Fowler talk about the need for a new relationship between the business department and the IT department. Studies have shown that projects mostly fail due to miscommunication between the two.
3 comments
Reply