Project Management
Emma
I have been using the project module on tryton for a little less than
a month to track time spent on different projects and it works great.
I have a few new projects that are scheduled ti start soon and I
wanted to use tryton for those projects from conception to billing.
Which led me to questioning the "same parent" restriction on task
predecessors/successors. Let me explain, here is an example of what I
was thinking to manage an MVC dev project
My project
+ Model
| + Product
| | + create (task)
| + Customer
| | + create (task)
| + Order
| | + create (task)
+ View
| + Product list
| | + create (task)
| + Product detail
| | + create (task)
| + View cart
| | + create (task)
| + Place order
| | + create (task)
| + Login
| | + create (task)
| + Order list
| | + create (task)
| + Order detail
| | + create (task)
+ Controller
| + Catalog
| | + list_all (task)
| | + get_detail (task)
| + User
| | + create (task)
| + Cart
| | + create (task)
+ General
+ Install database
+ Install dependencies
This is a simplistic approach. Now in order to start my controller =>
catalog => list_all task I first have to have completed my model =>
product => create task
So in this example, I cannot use the predecessors/followers since
those tasks don't have the same parent, they do have a common ancestor
thou.
More over If one of my top projects is "install new server" and
another is "brand new site for new client", in my planning, it's much
better to be done installing (at least some parts of) the new server
before starting to deploy the brand new sites. Those projects don't
even have a common ancestors.
Please tell me what you think.
Emma
Paul J Stevens
>
> I have been using the project module on tryton for a little less than
> a month to track time spent on different projects and it works great.
>
> I have a few new projects that are scheduled ti start soon and I
> wanted to use tryton for those projects from conception to billing.
> Which led me to questioning the "same parent" restriction on task
> predecessors/successors. Let me explain, here is an example of what I
> was thinking to manage an MVC dev project
[tree cut]
> This is a simplistic approach. Now in order to start my controller =>
> catalog => list_all task I first have to have completed my model =>
> product => create task
> So in this example, I cannot use the predecessors/followers since
> those tasks don't have the same parent, they do have a common ancestor
> thou.
This can be solved for you by creating a small custom module that will
modify the predecessors and successors fields to relay the restriction
currently in place. Looks trivial enough.
> More over If one of my top projects is "install new server" and
> another is "brand new site for new client", in my planning, it's much
> better to be done installing (at least some parts of) the new server
> before starting to deploy the brand new sites. Those projects don't
> even have a common ancestors.
You could use the relaxed restrictions on predecessors/successors, but I
get the feeling this more like milestones: sets of tasks or sub-projects
from possibly disparate projects whose completion denotes a marked phase
transition even when the respective parent projects are not completed.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/in...@nfg.nl/+31.85.877.99.97
________________________________________________________________
Bertrand Chenal
Emma <deles...@gmail.com> a écrit :
> This is a simplistic approach. Now in order to start my controller =>
> catalog => list_all task I first have to have completed my model =>
> product => create task
> So in this example, I cannot use the predecessors/followers since
> those tasks don't have the same parent, they do have a common ancestor
> thou.
Have you tried to define predecessors/successors relations at the parent
level? IIRC this will be taken into account.
Btw any other problems/remark/ideas with the planning feature? I wrote
the project_plan module without precise use case in mind, so I will be
glad to have feedback.
Thx,
Bertrand
--
Bertrand Chenal
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Email: bertran...@b2ck.com
Website: http://www.b2ck.com/
Jordi Ballester Alomar
I have developed modules in openerp to handle this. Look at :
https://launchpad.net/eficent-openerp-project-management
The project_time* modules are for managing this.
project_scope_wbs is also very interesting for complex projects, as it
helps you better navigate through the project work breakdown structure
you depicted.
tray
Sorry this is a slight diversion from the question but.....I'm trying
to get into the project management within tryton. I'm having trouble
getting my head around getting projects to being invoiced. Is there a
reference that I can refer to help?
You guys seem to know more than I on this topic.
Thanks.
Paul J Stevens
> Hi,
>
> Sorry this is a slight diversion from the question but.....I'm trying
> to get into the project management within tryton. I'm having trouble
> getting my head around getting projects to being invoiced. Is there a
> reference that I can refer to help?
You can use project_revenue to set a product on a project, but that
still won't get you to invoicing, just valuation of the work done.
It depends on how you wish to invoice projects - what entails a project
in your business.
Me, I do a lot of time-based billing. For that I wrote timesheet_invoice
(availabe on pypi and github). It allows me to write timesheet lines on
a task, and generate invoices and reports now and then based on billable
hours.
I'm currently working on contract_retainer where I have an agreement to
do a certain amount of work for a client in the context of one or more
projects, need to give an accounting of hours spent and track the
balance between invoiced hours and hours actually spent on the client.
All this is probably useless for projects to deliver certain goods, or
projects that are fixed price in nature. For those, you can use the
project modules for managing projects, but I would generate invoices
manually.
Cédric Krier
> Le Mon, 6 Feb 2012 07:00:39 -0800 (PST),
> Emma <deles...@gmail.com> a écrit :
>
> > This is a simplistic approach. Now in order to start my controller =>
> > catalog => list_all task I first have to have completed my model =>
> > product => create task
> > So in this example, I cannot use the predecessors/followers since
> > those tasks don't have the same parent, they do have a common ancestor
> > thou.
>
> Have you tried to define predecessors/successors relations at the parent
> level? IIRC this will be taken into account.
I think the issue is because the project_plan uses the concept of
milestone and Emma did not split the project in milestone but in "kind
of work".
Perhaps we miss an other concept which allow to group project task in an
other tree structure for business vision etc. A little bit like the idea
of consolidation in accounting.
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: cedric...@b2ck.com
Website: http://www.b2ck.com/
Emma
> This can be solved for you by creating a small custom module that will
> modify the predecessors and successors fields to relay the restriction
> currently in place. Looks trivial enough.
thought about it :)
> I think the issue is because the project_plan uses the concept of
> milestone and Emma did not split the project in milestone but in "kind
> of work".
be able to use Tryton from scratch on a new project.
I thought of using the (sub)project description field as an analytical
repository for both developpers and client. Developpers can check what
is exactly expected and I'm planning on a custom report that could be
printed and signed by the client based on the tryton project.
Maybe the "project" in this particular scenario is actually a
milestone...
> Perhaps we miss an other concept which allow to group project task in an
> other tree structure for business vision etc. A little bit like the idea
> of consolidation in accounting.
project_business or project_analytics which would allow to group works
of a parent project into different categories/groups ?
Emma