News

Planning a Software Project? 7 Things to Put in Your Brief Before Development Starts

Most software projects that go wrong do not fail because of the code. They struggle because nobody wrote down clearly, at the start, what the system was supposed to do, who would use it and what “finished” looks like. A good project brief fixes that. It does not need to be long or technical. It just needs to answer the right questions, so that you and your development team are building the same thing.

Whether you are planning a website, a web application or a mobile app for your organisation in Bhutan, here are seven things to put in your brief before development starts.

1. The problem you are solving

Start with the “why”, not the features. Describe the problem in plain language: paper forms that get lost, customers who cannot find information, staff re-typing the same data into several spreadsheets. When the problem is clear, a developer can often suggest a simpler solution than the one you first imagined.

2. Who will use it

List the different types of users: staff, managers, customers, partners, administrators. For each group, note what they need to do and how comfortable they are with technology. A system used mostly on mobile phones by field staff needs a very different design from one used at office desktops.

3. The must-haves and the nice-to-haves

Write your feature list in two columns. Must-haves are the things the system cannot launch without. Nice-to-haves can wait for a second phase. This one step does more than anything else to keep timelines and budgets realistic, because it lets you launch something useful sooner and improve it based on real feedback.

4. Data, existing systems and integrations

Note what data the system will store, where that data lives today and which existing systems it must talk to, such as accounting software, payment gateways, SMS or email services. Mention any data you already have in spreadsheets that will need to be moved across. Integrations are often the most time-consuming part of a project, so it is better to surface them early.

5. Security, access and privacy

Think about who should see what. Do different users need different permission levels? Does the system hold personal or financial information? How will data be backed up? Writing these expectations down at the start is far easier than adding security after the system is built.

6. Content, language and branding

Decide who will provide text, photos and documents, and whether the system needs to support Dzongkha as well as English. Share your logo, colours and any existing brand guidelines. Missing content is one of the most common reasons websites and apps launch late.

7. Life after launch

A system is never truly “done”. Plan for who will add content, manage users and handle day-to-day questions once it goes live. Ask how updates, security patches, hosting and backups will be handled, and what training your staff will need. Agreeing on this up front avoids surprises a few months later.

Keep it simple and keep it shared

Your brief can be a few pages in a shared document. What matters is that the people who will use the system help write it, and that it is reviewed with your development team before any design or coding begins. Expect it to change a little as you learn more; the point is to start from a shared understanding rather than assumptions.

Talk to eDruk about your project

eDruk Private Limited has been developing software in Bhutan since 2004, including websites, web applications and mobile apps, along with technical consultation to help organisations plan their projects. If you have an idea but are not sure where to start, we can help you shape it into a clear brief and a practical plan.

Email us at edruk@edruk.com.bt, call +975 2 332277, or visit www.edruk.com.bt.

News

Before You Buy or Build: 7 Ways Technical Consultation Keeps ICT Projects on Track

Many ICT projects run into trouble long before any equipment arrives or any code is written. The problems usually start earlier: a requirement that was never clearly written down, a specification copied from an old document, or a purchase made without checking how it fits with what is already installed. Independent technical consultation at the planning stage helps you avoid these mistakes and spend your budget on the right things.

What technical consultation actually means

Technical consultation is simply getting experienced advice before you commit. It can cover a new software system, a website or mobile app, an office or campus network, fibre links between buildings, CCTV, or automation such as gates and doors. The goal is to turn a general need (“our network is slow” or “we need an online system”) into a clear, practical plan that suppliers and your own team can follow.

1. Start with the problem, not the product

It is tempting to begin with a shopping list: a new server, more access points, a bigger firewall. A good consultation starts one step back. What is not working today? Who is affected, and when? What should be different after the project? Clear answers often show that the real fix is smaller, or different, from what was first assumed.

2. Understand what you already have

Before adding anything new, take stock of existing equipment, cabling, software licences and systems. A simple site survey and inventory can reveal hardware that can be reused, bottlenecks that need attention first, and compatibility issues that would otherwise appear only after installation.

3. Write requirements people can check

Vague requirements lead to vague results. Instead of “fast internet for all classrooms”, describe the number of rooms and users, the kind of work they do, and what “working well” looks like. For software, list the main tasks users must be able to complete. Requirements that can be checked make it much easier to compare offers fairly and to accept the finished work with confidence.

