WALTER TOOLS · TIBP

How we work, and how we build the site.

An internal walkthrough — what we own, who's on the team, and how a request becomes reality.

Daniel · IT Product Owner · Walter Tools
AGENDA

Three chapters.

Scope. People. The way we work.

  1. 01What we ownThe full scope of our web platform.
  2. 02Who's on the teamThe people behind it — and who does what.
  3. 03How we workScrum, the request pipeline, the weekly rhythm, and what makes a great requirement.
01 · SCOPE

What we own — and what we plug in.

A stack: what we build, what we integrate, and the layer that holds it all up.

BUILT IN TIBP

We design it. We build it. We deploy it.

Marketing
Content marketing
Marketing & campaign pages
Commerce
Toolshop
E-commerce platform
Online catalogue
Browsing & technical specs
InnoTime
Project management software
Web Assembly
Online tool-assembly builder
Portals
Recycling Vendor Portal
Customer used-tool sell-back
Walter Connect
Channel-partner extranet
INTEGRATED

Built elsewhere · we plug it in.

Walter GPS
E-Library
CutView
Walter Xpress Online
CIAM · FOUNDATION

Identity & access — the layer everything sits on.

02 · PEOPLE

Who's on the team.

A small core team — plus four developers in Sweden who actually build it.

Core Team
Anastasios Eltzidis
Team lead
Alexander Venter
Walther Mann
Daniel Cozma
Bianca Asurdoaei
Moayad Shaaban
Intern
Coordinates & supports external teams
BUILDS TIBP
TIBP
Sweden
Administration
Max Wikman
Sara Svedberg
Development
Mana · Jonas · Martin · Hans-Eric
(mixed roles)
BUILDS · WALTER GPS
IPS
Czech Republic
Administration
Jiri Hnat
Development
Igor Menovsky
BUILDS · E-LIBRARY
Cominto
Düsseldorf
Administration
Sebastian Kamp
Development
.NET · iOS · Android
BUILDS · CUTVIEW
Freelancer
Global
Development
Marcus Kettrucat
03 · WAY OF WORKING 1 / 3

The pipeline.

From your idea to live on site — typically ~1.5 months. Most of that is preparation, not coding.

  1. 01
    Submit

    Power Apps form on the intranet. The front door. Always.

  2. 02
    Triage

    Heads of IT decide which team(s) pick it up.

  3. 03
    Refine

    Several meetings. Data, design, content, product info. Most of the 1.5 months lives here.

  4. 04
    Build

    Weekly Scrum sprints. Power Apps → Azure DevOps.

  5. 05
    Live

    Production deploy. Tuesday.

03 · WAY OF WORKING 2 / 3

The weekly rhythm.

Inside “Build” — this is the cadence. Development runs the whole workweek; testing spans Wednesday through Monday evening, weekend included.

MON
Stand-up
TUE
PROD deploy
WED
TEST deploy
window opens
THU
Stand-up
FRI
—
SAT
—
SUN
—
MON*
Testing
closes (eve)
DEVELOPMENT Mon → Fri · the entire workweek
TESTING WINDOW Wed → Mon evening · spans the weekend
03 · WAY OF WORKING 3 / 3

What makes a great requirement.

The single biggest accelerator we have. The clearer the request, the faster we move.

01

Thoughtful

Written with care, not in a rush. The why is as clear as the what.

02

Thorough

Covers the main flow — and the edge cases. The boring details matter.

03

UI/UX-aware

Wireframes, sketches, references — or a clear vision of how it should look and feel.

“
A well-shaped requirement is the single biggest accelerator we have. When you bring clarity, we bring speed.
Daniel · IT Product Owner · Walter Tools