use that efficiency because requirements get
changed before the project ends, usually right from the start.
processes like Extreme Programming
(XP) and Scrum
requirements will change and create
opportunities for improvement and competitive advantage. We just can't
count on requirements being a
constant. Instead we will represent each feature the
customer wants as a user story
. Story cards are a low
mechanism for scoping out a project without spending our entire
analysis budget up front.
Now we can
flip the axis of the previous chart.
We visualize the activities, our process itself as the constant. Our
process is applied to our user stories in sequence. The activities are
on going and the user stories get what ever they need.
With professional software engineers on our project we can relax
knowing that the team will do what is needed to get the job done. Any
activity needed with any combination of people will just get done
without any further scheduling or ceremony. This is
the spirit and benefit of a self organizing team.