The S.C.R.I.P.T. Method: The Guide for an impactful specifications

Introducing the SCRIPT method

To help you draft a complete and effective specifications document, we present the SCRIPT method, a six-step process: Specification, Criteria, Requirements, Implementation, Planning, and Technology. The use of the S.C.R.I.P.T. method allows you to cover the subject from all angles, achieve alignment between business and IT, and create a strong request for proposal, thereby securing the successful development of the application.

Method summary:

Specification

Specifications are the foundation of your project requirements document. In general, this point is well covered, but some elements may be missing, and it is essential to clearly define the structuring elements of the project:

• Scope: describe the layout of the application and the list of key features. This overview allows you to frame the project and establish a common vocabulary with the consulted providers. Provide a plan for each application to be developed (web application, mobile application, back-office application, etc.).
• User stories: establish a list of user needs to give a clear idea of the expected features. Try to maintain consistent detail depth based on the importance of each feature. A common mistake in requirements documents is to have a high level of detail on less critical screens (such as account creation and login, where there aren't many surprises) and too little detail on key application features, leaving too much room for interpretation.
• Initial wireframes: at the very least, provide the wireframes of your First Use Case. You can supplement with wireframes of other important and structuring screens for your application.
• Graphic orientations: specify the graphic choices and constraints of the project to guide the desired design.

Tip: Start with an application plan (site map or application map) created using a mind mapping tool, prioritize screens by their importance to the user, and detail the features from most to least important.

Most project requirement documents stop here. While this is an essential part of the document, there are still many elements left to specify.

Criteria

You must be as clear as possible with the consulted providers (and for yourself) regarding the requirements of your request for proposal:

Requirements

For the provider to fully understand your expectations, it is important to detail the project's objectives and the expected outcomes:

• Company Vision: provide an overview of the company and the ecosystem in which the project is integrated.
• Current Situation: detail the existing setup, the role of the new application, and its interaction with other systems. Clearly state the purpose of the specifications document and what you expect from the new project.
• Project Ambition (the most important): clarify the project's objective with a clear and SMART success criterion (Specific, Measurable, Achievable, Realistic, and Time-bound).

Tip: In Discovery Discipline, the project's ambition is expressed with a “Success Criteria” and a “Damage Control” because achieving the success criterion should not be at all costs; there are always side effects that need to be managed.

Implementation

Describing the methodology that will be used for the project's execution is essential to create alignment between the provider's way of working and what you expect for the project's success:

• Project tracking: Detail the tracking system on your end and the methodology to be used by the provider. An agile approach is highly recommended, yes, even in case of outsourcing, the agile approach is often the right path to follow.
• Roles and responsibilities: List and describe the roles and responsibilities of the entire project team (on your side and the provider's side). One person can take on multiple roles, and a role can be shared by several people. For each role, specify whether it will be held by someone on your side, the provider's side, or both.
• Bug management and maintenance: Mention the requirements for handling bugs and future developments to ensure the project's sustainability.

Tips: Detail the roles and responsibilities of project stakeholders (both internally and on the provider's side), as well as the regular project events (which events to work on the product vision and which events to work on project execution).

Planning

A detailed plan helps structure the project and set realistic expectations:

• Major milestones: break the project down into distinct phases.
• Key checkpoints: define (many) alignment points to track progress, gather feedback as early and as frequently as possible, and remain agile throughout the project (yes, I'm repeating myself, but it's intentional 😉).

Technology

Finally, it is crucial to specify the key technical elements of the project:

• Architecture: provide a diagram of the proposed architecture.
• Technologies: indicate the frameworks, infrastructure, tools, and hosting solutions planned.
• Data Volume: share figures on data volume, number of application users, application usage rate, or any other information that will help the provider better anticipate certain load and/or volume challenges.
• Security and Quality: outline the performance, accessibility, and security requirements, as well as how the provider will collaborate with your internal teams.

Be specific in your description (React for the front, .NET Core for the back end, AWS for hosting, Flutter for the mobile app, using the company's Design System, using Jira, etc.). You should describe the ideal technical stack for you and your project within your IT environment, rather than being subject to the provider’s choices based on their expertise.

Conclusion

Don't leave the drafting of the project brief to chance. Use the SCRIPT method to structure your projects and ensure their success.

Bonus gift (because a gift is always appreciated): to help you even further, exFabrica offers you a downloadable project brief template.