01 · Starting point
Situation
A distributed rollout team had to onboard new members and manage daily tasks while operating a live SCCM landscape with packaging, updates, App-V and support reliably.
Constraints
- Changes within an already established IT environment
- Short, clearly scoped engagement
- Internal system and operating details remain confidential
02 · Responsibility
My scope of responsibility
As team lead I coordinated onboarding, task allocation, helpdesk alignment and reporting with central IT in France. In parallel I took technical responsibility for SCCM operations, software distribution, auditing and escalations.
- I onboarded team members, allocated tasks and coordinated the helpdesk and the main site in France.
- I monitored SCCM, software packaging, App-V, updates, WSUS, distribution points and status messaging.
- I handled 3rd-level escalations, security and permission issues as well as file server migrations.
03 · Technical work
Documented scope of work
Key decisions
Run team management and technical operating data in one shared daily rhythm. Rollout decisions only hold up when task allocation, status reports, incidents and technical platform states are viewed together.
- I onboarded team members, allocated tasks and coordinated the helpdesk and the main site in France.
- I monitored SCCM, software packaging, App-V, updates, WSUS, distribution points and status messaging.
- I handled 3rd-level escalations, security and permission issues as well as file server migrations.
04 · Technical context
Technology in use
SCCM
SCCM was part of the documented toolset in this Leadership engagement.
AdminStudio
AdminStudio was part of the documented toolset in this Leadership engagement.
App-V
App-V was part of the documented toolset in this Leadership engagement.
WSUS
WSUS was part of the documented toolset in this Leadership engagement.
ITIL
ITIL was part of the documented toolset in this Leadership engagement.
3rd-Level Support
3rd-Level Support was part of the documented toolset in this Leadership engagement.
05 · Factual basis
Evidence and limits
Team coordination, rollout reporting and technical SCCM operations were run under one shared delivery responsibility.
- Role
- Team Lead
- Period
- April 2013 — September 2013
Lesson from the engagement
Technical leadership becomes effective when prioritisation is not separated from real operational and support signals.
Confidentiality note: Internal architecture and operating data of this engagement are not published.