How to structure you D365 Project Operations Lite project in DevOps?
Matthew Lazowski
D365 Project Operations | 100% focus on D365 ProjOps since 2016 | Global experience | Advisory | Making a difference |
Much has changed since Microsoft released D365 PSA 1.0 in 2016. D365 PSA 4.x re-branded as D365 Project Operations Lite is a mature project used by hundreds of companies mainly in North America, Western Europe, and Australia. Since 2016 I have had the opportunity to take part in approx. 30 PSA and ProjOps implementations as a Solution Architect, Consultant, Trainer or Advisor.
Many companies I have worked with use Azure DevOps (or Jira) to manage their implementation tasks. Many people here blog about DevOps and I believe that it needs no further introduction. I have come up with a list of project epics that you can import to DevOps when you start your Dynamics Project Operations Lite project. The list is presented below and really hope that some of you will find it useful.
1.??????Office 365 setup: named users, service users, licenses, storage
2.??????Dynamics 365 setup: instances, applications, security roles
3.??????Project Operations’ basic setup: currencies, invoice frequencies, organizational units, task modes etc.
4.??????Project sales process: lead-opportunity-quote-contract) including estimation, bid, approval, and handover processes
5.??????Project costing and pricing: cost price lists, sales price lists, pricing dimensions; transfer prices
6.??????Project classifications: T&M/fixed fee; estimation/done deal; customer/internal, etc.
7.??????Project Management: PMO’s role; PMs’ role etc.: project templates, project plans, progress tracking, handling changes and change orders
8.??????Resource Management: generic and named resources; planning horizon and granularity, top-down and bottom-up planning, central/hybrid resource scheduling, process and roles involved
9.??????Additional Resource Management features: custom booking statuses, configuring Schedule Board, resource demand planning etc.
10.??External resources (as contacts or users) and subcontractors (using PO subcontracting feature)
领英推荐
11.??Timesheet and expenses process, approvals, preparation for billing
12.??Transactions and invoicing in Project Operations in Dynamics CE
13.??Integration with an accounting system: transactions, invoices
14.??Integration with an HR system: resources, grades, skills, work hours, holidays
15.??Document templates and signatures: quotes, contracts, and invoices (often using Document CorePack and DocuSign)
16.??Teams integration
17.??Reporting: forecast, revenue, planned utilization, actual utilization using D365 and Power BI
18.??Security Model: business units, security roles, teams, security profiles
19.??Master data: accounts, contacts, project contracts, project templates, resources, price lists etc.
20.??Data migration: from Dynamics Sales to Dynamics Project Operations, from another system.
Please let me know your thoughts. Do you see any other common processes and topics that you need to address on your Project Operations projects or that is key on your own project? Please comment and feel free to contact me directly as well. Your feedback will be greatly appreciated!
Senior Services Sales Architect bei ServiceNow, MBA
2 年Ingo Berger Ggf. interessant für dich?
Group Leader - Power Platform UG | Director Dynatecon Solutions
2 年Minimum License limit of 20 is still applicable for Project Operations Lite? If it wasn't there, I am sure the adoption would be more.