Software development project management: so things get delivered.
Software development project management from people who build software themselves: requirements and backlog, your in-house team or an external agency, quality assurance and one status everyone shares.
Technically solid
We read code, understand architecture and can tell whether an estimate has substance.
Team or agency
We manage in-house development as well as external agencies and nearshore teams.
Part-time works
Often 1–3 days per week are enough to secure pace and quality.
What our project management covers.
-
Requirements and backlog
Translate goals into buildable requirements, prioritise them and describe them so developers can implement them, with no room for interpretation where it gets expensive.
More on this
What starts as “we will clarify that during the sprint” ends as a debate about extra charges. Without a solid backlog the team builds fast, though rarely the right thing.
-
Vendor and team management
We manage sprints, milestones, dependencies and capacity, for in-house development as well as for an agency or mixed teams.
More on this
We assess proposals and estimates and insist on traceable progress. For the agency the collaboration usually improves, because clear requirements save their time too.
-
Architecture and code reviews
Spot-check reviews of architecture and code quality. Maintainability gets verified before it surfaces during a vendor change.
More on this
We develop ourselves: web, mobile with Flutter, desktop and integrations. That is where our judgement on estimates and technology decisions comes from.
-
Quality, budget and schedule
Test concept and acceptance criteria come before delivery. Effort runs against progress, and risks get named early.
More on this
Without schedule and risk management, a delay only becomes visible once it can no longer be recovered. Management, business and development all work from the same status.
Your project delivers demos, never results?
When the deadline slips slice by slice and nobody steers the agency, 1–3 days of steering per week are often enough.
How the collaboration works.
First call and goals
Understand the initiative, status, team and bottlenecks, then say what is missing.
Review and assessment
Examine backlog, plans, codebase and contracts, then state where the project stands.
Define role and scope
Capacity in days per week, responsibilities and goals, written into the proposal.
Steering and handover
Backlog, deadlines and quality run through one head, then your team takes over.
Frequently asked questions about software project management.
Do you work agile or classic?
We usually run software project management agile with Scrum or Kanban, embedded in a frame of milestones and budget. Management needs dates, the team needs focus.
Can you manage our external agency?
Yes, that is one of the most common engagements. We assess proposals and estimates, insist on traceable progress and verify quality. Clear requirements save the agency time too.
Is part-time project management enough?
Often, yes. Many mid-market projects need consistent steering in the right places, typically 1–3 days per week. We clarify the actual need in the first call.
How technical are you really?
We develop ourselves: web, mobile with Flutter, desktop and integrations, and we run our own products. Code reviews and architecture discussions come out of that practice.
Do you also take on the product owner role?
Yes, where it fits: prioritising requirements, maintaining the backlog, running acceptance. Business decisions stay with you, we prepare them and see them through.
What does external project management for software projects cost?
We bill by daily rate and agreed capacity. After the first call you receive a proposal with role, scope and duration, cancellable at any time if we fail to deliver.
Give your software project a head.
Describe your project and its status. You get an assessment of whether an external project lead would speed it up.
Request project management.
Describe project, team and timeline. We come back with an assessment of role, capacity and availability.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.