The company is preparing a new web service where customers and outside partners can run projects together.
On the website, customers can request work, submit the materials it needs, exchange comments with the assignee and receive the finished results.
Working from the plan, the development team starts sorting out the work to build.
PROJECT KICKOFF
Customer workspace
Launch in56 days
A new web service where customers and the company run projects together
PRODUCT REQUIREMENTS
AreaService requirements
Users and organizationsSign-up, sign-in, organizations and roles
Project managementRequests, project creation and status
CollaborationAssignments, comments and history
File upload and downloadSubmitting materials, delivering results
DeliverablesReview, approval and completion
OperationsCustomer support and service operations
Project lead09:30
In eight weeks, real customers have to be able to use the service. We will settle the scope and the tech stack this week.
The team assigns an owner to each area and reviews the schedule.
The features that manage customers' work are the core of the service.
File upload and download are filed as a basic feature customers need to get their work done.
No one has yet checked how much work this feature really takes.
Live contextNow
56 days to launchWeek 1, Monday
Current task
Reviewing the service scope
Schedule
Week 01 — Week 08
Project lead
We will settle the scope and the tech stack this week.
Next
Finalize requirements
Week 1, Tuesday
It was never just one upload button.
The team designs the screen where customers submit materials on the website.
At first they thought it meant a file picker button and a progress bar.
But as they go through the real service requirements one by one, the scope starts to change.
REQUIREMENTS REVIEW
The feature as planned
Project files
Choose filesSelect files to upload
Upload
A basic feature that picks files and saves them to the server
The real requirements
File and folder selectionVaried data structures
Large filesSource data of tens of GB or more
Many filesThousands of files or more
Transfer progressProgress, speed, time left
Interruption and recoveryUnstable networks
User environmentsOS and browser support
Security and accessAuth, storage location, file policy
Workflow eventsLinking results to the service
File downloadLarge results and many files
Operations and maintenanceFixing errors, keeping up with change
Developer14:20
We can build a basic upload. But once we consider the data and environments customers will use, the scope changes.
For the customer, submitting a file is a single action.
For the team, it is an area that has to cover file handling, networks, error recovery, browser support, security and user experience.
Even after launch, they would have to keep up with new operating systems and browsers and fix the problems customers run into.
The team decides to review the scope of file transfer on its own.
Live contextNow
55 days to launchWeek 1, Tuesday
Current task
Reviewing file transfer needs
Schedule
Week 01 — Week 08
Developer
Once we factor in customer data and environments, the scope changes.
Next
Decide the tech stack
Week 1, Thursday
What do we build ourselves?
The team reviews all the development work for the service again.
The value the company wants to offer customers lies in project management and a professional place to get work done.
File transfer technology itself is not the core business of the service the company wants to build.
TECHNOLOGY DECISION
How the new web service is built
APPLICATION DEVELOPMENT
What the team builds
Customers and organizations
Projects and workflow
Assignments and collaboration
Review and approval of deliverables
The service's own user experience
FILE TRANSFER TECHNOLOGY
What runs on proven technology
Large and bulk file transfer
Transfer status and user interface
Network failure handling and recovery
Support for varied user environments
Linking service events and file transfer
Selected technologyINNORIX
Engineering lead16:10
Instead of building file transfer from scratch, let's use technology we can apply directly to our service. We will focus on the features our customers need.
The team decides to embed INNORIX's file upload and download technology in the web service.
Using existing technology does not make all the development work go away.
Connecting authentication, project data, storage locations, the user interface and workflow events is still the team’s job.
Rather than build everything itself, the team will finish the service by putting the right technology together.
Live contextNow
53 days to launchWeek 1, Thursday
Decision
Use INNORIX for file transfer
Schedule
Week 01 — Week 08
Engineering lead
Let's focus on the service's core features.
Next
Test it in development
Weeks 2–4, Week 2
The team tries a real file transfer.
Before the full integration, the team sets up a separate development environment.
It adds INNORIX and checks the basic file transfer the new web service needs.
File transfer integration test
Development environment
var box = innorix.create({
el: '#projectFiles',
transferMode: 'upload',
uploadURL: '/upload.jsp'
})
box.on('uploadComplete', function (p) {
// Record the result on the project
})
Test application
Project attachments
Upload filesAdd files
project_documents.zip620 MBCompleted
reference_assets.tar24.8 GBCompleted
source_materials/1,240 files, 12.6 GBCompleted
Transfer completed
Integration validation
File transferFile selection and resultsVerified
StorageStorage location per projectVerified
AuthenticationTransfer rights per userVerified
Workflow eventsCompletion and error eventsVerified
DownloadResult files by permissionVerified
The team checks that files can be sent and received correctly.
It also checks that data is stored by project and that the service can use the transfer results.
The transfer technology tested here will go into several screens of the customer-facing service.
Live contextNow
49 days to launchWeek 2
Current task
File transfer integration test
Schedule
Week 01 — Week 08
Developer
We are testing basic file transfer in the development environment.
Next
Add it to the service screens
Weeks 2–4, Week 3
File transfer is now inside the service.
The project management screens the team built are starting to take shape.
The screen where customers create a project has an area for submitting the materials the work needs.
The assignee’s work screen has an area for adding more materials, and the results screen has an area where customers download deliverables.
The team adds the file transfer each screen needs.
APPLICATION DEVELOPMENT PREVIEW
Customer workspaceProjectsAccount
WORKSPACE
Overview
Projects
Messages
Team members
Settings
Projects / New project
Create a project
Project name
Product development project
Project description
Review source materials and prepare project deliverables.
Requested completion date
June 30
Project filesAdd files
project_assets.zip24.8 GB
reference_documents.pdf12 MB
2 files selected
Create project
The team builds the design and project creation. The file transfer area runs on INNORIX.
The company decides how the service looks to its customers.
Where files are picked and how projects are submitted also follow the service’s own workflow.
Customers don’t go to a separate file transfer site. They do their work inside the service the team built.
Live contextNow
42 days to launchWeek 3
Status
Building service features
Schedule
Week 01 — Week 08
Developer
We are adding file transfer to the project and results screens.
Next
Connect workflow events
Weeks 2–4, Week 4
Customer work and files become one flow.
With file transfer tested, the team now builds the whole workflow customers go through in the service.
When a customer submits materials, the work has to reach the project assignee.
When the work is done, the customer has to be able to review the results and download the files.
APPLICATION WORKFLOW
Project Alpha
Completed
Create
Submit
Work
Deliver
Done
Current service screen
Project completed
The customer downloaded the deliverables.
Project AlphaCompleted
Internal service task
Archive project history
NextNext project request
Project activity
Customer created a project
Materials submitted
Assignee started work
Deliverables uploaded
Project completed
File transfer does not stand on its own.
The team ties the result of each transfer to the status of the work in the service.
When a transfer finishes, the needed checks run and the next task starts. Work cannot move ahead while a submission is still incomplete.
The team now focuses less on how files move and more on the order in which customers do their work.
Live contextNow
35 days to launchWeek 4
Status
Connecting the project workflow
Schedule
Week 01 — Week 08
Developer
When files are submitted, a task is created for the assignee.
Next
Test customer environments
FOUR WEEKS LATER
The service the team set out to buildis starting to take shape.
Customer workspaceDevelopment preview
Projects
12
In progress
5
In review
3
Completed
4
ProjectAssigned toStatus
Product developmentDesign teamIn progress
Reference material reviewTechnical teamIn review
Customer requestProject teamCompleted
Four weeks to launch. Now it is time to check that real customers can use it.
INNORIX in Practice
Week 1Monday
Weeks 5–8, Week 5
Every customer works in a different environment.
A web service does not only run in the environment the team uses.
Customers use different operating systems and browsers.
Some business customers cannot install software freely, and some submit large amounts of data often.
The team reviews transfer methods and user guidance with real customers' environments in mind.
USER ENVIRONMENT VALIDATION
Where customers use the service
EnvironmentWhat we checkStatus
Windows usersSupported browsers and transfer setupReviewed
macOS usersSupported setup and installationReviewed
Company-managed PCsInstall rights and security policyReviewed
Large-data customersDedicated transfer and recoveryReviewed
Dedicated file transfer
Project files
source_assets.tar82.4 GBReady to upload
Full features for large data on supported setups
Browser-based transfer
Project files
project_documents.zip240 MBReady to upload
A fallback where installing is not an option
The team sets up the service so that not every customer has to go through the same installation.
It checks the differences between the available transfer methods and prepares guidance and policies that fit each environment.
Customers should rarely need to understand file transfer technology just to use the service.
Live contextNow
28 days to launchWeek 5
Current task
Checking user environments
Schedule
Week 01 — Week 08
Developer
We are matching transfer methods and guidance to each customer's setup.
Next
End-to-end testing
Weeks 5–8, Week 6
The team replays a real customer's day.
With each feature built, the team starts end-to-end testing.
Instead of ticking off a feature list, it replays a day in which a real customer uses the service.
It tests every step, from the morning when the customer creates a project to the afternoon when the assignee uploads results and the customer receives them.
END-TO-END TEST
Replaying a customer's day
09:00Customer signs inCompany account and project accessPassed
09:10Project createdRequest details and file selectionPassed
09:15Materials submittedLarge and bulk file uploadPassed
09:28Network dropsPause and resume on supported setupsPassed
10:20Materials receivedFile checks and workflow statusPassed
10:30Assignee starts workFile access and project managementPassed
15:00Deliverables uploadedWork results and filesPassed
15:30Customer gets resultsDownload rights and resultsPassed
16:00Project completedHistory and final statusPassed
Exception test
Connection lost during a submission
source_assets.tar42 GB / 42 GB
Resumed from 18.6 GB, Completed
Project status, Source data received
The tests cover not only normal use but also a range of exceptions.
They check what happens when a transfer stops, user rights change, storage runs low or a customer submits the same project again.
The team separates what the transfer technology handles from the business rules the service has to implement itself.
Before launch, they check as many of the problems customers might hit as they can.
Live contextNow
21 days to launchWeek 6
Current task
End-to-end and exception tests
Schedule
Week 01 — Week 08
QA engineer
We are also testing what happens when the connection drops mid-upload.
Next
Final UX improvements
Weeks 5–8, Week 7
The team polishes the service.
The main features of the service are built.
The team improves the screens and user experience so customers can get their work done more easily.
They check for unnecessary steps in the request flow, whether assignees can find their projects easily and whether reviewing results feels intuitive.
FINAL PRODUCT REFINEMENT
Making customers' work easier
Customer project requests
New project
Project templateProduct reviewTemplates for frequent requests
Requested completionSelect date
Simpler repeat requests
The assignee's workspace
My tasks
Project AlphaToday
Project BetaTomorrow
Project GammaFriday
Clearer priorities for assignees
Project review
Review results
Version 03Updated todayApproveRequest changes
Easier review and approval
Customer and assignee communication
Project activity
Project managerThe updated deliverables are ready for review.Customer, 10:42Thank you. We will review them today.
Better history and messaging
What the team set out to build was never a file transfer program.
It was a web service where customers and the company could work together more easily.
With launch close, the team is focused on making that service as good as it can be.
Live contextNow
14 days to launchWeek 7
Current task
Improving the user experience
Schedule
Week 01 — Week 08
Product designer
We are looking for unnecessary steps in the request flow.
Next
Final launch check
Weeks 5–8, Week 8, Monday
The service goes live this week.
The last development meeting before launch takes place.
The development and operations teams make a final check that the service is ready for real customers.
RELEASE READINESS
Customer workspace
Launch in4 days
AreaTeamStatus
Customer and company accountsDevelopmentReady
Project and task managementDevelopmentReady
Customer user experienceProduct designReady
File transfer and workflowDevelopmentReady
Authentication and securitySecurityReady
Production and storageInfrastructureReady
Service monitoringOperationsReady
Customer support readinessCustomer successReady
Project lead
Every launch condition is met. We will open the service this Friday at 9 a.m.
The team reviews the final test results and deploys the service to production.
They check the network and storage customers will submit to, and confirm that files reach the right place under real customers' accounts and permissions.
The schedule written eight weeks ago now ends in a launch.
Live contextNow
4 days to launchWeek 8, Monday
Current task
Final launch check
Schedule
Week 01 — Week 08
Project lead
We will open the service this Friday at 9 a.m.
Next
Deploy to production
WEEK 08, FRIDAY
At 9 a.m.,the new web service goes live.
https://workspace.example.comLive
Customer workspaceAboutSign in
A better way to work together
Your projects. Your team. One workspace.
Create projects, share materials, collaborate with your team and review deliverables.
Create your workspace
Your projectsNew project
Product reviewIn progress
Material developmentIn review
Design projectCompleted
09:00 Service live, First visitor arrives
Eight weeks ago this service was a plan on paper. Now real customers can use it.
INNORIX in Practice
Week 1Monday
Launch day, 09:24
The first customer uses the service.
A new customer has created a company account.
In the web service, the customer creates a first project and submits the materials it needs.
FIRST CUSTOMER PROJECT
09:24
Customer workspaceMy account
Projects / New project
Product development request
Project description
Please review the submitted reference materials and prepare the initial deliverables.
Project files
reference_materials.zip2.4 GBCompleted
product_specifications.pdf18 MBCompleted
design_assets.tar16.8 GBCompleted
Project submitted
Your project has been assigned to our team.
Service operations09:32
The first customer's project came in without issues. The assignee is checking the files and starting work.
The customer does not need to know what technology went into the service.
What matters to them is that they can request work, submit materials and run the project with the assignee.
File transfer is just one natural step in the customer's work.
Live contextNow
Now 09:24Launch day 09:24
Service status
Live
Schedule
Week 01 — Week 08
Service operations
The first customer has created a project.
Next
Support customer projects
Launch day, 17:30
The team's first operations meeting
The first day of operations is winding down.
The team reviews the feedback customers left while using the service.
The improvements customers asked for are about the business features the team built.
FIRST DAY CUSTOMER FEEDBACK
New features customers asked for
Customer feedback, 11:42It would help to copy an earlier request into a new project.
Customer feedback, 14:18We would like other people at our company to review and approve projects too.
Customer feedback, 16:25Can we get project updates by email?
Next development
Project duplicationProduct backlog
Internal approvalProduct backlog
Work notificationsProduct backlog
Launch is not the end of development.
As real customers use the service, new features for the team to build keep appearing.
The team builds its next development plan from customer feedback.
Live contextNow
Now 17:30Launch day 17:30
Customer feedback
3 items received
Engineering lead
We will feed customer feedback into the next plan.
Next
Plan the next release
After launch, 3 months later
The team builds what customers ask for.
The new web service keeps evolving.
As customers request projects again and again, they need work types and approval steps for each company.
The team builds these requirements into the service.
PRODUCT EVOLUTION
Development since launch
Month one
Version 1.1
Project templates
Product review
Material development
Custom template
Project templates for repeat work
Month two
Version 1.2
Approval workflow
Project owner, Reviewed
Team manager, Approved
Customer, Pending
Approval process for business customers
Month three
Version 1.3
Notifications
Project assigned
Review requested
Project completed
Work notifications for customers and assignees
Shared file transfer technology
INNORIXExisting integration reused
New features reuse the existing file transfer technology, with integration added where business rules changed.
Each new feature does not need file sending and receiving built from scratch.
The permissions, storage policies and file transfer events a new feature needs are still set up separately.
The team's plans keep changing around what customers need from the service.
Live contextNow
Version 1.33 months later
Current task
Building customer requests
Developer
New features reuse the same file transfer technology.
Next
Expand operations
After launch, 6 months later
Customers no one expected start to arrive.
More business customers are using the service.
Some use far larger data and far more files in their projects than anyone expected.
The team reviews how real customers use the service and improves the operating environment.
SERVICE OPERATIONS
Real customer projects
Project typeData sizeFiles
Document review240 MB18
Product development16.8 GB124
Source data analysis186 GB2
Design data review82.4 GB324
Large-scale data management420 GB8,640
Operations team
We review data use, storage and network capacity per customer and adjust our operating policies.
When the team first designed the service, it could not predict every customer's data size.
The service grows with its customers.
Within what the adopted technology supports, the company checks new customer needs and improves its infrastructure and service policies to match.
Live contextNow
Largest project 420 GB6 months later
Current task
Improving operations
Service operations
We are reviewing data use and storage per customer.
Next
Adjust operating policies
After launch, 1 year later
The team prepares another web service.
The first web service is running smoothly.
The company is planning a new service for its outside partners.
It serves a different kind of customer and different work, and needs a different user experience from the first service.
The team starts listing the development work for the new service.
ONE YEAR LATER, NEW PROJECT
Service in operation
Customer workspace
Customer projects and collaboration
Customer projects
Project requests
Review & approval
Project results
Project filesUpload & Download
New service in development
Partner workspace
Partner work and file management
Partner organizations
Shared assignments
Partner submissions
Delivery management
Partner filesUpload & Download
Tech review for the new service, Developer
We can reuse the file transfer technology and integration experience from the first service. We will set it up around partners' workflows and permissions.
A year ago, planning the first web service, the team started by working out how to build file transfer.
This time it already has the experience and test results from integrating file transfer into a service.
The new service needs different features, but the same technology can be used again.
This time, the team starts with what service to offer its new customers.
Live contextNow
New project: Partner workspace1 year later
Current task
Planning the partner service
Developer
We will reuse the same file transfer technology in the new service.
Next
Design the new workspace
ONE YEAR LATER
From the start, the teamwanted to build its own service.
The meeting a year ago
Building a new service
56 days to launch
The team's question
How do we even build sending and receiving files?
Service scope and technology review
The meeting today
Building another service
Partner workspace
The team's current work
What work experience should we give new customers?
Customer needs and service experience design
Eight weeks before launch, the team chose the technology for its new web service.
A year on, the team is still building for its own customers and service.
To launch a new web service,you don’t have to build file transfer first.
INNORIX
THE TECHNOLOGY BEHIND THIS STORY
Embedded Web Upload & Download
INNORIX lets you embed file upload and download directly in web services and software.
It lets development teams focus on features for their own service and customers, not on building file transfer technology.