| A | B | C | D | E | |
|---|---|---|---|---|---|
1 | Please make a copy of this Google Sheet so that you can make changes and fill it in. | ||||
2 | |||||
3 | Project components | Questions to answer | Your answer | Status | |
4 | 1. INTRODUCTIONS | ||||
5 | 1.1 | Company information | Could you give some insight into your company's operations and the market it operates in, including what makes you unique compared to other industry players? | ||
6 | 1.2 | Glossary | Can you clarify any technical terminology, jargon, or acronyms used in the document that might be challenging for those unfamiliar with your industry or company to comprehend? | ||
7 | 2. GOALS | ||||
8 | 2.1 | Aims of the project | Can you make an overview of the project goals, including what you're looking to accomplish and the expected results? Additionally, if there are any key performance indicators (KPIs) associated with the project, please mention them. | ||
9 | 2.2 | Project context | Could you provide some background on the inspiration for your software, as well as its intended purpose? How does it fit into the larger context of your organization's initiatives, and is it related to any other ongoing projects or efforts? If so, how closely are they connected? | ||
10 | 2.3 | Previous project activities | Can you outline all project activities that have been initiated thus far and describe their current progress status? | ||
11 | 2.4 | Timeline | What are your delivery date requirements for the software? Would you prefer a complete delivery or an iterative approach? Do you have a plan in place, and how flexible are the deadlines? | ||
12 | 2.5 | Budget | What is the estimated budget range for this project that a potential supplier should expect to work with? | ||
13 | 2.6 | Expected results | What results do you expect? | ||
14 | 3. USERS | ||||
15 | 3.1 | User groups | Can you identify and describe the various user groups who will be using your software? | ||
16 | 3.2 | Permissions for user groups | Can you provide details on the permission model for the software, such as those for users, groups, and other stakeholders? Will permissions be granted automatically by the software or by an administrator on an individual basis? | ||
17 | 4. FUNCTIONS | ||||
18 | 4.1 | Business process scheme | Could you provide a verbal or visual breakdown of the actions required to reach our business objective | ||
19 | 4.2 | User functionalities | Could you outline the specific actions that each user group will undertake when using the software, either through verbal description or visual representation? | ||
20 | 4.3 | Integrations | Please list any programs that you anticipate will need to be integrated with the new software. | ||
21 | 4.4 | Priorities | Please indicate which of the listed requirements are critical for completion of the project and which are optional or can be completed at a later stage. | ||
22 | |||||
23 | |||||
24 | |||||
25 | |||||
26 | |||||
27 | |||||
28 | |||||
29 | |||||
30 | |||||
31 | |||||
32 | |||||
33 | |||||
34 | |||||
35 | |||||
36 | |||||
37 | |||||
38 | |||||
39 | |||||
40 | |||||
41 | |||||
42 | |||||
43 | |||||
44 | |||||
45 | |||||
46 | |||||
47 | |||||
48 | |||||
49 | |||||
50 | |||||
51 | |||||
52 | |||||
53 | |||||
54 | |||||
55 | |||||
56 | |||||
57 | |||||
58 | |||||
59 | |||||
60 | |||||
61 | |||||
62 | |||||
63 | |||||
64 | |||||
65 | |||||
66 | |||||
67 | |||||
68 | |||||
69 | |||||
70 | |||||
71 | |||||
72 | |||||
73 | |||||
74 | |||||
75 | |||||
76 | |||||
77 | |||||
78 | |||||
79 | |||||
80 | |||||
81 | |||||
82 | |||||
83 | |||||
84 | |||||
85 | |||||
86 | |||||
87 | |||||
88 | |||||
89 | |||||
90 | |||||
91 | |||||
92 | |||||
93 | |||||
94 | |||||
95 | |||||
96 | |||||
97 | |||||
98 | |||||
99 | |||||
100 | |||||