Forum

  • If you are new to these Forums, please take a moment to register using the fields above.
Announcement Announcement Module
Collapse
No announcement yet.
New Project or Existing Project Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • New Project or Existing Project

    When should you create a new project versus put NA under an old project.
    For example, I'm working on delivering a new sofware module: that's a project. An emergency issue comes up, related to that project. It's kind of a subcomponent.
    I'm sure David doesn't have RULE for the above - all he would care about is that it gets collected, etc., so what's best practice. Which one produces the best feel - based on experience.

  • #2
    I frequently create a new project in the circumstance you describe. If clearing up this problem is the "next action" for the old project, I put "waiting for XYZ bug to be fixed" in @Waiting For as the Next Action of the old project, and then I get along with the new project.

    Comment

    Working...
    X