[ 
https://issues.apache.org/jira/browse/OFBIZ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649978#action_12649978
 ] 

Julio Echeverria commented on OFBIZ-796:
----------------------------------------

Hello everybody,
Let me take the cordial David's invitation, and extend my congratulations for 
your contribution and I expect don't brake the scope but deeper the first two 
objectives proposed by Amid; I think that OFBiz PMA with little effort can 
resolve what no other ERP PM do it, because they have limited objective 
(inherited) to control time and resources (the process), but don't make the 
same with the results (the scope) and only express the completation percentage 
of activities.
This is because the result is (a unit) one (the classical big projects model), 
I think like our friend E.Poe, there is no great poem, the great poem is a 
successive of little poems.
1.> To make project Plan./Org. easier and intuitive
The Project tree (WBS): project, subproject, phase are nodes (as a accumulative 
planned/actual in phisical and monetary) to consult in any range of time.
2.> Process requests in a better way,
The Product tree (PBS): to make the tasks in cartesian product with process we 
can assign no only resources but requisitions of products (to buy) or services 
(subcontract) or results like manufacturing products, as we can associate with 
the workeffort application, and finally
The organization tree (OBS): When we are planning we assign generic resources 
ie. job positions, like chief, clerk, labourer, etc and in the schedule we have 
the timesheet of César Alvarez, Mike Billington, George Bush, etc,
I understand that project management scope is Services oriented, but we need at 
least some materials and its respective MRP for the projects (PRP). If these 
opinion is far of the scope sincerely excuse me 

> WorkEffort Application aka Project Management Application
> ---------------------------------------------------------
>
>                 Key: OFBIZ-796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-796
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>            Reporter: Amit Shinde
>            Assignee: Anil K Patel
>         Attachments: ProjectMgr.patch
>
>
> WorkEffort Application aka Project Management Application -
> Objective -
> 1.> make project planning/organization easier and intuitive,
> 2.> process requests in a better way,
> 3.> improve iteration planning,
> 4.> include ability to integrate seamlessly with invoices/billing ,
> 5.> generate detailed and snappy reports,
> 6.> send email/ mobile notifications.
> Process -
> Project Tree -
> 0 - Project/s (WE)
>                 1 - Sub Project/s (WE)
>                               2 - Task/s (WE)
>                                           3 - Sub-Task/s (WE)
>                 1 - Task/s (WE) - These are not assigned to any sub-project
> 0 - Task/s - These are not assigned to any project
> 0 - Request/s-
>                 1 - Request Item/s
> - Projects, Sub-projects and Tasks all are WorkEfforts of a respective type. 
> - Request is a CustRequest and can have many Request Items.
> - Time Entry can be done from any level or type of WE
> - Requests and WorkEfforts have many-to-many relationship
> Effort - 
> Most of the screens and models are already in place. We definitely dont need 
> any changes in the models. We need to add new screens, forms and services. 
> Heres a list of todos -
> Create Demo data of a project - I am working on this one right now. This will 
> be helpful for reports. We can import this and pick any of the reports and 
> start implement them.
> Create Reports Menu page - Adrian Crum has helped with this. 
> Reports - These are planned to be pdfs but to start with we can start 
> implementing them in HTML.
>  1.  Task by priority (Iteration planning), - Amit
>  2  Task over time estimate,  
>  3. Project summary  (By Supervisor / By Client), 
>  4. Gantt for Project, 
>  5. Tasks of type project, 
>  6. Tasks completed, times task was reopened,  Avg. time taken to fix a task 
> , Avg.  number of tasks fixed per day, - Amit
>  7. WE estimate versus actual. 
> UI - All these screens will be in HTML.
>  1.  Tasks assigned to me, - Amit 
>  2.  Tasks not assigned, dropdown/popup assign to X
>  3.  Tasks not scheduled
>  4.  Tasks past schedule
>  5.  Estimated schedule/ workload for me
> Email notifications -
>  1.  Tasks assigned to me
>  2. Weekly project summary
> Mobile Notifications -
> 1. Send SMS alert on any event. - Need to do more research.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to