Key Risks -> External dependencies

Author: krlmlr

proposal/03-proposal.qmd

@@ -20,5 +20,25 @@ Depending on project type the detail section should include:
 -->
 
 ### Minimum Viable Product
+
+<!--
+What is the smallest thing you can build that delivers value to your users?
+-->
+
 ### Architecture
+
+<!--
+What does the high-level architecture look like?
+-->
+
 ### Assumptions
+
+<!--
+What assumptions are you making that, if proven false, would invalidate the project?
+-->
+
+### External dependencies
+
+<!--
+What external dependencies does the project have (e.g. libraries, services, other projects, etc.)?
+-->

proposal/06-success.qmd

@@ -1,33 +1,22 @@
 # Success
-<!-- 
+<!--
 Projects should have a definition of done that is measurable, and a
 thorough understanding going in of what the risks are to delivery
 -->
 
 ## Definition of done
-<!-- 
-What does success look like? 
+<!--
+What does success look like?
 -->
 
 ## Measuring success
-<!-- 
+<!--
 How will we know when success is achieved, what markers can we use
 along the way
 -->
 
 ## Future work
-<!-- 
+<!--
 How could this be extended / developed in the future by yourself
 and/or the community in general?
 -->
-
-## Key risks
-<!-- 
-What sort of things could come up that can delay or break the project?
-
- - [ ] People
- - [ ] Processes
- - [ ] Tooling & Technology
- - [ ] Costs
-
--->