Starting a Project Right

When you look at statistics about how often IT projects fail or come up short it is hard to ignore properly defining the problem.  Two of the most common themes in failed projects are a lack of definition and a lack of usefulness.  In this first step in our video series, we look at finding the “why” for a project.  Then we look at how to build and document use cases.

Use Cases Done Right

There is no magic to creating use cases.  All that is required is an understanding of how a process should flow.  It is not a technical task or skill, but good use cases do lead to higher success rates in a project.  It is like getting in a car for a long trip.  A good GPS or maps will make it far more likely to reach the destination.  We look at some of the detail a good use case should contain and offer some real-life examples.  Thus, viewers can walk away from this tutorial and easily build their own use cases.

This series comes from our mentoring/mastermind classes.  These classes are virtual meetings that focus on how to improve our technical skills and build our businesses.  The goals of each member vary, but this diversity makes for great discussions and ton of educational value every time we meet.  We hope you enjoy this series as much as we enjoy creating it.

 

Presentation Deck: SoftwareRequirements

Rob Broadhead

Rob is a founder of, and frequent contributor to, Develpreneur. This includes the Building Better Developers podcast. He is also a longtime student of technology as a developer, designer, and manager of software solutions. Rob is the founder of RB Consulting and has managed to author a book about his family experiences as well as a few about becoming a better developer. In his free time, he stays busy raising five children (although a few have grown into adults). When he has a chance to breathe, he is on the ice playing hockey to relax.

Leave a Reply