Technical management & development teams
Dtouch combines overall vision, project management and coordination of skills. Architecture, development, integration and production are part of a common organization, with identified technical management.
Concrete functions.
Tools in situ.
Interfaces used to organize work, prepare data and track files. Each screen shows a specific function, with presentation data.
Enlarge screen A common view for teams
The weekly schedule brings together technicians, slots, locations and interventions.
Real interface · test environment · demo data.
Enlarge screen View folder progress
Requests are grouped by status, with their subject, an overview of the exchanges and the team in charge.
Real interface · test environment · demo data.Applications, data and connectors.
Uses, recipe and support.
Organization, instructions and returns.
A direction to keep the project as a whole
The development of a platform requires different skills: interfaces, data, connectors, processing, hosting and business uses. Technical management gives consistency to these interventions and links decisions to expected operation.
We define the scope with business contacts, identify dependencies and organize the steps. Developers and specialists have a common context to understand what they are building and how their contributions fit together.
Manage developers and coordinate specialists
Patrice Salib's career path includes the integration of internal developers and the coordination of independents specialized in the Reymann collaborative platform project. The overhaul projects in 2014 and engine upgrades in 2018 extend this driving experience.
Coordination concerns the distribution of interventions, interfaces between components, blocking points and verifications with production. Discussions with developers must result in understandable decisions and results that users can evaluate.
Connecting the technical team to the teams that produce
In a company of more than 100 people like Reymann, the tools were in contact with graphic designers, image teams, photoengraving, traffic and customer contacts. The technical choices had to take into account this organization and manufacturing deadlines.
This experience provides practice in dialogue between professions: specifying a request, understanding its urgency, examining its impact on the other stages and preparing changes with the people concerned.
A 2017 architectural study to organize applications and their exchanges.
Enlarge Design document from January 2017: study of exchanges between Excel imports, PIM Akeneo, images in Nextcloud and Rey’actif production platform.
Architecture study · design document · 27/01/2017Organize work with offshore partners
Management goes beyond software development. The course also includes research, training and coordination of offshore partners for images and layout. Instructions, resources, schedules and feedback must give continuity to distributed work.
Scheduling, queues, and release management connect teams. Preparing submissions, identifying corrections and transmitting practices are as important as transferring files.
Lead developments and support commissioning
A redesign may involve an interface, engine, database or several services at a time. We are preparing the recovery steps and the checks necessary to ensure that developments reach a workable path.
The recipe, user support and production monitoring extend the management. The objective is to give teams a coherent solution, clear responsibilities and useful information to develop it.
Manage developers and project dependencies.
The technical management role brings together business teams, developers and specialists to maintain consistency from framing to production.
Enlarge the diagram - 01Set expectations ↓
Business need
Uses and priorities
Journey • constraints • challenges - 02Organize the production ↓
Technical framework
Perimeter and architecture
Data • dependencies • steps - 03Checking uses ▼
Developers
Implementation and integration
Team • partners • offshore - 04Preparing for commissioning ▼
Recipe
Check the routes
Scenarios • differences • arbitrations - 05Develop tools ↓
Put into production
Preparing for exploitation
Deployment • monitoring • continuity - 06
Developments
Organize returns
Uses • maintenance • priorities
Enlarge the diagram Frame
Define expected results and responsibilities.
Coordinate
Treat dependencies between developers and specialists.
Transmit
Make decisions and operating conditions understandable.
Projects and concrete situations.
Reymann : pilot developers and specialists
Founder's Experience · Reymann
Building an editorial platform requires an organization capable of linking internal developers, specialized partners and production teams. The Reymann route gives concrete reality to this piloting.
Explore the caseClestra: preparing an international web overhaul
Founder's Experience · Reymann
Technical reference for a recasting project involving WordPress, several regions, accommodation constraints and a need for liaison with CRM.
Explore the caseYour job deserves
the right tools.
A specific need, a software to evolve, a project to frame.