In summary
Recipients
All companies or industries that want to implement new software, restructure software, or expand one, such as Management Systems, integrations with the production line for Industry 4.0, Business Intelligence, resource management systems, CRM, web portals, apps, and web apps.
Why
An external consultant ensures the fulfillment of requests and provides technical protection to the client company.
Objectives
Control: have a control plan on development and possible expansions Independence: have independence from potential developers (future) Usability: the software must be easy to use and clear Savings: it must be designed to allow users to save time Certain times and costs
Timelines
For the complete structuring, the Temporary Manager is applied, which can last a few weeks intensively and then taper off, transforming into occasional checks for the overall duration of the software development.
The phases
The project is based on 4 main successive phases. To proceed to the next one, the previous one must be completed.
Analysis and Project
Requirements analysis, creation of wireframes and the supply specifications.
1
Supply Tender
Implementation of the supply tender, identification of the technology and suitable supplier(s).
2
Sviluppo
Project division into milestones, Follow-up of development, coordination meetings, and progress.
3
Production and Maintenance
Follow-up of the application launch, training management, change management, and long-term maintenance.
4
1 -
Analysis and Project
1.1 - Business Process Analysis (User Case)
The entire workflow of the operators is analyzed, describing every expected functionality in the application. This allows for a clear understanding of business operations and optimizing the software to support them. Based on this, potential process improvements are evaluated to streamline them (for example, in a LEAN perspective).
1.2 - Requirements Analysis
Based on the previous analysis, a list of functional requirements expected from the application is created. Estimation or regulatory requirements are added to it.
The detailed list and the software's compliance with usage allow for easy quantification by the software house.
1.3 - Interface Design (Wireframe)
Based on the requirements, a preliminary design of the graphical interface is executed. This serves to give concreteness to the requirements and verify if all requested functionalities are actually present. For each button or field in the scheme, its expected functionality or limits are described. The interface is developed according to ISO and HCI standards to ensure standardization.
1.4 - Savings
Complete analysis of the interface and usage mode and estimation:
of the time saved by the operators
reduction of any error rate / non-compliance in the process
increase in process control capacity
potential future expansions
1.5 - Specifications
It concludes by drafting the actual contract specifications attaching:
Use cases specifying usage methods by various users
Requirements analysis: the exact list of needs
Wireframe: the graphic interface scheme accompanied by explanations
the client's technical obligations: development environment, server etc
the standard code documentation: essential if in the future there is the possibility of having multiple software houses develop simultaneously or if you want to change the current one
manuals: installation, usage etc
the timeline plan: when release is required
the training planfor usage
maintenance requirements: costs, application duration
future expansion scenarios: to prepare any APIs or custom classes.
any penalties
2 -
Supply Tender
2.1 - Supplier research
After searching for potential suppliers in the area, they are invited to learn about the project. Meetings are then organized to explain the specifications, addressing any of their doubts or requests.
2.2 - Selection of the best proposal
Based on the proposals, a round table discussion is held to evaluate the best one considering: costs and payment plan, development methods (Agile, Scrum, Incremental, Evolutionary, etc.), any grants to cover the expense, application architecture, maintainability, compliance with requirements
3 -
Sviluppo
3.1 - Development Plan Creation
Based on the chosen company, the project is divided into milestones and a coordination meeting is scheduled: the software house will thus monitor the work done and the client will have a tangible status of the development and progress compared to the indicated timelines.
3.2 - Test Plan Creation
Based on the development plan and milestones, the test plan for the application is organized by the client. It is essential to verify the application before it is released. Ideally, future users should highlight any gaps or shortcomings, which, if identified early, allow for course correction without significant waste (time and money).
3.3 - Monitoring and Follow-up
We will monitor every activity, participate in every meeting, create reports, and update the activity plan according to any advances or delays, informing the client of any issues.
4 -
Production and Maintenance
4.1 - Release
At the time of release, i.e., the installation of the application on the server or terminals, we will monitor the launch and ensure the delivery of the installation manual (essential for future autonomous installations). The release is planned to minimize company germs.
4.2 - Training
We will create the training plan to be as fast and effective as possible, limiting company downtime. We will randomly monitor training interventions to assess their quality and potentially negotiate with the supplier for any discounts or improvements.
4.3 - Maintenance
Immediately after the release, we will follow the scheduled maintenance plan. Scheduled maintenance prevents unexpected downtimes and long-term issues.
4.4 - Evolution
The software must evolve and keep pace with the company, which is why it may be useful to evaluate an evolutionary plan 6 months / 1 year after the release to request any modifications or implementations. It is pointless to request them earlier as if it is not fully integrated, the requests may be superfluous and costly.