Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
Hi,
I would suggest to add an additional item -'Story' to cope with Agile methodology. Story need to be linkable to Ticket , Activities, Requirements, Test cases, etc.
Should have standard fields (creator, date, etc.), description, and estimates (in Units or free format), status, may be some more - anybody suggestions welcome.
May be pick up some staff like it done in JIRA for Agile, including some diagrames
What difference between Story and Activity (except the name) ?
Story usually has more than one Activity and contains value of effort, complexity (including technical environment, experience of the team, how clear requirements are, how complex is the code to complete the story), and risk. Story is something that can be released when it completed. Story is the primary development artifact and the basis for defining the functions a business system must provide, and to facilitate requirements management.
Story usually has more than one Activity and contains value of effort,
So, to this point, it is similar to sub-project
complexity (including technical environment, experience of the team, how clear requirements are, how complex is the code to complete the story),
These points would look like requirements.
and risk.
Once again ,sub-project would fit.
Story is something that can be released when it completed. Story is the primary development artifact and the basis for defining the functions a business system must provide, and to facilitate requirements management.
This looks like product version
So Story would be an hybrid object, mid-way between sub-project, requirement and product version...
I'll have a look to agile methods to get more information
Request recorded as Ticket #1794