Software Development Cross Solution - Index of - Free

How to ruin your team’s lives
It’s easy to look at those long schedules, growing estimates, and
diminishing iteration cycles, and start to think, “My team can
work longer weeks!” If you got your team to agree to that, then
you’re probably setting yourself up for some trouble down the line.
�
�
�
�
Personal lives matter
Long hours are eventually going to affect your personal
life and the personal lives of the developers on your team.
That might seem trite, but a happier team is a more
productive team.
Fatigue affects productivity
Tired developers aren’t productive. Lots of studies suggest
that developers are really only incredibly productive for
about three hours a day. The rest of the day isn’t a loss,
but the more tired your developers are, the less likely
they’ll even get to that three hours of really productive
time.
The first step to planning what you are going to develop
is to ask the customer to prioritize their requirements.
Milestone 1.0 should be delivered as early as you can.
During Milestone 1.0 try to iterate around once a
month to keep your development work on track.
When you don’t have enough time to build everything,
ask the customer to reprioritize.
Download at WoweBook.Com
�
�
�
project planning
Be confident
in your plans
by applying
velocity
and not
overworking
yourself and
your team.
Plan your iterations by factoring in your team’s velocity
from the start.
If you really can’t do what’s needed in the time allowed,
be honest and explain why to the customer.
Once you have an agreed-upon and achievable set of
user stories for Milestone 1.0, it’s time to set up your
development dashboard and get developing!
you are here 4 103