Stories in TargetProcess

TargetProcess is fantastic tool for managing projects using Agile techniques. Gone are the days of 6 month Gantt charts, not truly knowing where you’re at on a daily basis and less effective communication of status.

Stories and task breakdowns are the essential elements in this tool, but TargetProcess is incredibly flexible in how you can use it – from usage by one man shops to enterprise level teams.

I use TargetProcess on my personal projects by first creating stories, the equivalent of requirements, and having conversations with the end user to hash out the details of the story and beginnings of a domain model:

 

The beauty of stories is that they are simple to create and track. What is difficult is thinking about going back to utilizing other requirement methods because stories provide significant value by just being so easy to use. 

With stories, you do not try to get it all right upfront, but you do try to write as many stories as possible. From here, you can break down stories further, come up with tasks, and/or roughly estimate the story.

Related Articles:

    Post Footer automatically generated by Add Post Footer Plugin for wordpress.

    About Nelson Montalvo

    I’m a software developer who loves .NET, Agile methodologies, Test Driven Design, Domain Driven techniques, and open source tools. Don’t get me wrong, I also like to use a thing or two that Microsoft creates besides .NET itself. :) In my “spare time” (when is that, anyways?) I like riding my motorcycle (http://sportbike.nmonta.com), reading, watching movies (lots of movies), working out, and hanging out (good conversation, good beer, good times). Look me up in Facebook, Linked In or Plaxo. My personal code blog is http://codemonkey.nmonta.com.
    This entry was posted in Agile. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

    2 Responses to Stories in TargetProcess

    1. agilejoe says:

      I couldn’t agree more how awesome TargetProcess is. Not to mention how great it’s Agile Reporting engine is.

      On a side note I couldn’t help but notice you story names. Don’t fall into the same traps that you have experienced elsewhere.

      Consider the following template:

      I as a {role} want {function} so that {business value}

      Follow these guidelines:
      Write for One User
      Write in Active Voice
      Do not Number Story Cards
      Don’t Forget the Purpose

      Cheers!

    2. Michael says:

      Good post. In fact we (at TargetProcess) often rush to fast with TargetProcess development. It seems that often people need very simple things and concepts like user stories. For us user story is so obvious thing to work with that we even forgot how it is possible to live without it :)