About NorroSoft
Different disciplines. One view of the work.
NorroSoft began as a group of friends working in software development, systems administration and digital transformation. That combination shapes our approach: a feature needs a useful interface, sound business rules and an environment that can run it. We bring those questions together early, while your team brings the knowledge of customers, processes and priorities that no specification can fully capture.
A project can begin with an everyday problem, an existing application or a product idea that needs definition.
Our working principles
Make the important decisions together.
Clear requirements and regular reviews give both teams a common basis for the work.
Talk through your requirementsStart with the people
Follow the task from the user’s point of view. Find out who enters information, who approves it and what happens when the usual process does not apply.
- User responsibilities
- Everyday tasks
- Exceptions and priorities
Look beyond the screen
Consider the systems behind each action: where information comes from, which rules apply and what another application needs to receive.
- Data movement
- Connected applications
- Operating requirements
Review something concrete
Use a design, prototype or working feature to test assumptions together. Record the feedback and agree how it affects the scope and the next stage.
- Design discussions
- Feature demonstrations
- Agreed changes
Prepare for everyday use
Discuss release, administration and maintenance while development is underway. A handover should explain the setup and the responsibilities agreed for it.
- Release preparation
- Useful documentation
- Support responsibilities
Working with your team
The detail often appears in the discussion.
An approval screen may look complete until someone asks who handles an absent manager’s requests. A report may need a different date rule from the application that supplies its data. Reviews bring these details into view. We work through their effect on the requirements, record the decision and agree what belongs in the current release.
- Include the people who know the process and can make decisions.
- Use real tasks to review whether a feature serves its purpose.
- Keep changes, open questions and release priorities visible.
- UnderstandExplain the task, the people and the practical constraints.
- ExploreUse a design or technical investigation to examine the options.
- ReviewDiscuss the proposed behaviour with the people who will use it.
- AgreeRecord the decision and its place in the development scope.
These examples explain the approach; they are not client case studies.
What to expect
A shared direction at each stage.
We define the deliverables and review points around the project you commission.
Agree the starting point
Bring business priorities, existing systems and unanswered questions into one brief. Decide which assumptions need investigation before development can be planned.
What you leave withScope, priorities and open questionsReview the application
Examine the work in agreed stages, including complete user tasks and the connections between features. Use the feedback to guide development and testing.
What you leave withReviewed features and agreed next stepsPrepare the handover
Explain the agreed setup, release steps and administration tasks. Confirm how maintenance, issue reporting and future improvements will be handled.
What you leave withRelease guidance and responsibilities
What does NorroSoft do?
NorroSoft works across custom software, web and mobile applications, SaaS products, AI, data and cloud services. Technology consulting can help define an uncertain requirement or assess an existing system before deciding what to build or change.
Can we begin without a technical specification?
Yes. Start with the people who need the software, the task they want to complete and the difficulty they face today. Examples of the current process help us identify requirements and decide whether an initial review or prototype would be useful.
Can you work with our existing application and team?
Yes. We first discuss the application, available access and who is responsible for it. The scope can then define the changes, integrations or review needed, together with the division of work, handover and any ongoing support arrangements.
Your next step
Let us get to know the work behind your project.
Tell us about the people, process or product you want to support. We can help define a practical starting point.