4. Plan for the whole life of the system

The purchase price is only part of the picture. Think about power and UPS needs, spare parts, warranty and support, software updates, staff training and who will look after the system day to day. A system that is easy to maintain locally is often a better choice than one that looks impressive on paper.

5. Keep security and backups in the plan from day one

Security is far easier to build in than to add later. Decide early how users will log in, how data will be backed up, how the network will be separated (for example, staff and guest Wi-Fi), and who has administrator access. These choices shape the design and are hard to change once everything is running.

6. Phase the work sensibly

Large projects are easier to manage in stages. A phased plan lets you fix the most urgent issues first, learn from the early stages and spread costs over time, while making sure each stage fits the overall design.

7. Check the work at handover

Finally, agree in advance how the finished work will be tested and documented. Network diagrams, cable labels, configuration backups, user guides and admin credentials handed over properly will save a great deal of time and frustration later.

How eDruk can help

eDruk Private Limited has been working in Bhutan’s ICT sector since 2004, across software and app development, networking and fibre-optic infrastructure, and IoT and automation. If you are planning a new system, upgrading your network or preparing an ICT requirement, we are happy to talk it through with you and help you build a clear, practical plan.

Contact us at edruk@edruk.com.bt, call +975 2 332277, or visit www.edruk.com.bt.

News

Connecting Buildings with Optical Fibre: 6 Steps to Plan a Reliable Link

When an organisation grows beyond a single building, the network has to grow with it. A second office block, a hostel on the other side of a campus, a warehouse down the road or a site office in a remote valley all need a link that is fast, stable and easy to maintain. In many cases, the right answer is an optical fibre link. Here is a practical guide to planning one well.

Why fibre for links between buildings?

Copper Ethernet cable works well inside a building, but it has a limited reach and can be affected by electrical interference and lightning-related surges when run outdoors between structures. Optical fibre carries data as light, so it is not affected by electrical interference, does not conduct electricity between buildings, and can cover much longer distances. It also leaves room to grow: the same fibre can usually carry higher speeds later by upgrading the equipment at each end.

1. Start with what you need today and tomorrow

Before choosing cable or equipment, write down what the link will carry: staff computers, Wi-Fi, CCTV, phones, servers or shared applications. Think a few years ahead too. Pulling cable is often the most disruptive part of the job, so it usually makes sense to install more fibre cores than you need right now, keeping spares for future services or as a backup.

2. Choose the right type of fibre

Single-mode and multimode fibre suit different distances and equipment. Single-mode is the common choice for longer runs and campus or inter-building links, while multimode is often used for shorter runs inside data rooms. The cable construction matters as well. Aerial routes on poles need cable designed for that purpose, such as ADSS (all-dielectric self-supporting) cable, while underground routes need cable and ducting suited to burial. A good design matches the cable to the route, not the other way round.

3. Survey the route carefully

Bhutan’s terrain makes route planning especially important. Steep slopes, rivers, roads, landslide-prone areas and seasonal weather all affect where cable can safely go. A site survey should confirm the path, the pole or duct positions, crossing points and any permissions needed from landowners or authorities. Skipping this step is one of the most common causes of delays and rework.

4. Plan the termination points

Every fibre link needs a tidy, protected place to end. Fibre distribution panels (FODPs) in each building, joint enclosures where cables are spliced, and properly labelled patch cords make the network far easier to troubleshoot. The equipment at each end, such as switches with the correct optical modules, must match the fibre type and distance.

5. Test and document everything

Once installed and spliced, each fibre core should be tested so you know the link performs as designed. Keep the test results, a route map and a labelling scheme. Good documentation saves hours when something needs to be repaired or extended, especially if a different team handles it years later.

6. Think about operation and maintenance

A network is only useful if it stays up. Decide in advance who will monitor the link, how faults will be reported, and how quickly repairs can be made. For critical sites, consider a second path or spare cores so a single cable cut does not take everything offline.

How eDruk can help

eDruk Private Limited has worked on technology in Bhutan since 2004, including optical fibre networks, structured LAN cabling, network equipment installation and network operation and maintenance. Whether you are connecting two buildings, a campus or a remote site, we can help you plan the route, choose suitable equipment and get the link built properly.

Talk to us about your next network project:

• Email: edruk@edruk.com.bt
• Phone: +975 2 332277
• Website: https://www.edruk.com.bt