To maximize business benefits, we first clarify objectives, plan and budget
1 - Project definition (10%)
Before the kick-off, we formalize the project objectives, scope, methodology and budget.
Business Case* - cover both, what the project is expected to achieve and what are the business benefit for the company.
Scope* - define the function covered by the project and what is out of scope. For small projects we define complete high level requirements to lock the scope before the kick-off.
Milestones and planning - We define first the release strategy. To design the right process, we usually develop the IT product by stage: prototyping (optional), release candidate and live deployment.
Stakeholders - set the team and responsibilities. Port Cities offers product owners, project managers, business consultant, Odoo functional analyst and developers.
The company that implement Odoo should take important responsibilities in the project to garantee the sucess!
Budget* - a fixed budget can be set only after high level requirements gathering. For big projects it requires to buy a "pre-sales" or "requirements gathering" study.
For companies that prefers flexible contract, on a man-day basis, we define an estimated budget that is revised monthly.
Develop a minimum product
We deploy first a minimum product to go live
Requirements gathering (10%)
In case a fixed price is required for big project, a preliminary "requirement gathering" is required to be purchased. Otherwise it will simply be done at the beginning of the project.
Process and business rules
- design workflow using BPMN
- define user process
Report and user interface*
go-live: data migration, training and support
Estimation and planning
- Estimate time of each deliverable/task with the team members (developers)
- Add risk estimation for unknown deliverable/task. Usually done for the entire project, we add 10%-50%.
Build a prototype, then a product (45%)
1 - Our team breakdown story/requirements in smaller deliverable (max 1 day work) and set a deadline for each item.
2 - We work by weekly sprint and deliver a version every 1-2 weeks.
3 - We prioritize items to deliver first a prototype that will help to collect requirements. Then a minimum product (not ideal but good enough) that is ready to go-live.
Documentation & training material
4 - We keep update workflows and a user guidebook as a reference document for users and project team
Test to clarify requirements, preare data (15%)
Train users and test the product
- we train users on the product by focusing on story, scenarios and use cases.
- we collect feedback and update our product backlog.
- We test the system with real data as soon as possible
- Before the go-live we build solid scenarios and proceed to a formal UAT to align every stakeholders before the go-live.
Deployment & Closing
Manage deployment risks & evaluate customer satisfaction
Deployment preparation (10%)
Define a strategy
- We define a strategy for the go-live
- We assess the risks and prepare a plan of preventive and corrective actions
- We prepare solid communication and align all players.
- We template for master data and operating data
- We simulate go live to verify the process
- We prepare tool and check-lists to control the go-live
- Managed by the client, we serve as adviser and support