Our services
LEITH Solutions Development Approach
Leith Solutions adopt state of the art methodologies to optimize their development quality and minimize the time to operation for their clients.
Agile approach in the software development is used by the most prominent software development leaders in this century.
Benefits :
› Stakeholder Engagement
› Transparency
› Early and Predictable Delivery
› Predictable Costs and Schedule
› Allows for Change
› Focuses on Business Value
› Focuses on Users
› Improves Quality
› Meeting with the board of executives
› Interviews with keys managers/users
› Identify the current processes and document them
› Understand the business environment
› Adapt our language to client’s
› Cover the functional gap
› Identify the discrete tasks, responsibilities and time lines for the project
› Establish proper system policies for maintaining and backing-up data
› Plan the Project in conjunction with the Project Team
The Scrum model suggests that projects progress via a series of sprints. In keeping with an agile methodology, sprints are time boxed to no more than a month long, most commonly two weeks. At the end of a sprint, the team conducts a sprint review during which it demonstrates the new functionalities.
› Increase the quality of the deliverables.
› Cope better with the changes.
› Provide better estimates and spend less time doing them.
› Be more in control of the project schedule and state (short iterations, clear, unambiguous ways of calculating the velocity etc.).
› As a result we achieve higher customers satisfaction rate in general
This consists of transferring the accurate and secure master data and transactional data from the clients legacy systems into ODOO database.
For simple data migration, ODOO offers the possibility of using simple Excel / CSV files to import / export data in an easy and native manner.
To conduct complex data migration requirement for clients, we use many migrations tools. These tools allow us to create transformation scripts that will copy, manipulate and insert the source data into the ODOO database.
The purpose of the training is to make sure that users know every feature of the scope deployed like :
› How to enter transactions, and the different ways they can be entered and posted
› How to maintain the data that is accumulating in the system.
› How to use inquiries and reports to obtain the information you wish to access.
› How to design KPIs.
› How to draw up and personalize Dashboards.
› How to get the maximum from Odoo BI.
During this Phase, we provide :
› Functional help
› Error solving
› Unlimited bug fixing
› Management of security alerts
We can also :
› Design a plan for on-going improvement
› Schedule eventual additional phases of your implementation
QA & Testing approach performed through 4 layers of check points :
Acceptance Test will performed per sprint delivery, according to Analysis stated use cases Acceptance Criteria.
Acceptance Criteria will be based on Main Back-Log User Stories to provide details. They should be relatively high-level while still providing enough detail to be useful. They target Functional items that identify specific user tasks, functions or business processes that must be in place. A functional criterion might be “A user is able to access a list of available reports.”
Acceptance Criteria should state intent, but not a solution (e.g., “A manager can approve or disapprove an audit form” rather than “A manager can click an ‘Approve/Disapprove’ radio button to approve an audit form”). The criteria should be independent of the implementation: ideally the phrasing should be the same regardless of target platform.