Agile Estimating and Planning" author, and Agile Alliance co-founder, Mike Cohn, provides detailed, proven techniques for estimating and planning any Agile project.
Agile Estimating and Planning s...
Agile Estimating and Planning" author, and Agile Alliance co-founder, Mike Cohn, provides detailed, proven techniques for estimating and planning any Agile project.
Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member.
Like to rate videos and let people know what you think?
Automatically share your ratings, favorites, and more on Facebook, Twitter, and Google Reader with YouTube Autoshare.
Autoshare makes certain YouTube activities public on the services you choose. Select only the services you are comfortable with - like Facebook, Twitter, or Google Reader - to let your friends know what you like on YouTube. You can turn Autoshare off at any time.
Like to share videos with friends?
Automatically share your ratings, favorites, and more on Facebook, Twitter, and Google Reader with YouTube Autoshare.
Autoshare makes certain YouTube activities public on the services you choose. Select only the services you are comfortable with - like Facebook, Twitter, or Google Reader - to let your friends know what you like on YouTube. You can turn Autoshare off at any time.
20% of IT projects fail completely. Weak methods produce weak results. Bigger projects need bigger methods. Design-build, not build-rebuilt. You can't rewrite a bridge. Why does anyone think it's OK to rewrite software because you screwed up the original design?
Autoshare makes certain YouTube activities public on the services you choose. Select only the services you are comfortable with - like Facebook, Twitter, or Google Reader - to let your friends know what you like on YouTube. You can turn Autoshare off at any time.
Weak methods produce weak results.
Bigger projects need bigger methods.
Design-build, not build-rebuilt.
You can't rewrite a bridge.
Why does anyone think it's OK to rewrite software because you screwed up the original design?
Agile isn't just for small teams on small projects. Here's a vision of how it can be applied to big projects. Basically, the same rules apply.
"Teams need three things from a company: money, moral support, and guidance."
"What is the size of this task compared to others?"
Plus a nice, quick description of how to estimate by relative size.
PS Skip the first 30 seconds and the last 50 seconds - they're ads.