Software Development Cross Solution - Index of - Free

formalize if necessary
Formal attire required...
There are projects where you may need more formality than index cards and sticky
notes. Some customers and companies want documents that are a little more formal.
It’s OK, though; everything you’ve learned still applies, and you don’t need to scrap a
process that’s working just to dress up your development a bit.
First, remember that unless you absolutely have to, wait until the end of your current
iteration to make any changes to your process. Next, know why you’re making a
change and how you’re going to measure its effectiveness. “The customer won’t pay
me unless we have design documentation” is a perfectly reasonable starting point for
dressing up your process. However, it’s still important to know how you’re going to
measure effectiveness. Most customers are (rightfully) concerned about their business
and aren’t just looking to give you extra work.
If you’re going to put together more documentation, project plans, use cases, or
anything else, make sure it helps your customer—and hopefully your team—be better
at communication. That’s a result that is good for your project.
Do what you’re doing...just prettier
Most of the work you’re doing can be captured and reported in a more formal
fashion. With software and a little extra polish, everything from your big board to
your user stories can be converted into something that meets your customer’s needs.
You may need to turn your
user stories into use cases.
Flip to Appendix i for some
examples of use cases.
424 Chapter 12
You can usually capture most of
what’s on your board in software
like Microsoft Project if you need
more formal project planning.
Download at WoweBook.Com
Your class diagrams might
need to be translated into
a tool like Rational Rose, or
captured in design documents.