Join Doug Rose for an in-depth discussion in this video Calculating your velocity, part of Agile at Work: Planning with Agile User Stories.
- [Voiceover] In 1914 Henry Ford noticed that his employees…worked best when limited to eight hours.…After eight hours, their productivity began to slow down.…That's why Ford Motor established the 40 hour work week.…The change increased their productivity…and many companies soon followed.…That's why the 40 hour work week became standard.…In the 1980s fewer people worked in manufacturing.…they became desk workers and computer programmers.…Because of this, many employers felt that the 40 hour…work week was dated.…
It only made sense in manufacturing.…Working a 70 hour work week became a badge of honor…for desk working go-getters.…The agile framework pushes back on this…ever expanding work week.…Agile promotes the idea that people should go home…at a reasonable hour.…Often developers will think more clearly…when they're driving home or walking their dog.…An agile project should have a challenging pace,…there shouldn't be any project crashes.…The team shouldn't have a flurry of activity…at the end of the sprint.…
Even though they're not building cars,…
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Starting with user roles
- Creating user stories
- Grouping stories with themes or epics
- Creating a project charter
- Writing your release plan
- Avoiding common pitfalls