IT project management with every milestone in view
Migrations, rollouts and new systems run well when someone holds every thread. Visgenix takes over project management and steers schedule, budget, risks and quality through defined milestones and acceptance, from planning to go-live. Deviations surface early. You decide how to respond, with us at your side.
- A free 30-minute first call, no strings attached
How projects stay under control
Jira: tasks and progress
Requirements, tasks, bugs and decisions are planned and prioritized in a traceable way. For every task it is clear whether it is open, in progress or done.
Scrum or Kanban, to fit the project
Iterative software projects run with a backlog, sprints, reviews and retrospectives. Migration and infrastructure projects tend to run in phases with milestones.
Git and Bitbucket: traceable changes
Code and, where it makes sense, infrastructure configurations are versioned. Changes go through reviews and can be tied to individual tickets.
CI/CD: reproducible releases
Builds, tests and deployments are automated where it makes sense. That makes every release traceable and repeatable.
Documentation and decisions
Architecture decisions, acceptance, risks and important changes are documented while the project runs, not in a rush shortly before it ends.
Services in IT project management
From the project plan to go-live support. Order the whole package or single services.
Project management
You know where things stand every week: a fixed contact person, a project plan with milestones and owners and a weekly status report. Whether we work in an agile or phase-based way depends on the project.
Change management
A changeover goes more smoothly when people know what is coming. Employees learn before the changeover what changes. The affected areas get fixed contacts and key users. A communication plan sets out who is informed when.
Rollout planning
Sequence and time windows, a pilot group and rollout waves, all in one rollout plan. Every stage has a fallback point.
Training
Your team learns the systems it will work with afterwards. The quick guides stay in your company.
Documentation
At project close you receive operations documentation: system overview, responsibilities, technical configurations, administration paths and operating procedures. It becomes your property. Credentials belong in a password and secret manager, not in a document.
Quality assurance and acceptance
Acceptance criteria and tests are defined for each work package beforehand. Results count as complete only after passing the check and documented acceptance.
Go-live support
For a stabilization phase defined beforehand after go-live, your fixed contact person stays available. For prioritized incidents the response time of your managed IT tier applies: Basic from 4 hours, Plus from 2 hours, Pro from 1 hour. That is the response time, not the time to resolution.
Which method fits which project
Software development
Scrum, Kanban or iterative releases with a backlog, short cycles and a review after each cycle. Fits when requirements become concrete during the project.
Migration and infrastructure
Phases, milestones, change windows and rollback. Fits a clearly bounded scope, such as a Microsoft 365 migration, servers or network.
Rollouts
Pilot group, then waves, then full introduction. Fits clients, telephony, Intune and security policies.
Scope, price and changes
Requirements and scope
Requirements are documented before implementation, prioritized and given acceptance criteria.
Price per work package
For each clearly bounded work package we agree the price up front. The price covers the agreed scope, not every later requirement.
Changes to scope
Additional effort outside the agreed scope is described, rated and approved by you in writing before implementation.
Two kinds of change
Change control manages changes to scope, budget and requirements. Change management accompanies employees through communication and training. We run both separately.
How an implementation project runs
Four stages, each with a result you review.
Kick-off and scope
The kick-off brings the project team together. Goals, scope and success criteria are defined jointly.
Planning and design
Detailed planning follows, with test scenarios and acceptance criteria. Risks, open decisions and dependencies are documented centrally.
Implementation, tests and acceptance
We configure and integrate the systems. After review and tests, your departments check the environment and accept it.
Go-live and stabilization
After the switchover comes a stabilization phase defined beforehand. At the end you receive the operations documentation.
Testing and acceptance
Test or pilot environment
Critical changes are tested before the switch to production, as far as technically possible, in a test or pilot environment.
Pilot group
A defined pilot group validates new systems first. This is particularly useful for Microsoft 365, Intune, telephony, clients and security policies.
Rollout waves
The rollout follows, depending on the project in controlled waves. Every wave has a fallback point.
Acceptance
Acceptance criteria and definition of done are set up front. Technical tests and the business acceptance test (UAT) end with an acceptance record.
What you can see at any time
Backlog
What still has to be implemented.
Current work package
What is being worked on right now.
Milestones
When the next results are expected.
Risks
What endangers time, budget or quality.
Decisions
Which open points you need to decide.
Budget
Ordered, used, still open.
Taking over a project that has stalled
A stalled project can get back on course. It starts with a project analysis that records status, risks and open points. From there a recovery plan takes shape. Clear milestones and status reports then steer the project again.
Unclear scope
Nobody can say what exactly is still to be delivered.
Blocked provider
The current provider no longer moves things forward.
Missed schedule
Milestones have slipped without a new plan.
Budget out of control
Costs grow without a clear link to results.
Nobody knows the status
There is no reliable view of progress and risks.
Technical problems
Open defects or architecture issues hold the project up.
Frequently asked questions about IT project management
Related consulting
Strong delivery rests on sound decisions about strategy, infrastructure and security.
- LeistungIT strategy and roadmapGoals, architecture and priorities, settled with you before delivery starts.
- LeistungIT infrastructure consultingNetwork, servers and cloud, planned as the ground your project stands on.
- LeistungIT security consultingSecurity requirements built into the project plan from the start.
- LeistungManaged IT (German)After go-live, Visgenix can take over ongoing operations on request.
Put your IT project on a steady course
In the first call we classify your starting point and tell you whether project management, a recovery plan or a bounded work package fits.