diff --git a/1au46-getting-oriented.html b/1a-getting-oriented.html similarity index 54% rename from 1au46-getting-oriented.html rename to 1a-getting-oriented.html index 3796703..25e1f5d 100644 --- a/1au46-getting-oriented.html +++ b/1a-getting-oriented.html @@ -8,7 +8,7 @@ - + @@ -27,225 +27,207 @@ - -
-
-
- -
- logo symbol -
- Foundation for Public Code -
-
-
-
-
Codebases
Resources
Who we are
Join us
- -
-
- Mastodon Github - + +
+
+ +
+ logo symbol +
+ Foundation for Public Code
+
+
+
+
Stewardship
Resources
Who we are
Join us
+ +
+
+ Mastodon Github +
-
-
-

Process code for software procurement

-
-
-
-
-
- +
+

Process code for software procurement

+
+
+
+
+
+ This process code will introduce you to a digital-native approach to procurement. It maintains the core principles of public procurement—fairness, transparency and objectivity—but realigns the process with contemporary software development.
-
- + By using this process code, government organizations will obtain the best possible software for the needs at hand and avoid ballooning costs. Public sector employees are in control of how their - digital tools are designed, purchased and used. + digital tools are designed, purchased and used.
 +
+
+ Read more about process codes here
-

- Read more about process codes here -

-
-
-
1a. Welcome!
-
-
-
- Ellipse -
-
- Vector -
- Vector - Vector - Vector -
-
-
-
-
- Ellipse 2.7 - Ellipse 2.10 -
-
-
-
-
-
- Ellipse - Ellipse - Ellipse -
-
-
-
- Vector 2 - symbol-dev - Ellipse 2.11 - Ellipse 2.12 -
-
-
-
- This document is a guide to help public sector employees source the best possible software to - serve the public better. It walks through government contracting step-by-step, aligning legitimate - public procurement with the cutting-edge best practices of software development.
-
-
- It is not an inflexible set of mandatory steps. Rather, it introduces fundamental concepts at - each stage of a procurement, provides guidelines and best practices, and offers links to - additional resources if you would like to read more. +
+
1a. Welcome!
+
+
+
+ Ellipse +
+
+ Vector +
+ Vector + Vector + Vector +
+
+
+
+
+ Ellipse 2.7 + Ellipse 2.10 +
+
+
+
+
+
+ Ellipse + Ellipse + Ellipse +
+
+
+
+ Vector 2 + symbol-dev + Ellipse 2.11 + Ellipse 2.12
+

+ We believe that software can serve the public better! This document is a guide to help you, a public + sector employee, source the best possible software. It walks through government contracting + step-by-step, aligning legitimate public procurement with the cutting-edge best practices of software + development. It is not an inflexible set of mandatory steps. Rather, it introduces fundamental + concepts at each stage of a procurement, provides guidelines and best practices, and offers links to + additional resources if you would like to read more. +

-
-

+

+

Who should use this process code for software procurement?

-
-
- +
+ Several people from different departments should be involved in a software design and procurement process—from legal counsel to IT to the end users themselves—each bringing their own expertise and perspective. This guide is intended for all of them, but each will have a more prominent role in certain phases.
-
- There will also typically be a single person who follows the process from beginning to end: the - product owner. Product owners are expert generalists who deeply understand end users and their - needs, work across different departments, ask good questions, and carry the project from start to - finish. The product owner should read this whole guide, and be comfortable with each step of the - process, while specialists can read the introduction and basic principles, then focus on the - particular step that is most relevant to them. + There will also be a single person who follows the process from beginning to end: the ‘product + owner.’ Product owners are expert generalists who deeply understand end users and their needs, + work across different departments, ask good questions, and carry the project from start to finish. + The product owner should read this whole guide, and be comfortable with each step of the process, + while specialists can read the introduction and basic principles, then focus on the particular + step that is most relevant to them.
-
-

How to use this process code

-
-
- +

How to use this process code.

+
+
+ You should read through this process code and become familiar with its content, now—before you begin working on a specific software project. Successful procurement is built on a solid - foundation of staff capacity, collaboration, and shared understanding. It’s important to lay that + foundation of staff capacity, collaboration, and shared understanding. It’s important ot lay that foundation before you have the time pressure of a specific project.
-
- This process code will walk you through four primary phases: +
+ This process code will walk you through four primary phases.
-
-
-
-
1. Orientation
+
+
+ Orientation
-
-
-
2. Planning
+
+ Planning
-
-
-
3. Assessment
+
+ Assessment
-
-
-
4. Implementation
+
+ Implementation
-

- Within each phase there are number of steps. Each step contains key challenges, knowledge content, - suggested actions, and takeaways, as well as references and additional reading. In some cases, the - suggested actions culminate in you choosing to progress down one path or another. +

+ Within each phase there are number of steps. As you click through the course, each step is a page. On + that page, you’ll find key challenges, knowledge content, suggested actions, and takeaways, as well as + references and additional reading. In some cases, the actons on a page culminate in a decision + – you’ll choose to progress down one path or another.

- main-diagram v6 1 -
-
- +
+
+ The process code ends with an implementation phase that emphasizes ongoing collaboration. That is - to say, a software project is never really finished. In the best case, you become an active + to say, a software project is never really “finished.” In the best case, you become an active participant in the use, maintenance and improvement of your software, for the benefit of all public sector organizations.
-
- The fundamental purpose of the process code is to anchor a community of practice. Reach out - to the Foundation for Public Code with any questions, and to learn about joining a group of peers. - +
+ The fundamental purpose of the process code is to anchor a community of practice. Reach out to + the Foundation for Public Code with any questions or to learn about joining a group of + peers.
-
-
-
Strategic paths
-
-
- +
+
Strategic paths
+
+
+ At the end of the Orientation phase, you will have a clear sense of where your software will come - from, based on the needs you identify using various discovery methods, your development capacity, - and the maturity of the market. At that point, you will choose a path—purchasing existing - software, customizing open source software, or contracting a vendor who can build custom software - for you—and write an RFP (Request for Proposal) accordingly.
-
- + If you decide to build software in-house, you won’t write an RFP. Instead, your team will run an agile development process. Although the details of agile development are out of scope for this process code, we provide some useful resources and references. And the Orientation and @@ -254,95 +236,91 @@

Process code for software procurement

-
-
-
-
-
- icon.path.off-the-shelf -
-
-
Purchase existing
-

Get software off the shelf

-
+
+
+
+
+ icon.path.off-the-shelf
-
-
-
-
-
-
- Union - Union - Union -
- $ -
-
-
- Vector 6 - Vector - Vector -
+
+
Purchase existing
+

Get software off the shelf

+
+
+
+
+
+
+
+
+ Union + Union + Union +
+ $ +
+
+
+ Vector 6 + Vector + Vector
-
-
-
Customize OSS
-

Contract a vendor to adapt open source software

-
-
-
-
-
-
-
-
-
- Union - Union - Union -
- code - $ +
+
Customize OSS
+

Contract a vendor to adapt open source software

+
+
+
+
+
+
+
+
+
+ Union + Union + Union
+ code + $
-
-
Custom software
-

Contract a vendor to build software

-
-
-
-
-
-
- Union - gear 2 -
-
-
-
Build in-house
-

Build software (or adapt OSS) in-house

+
+
Custom software
+

Contract a vendor to build software

+
+
+
+
+
+
+
+ Union + gear 2
-
-
+
+
Build in-house
+

Build software (or adapt OSS) in-house

+
+
+
-
-
-
Getting oriented
+
+
+
Getting oriented
-
-
- +
+ Procurement is an opportunity to evaluate how you work today, how you could work more effectively in the future, and how to align with broad municipal priorities like climate change or social equity. Orientation is about creating a solid foundation for your organization to effectively build, @@ -352,32 +330,34 @@

Process code for software procurement

-
- + Capacity-building starts long before there is any specific software project to work on. Product owners should spend time meeting staff members from various departments, hosting Q&A workshops, - debunking myths about government procurement, helping colleagues become fluent with common language - (for example agile, DevOps, exclusionary criteria), and sharing the basics of agile software - development. The process of obtaining specific software builds on this foundation.
(“agile” “DevOps” “exclusionary criteria”), and sharing the basics of agile software development. The process of obtaining specific software + builds on this foundation.
-
- + The next step is to use discovery research methods to understand the challenge or opportunity, define user needs, and develop ideas about potential solutions. The goal is to arrive at a precise problem statement.
-
- + A good sense of the problem allows us to evaluate potential solutions that might already exist in the market—including off-the-shelf software and open source software (OSS). If nothing good exists, the problem statement also helps with estimating the costs of building software in-house or contracting a custom solution.
-
- + These options should be evaluated in a neutral way, accounting not only for cost, but also for quality, long-term lifecycle costs of ownership and maintenance, and potential unforeseen concerns like vendor lock-in and data ownership.Process code for software procurement
-
- -
-
1b. Capacity-building
- Arrow
+ +
+
1b. Capacity-building
+ Arrow
-
-
- - - - -
-
-
-
Have a question?
+
+ + + + +
+
+
+
+
Have a question?
+ >
-
-
-
- -
- logo symbol -
- Foundation for Public Code +
+
+
+ +
+ logo symbol +
+ Foundation for Public Code +
+
+
+
+
Codebases
Resources
Who we are
Join us
+ +
+
+ Mastodon Github +
-
-
-
-
Stewardship
Resources
Who we are
Join us
- -
-
- Mastodon Github -
-
-
-

Process code for software procurement

-
-
-
-
-
- +
+

Process code for software procurement

+
+
+
+
+
+ This process code will introduce you to a digital-native approach to procurement. It maintains the core principles of public procurement—fairness, transparency and objectivity—but realigns the process with contemporary software development.
-
- + By using this process code, government organizations will obtain the best possible software for the needs at hand and avoid ballooning costs. Public sector employees are in control of how their - digital tools are designed, purchased and used.
 -
-
- Read more about process codes here + digital tools are designed, purchased and used.
+

+ Read more about process codes here +

+
-
-
1a. Welcome!
-
-
-
- Ellipse -
-
- Vector -
- Vector - Vector - Vector -
-
-
-
-
- Ellipse 2.7 - Ellipse 2.10 -
-
-
-
-
-
- Ellipse - Ellipse - Ellipse -
-
-
-
- Vector 2 - symbol-dev - Ellipse 2.11 - Ellipse 2.12 +
+
1a. Welcome!
+
+
+
+ Ellipse +
+
+ Vector +
+ Vector + Vector + Vector +
+
+
+
+
+ Ellipse 2.7 + Ellipse 2.10 +
+
+
+
+
+
+ Ellipse + Ellipse + Ellipse +
+
+
+
+ Vector 2 + symbol-dev + Ellipse 2.11 + Ellipse 2.12 +
+
+
+
+ This document is a guide to help public sector employees source the best possible software to + serve the public better. It walks through government contracting step-by-step, aligning legitimate + public procurement with the cutting-edge best practices of software development.
+
+
+ It is not an inflexible set of mandatory steps. Rather, it introduces fundamental concepts at + each stage of a procurement, provides guidelines and best practices, and offers links to + additional resources if you would like to read more.
-

- We believe that software can serve the public better! This document is a guide to help you, a public - sector employee, source the best possible software. It walks through government contracting - step-by-step, aligning legitimate public procurement with the cutting-edge best practices of software - development. It is not an inflexible set of mandatory steps. Rather, it introduces fundamental - concepts at each stage of a procurement, provides guidelines and best practices, and offers links to - additional resources if you would like to read more. -

-
-

+

+

Who should use this process code for software procurement?

-
-
- +
+ Several people from different departments should be involved in a software design and procurement process—from legal counsel to IT to the end users themselves—each bringing their own expertise and perspective. This guide is intended for all of them, but each will have a more prominent role in certain phases.
-
- There will also be a single person who follows the process from beginning to end: the ‘product - owner.’ Product owners are expert generalists who deeply understand end users and their needs, - work across different departments, ask good questions, and carry the project from start to finish. - The product owner should read this whole guide, and be comfortable with each step of the process, - while specialists can read the introduction and basic principles, then focus on the particular - step that is most relevant to them. + There will also typically be a single person who follows the process from beginning to end: the + product owner. Product owners are expert generalists who deeply understand end users and their + needs, work across different departments, ask good questions, and carry the project from start to + finish. The product owner should read this whole guide, and be comfortable with each step of the + process, while specialists can read the introduction and basic principles, then focus on the + particular step that is most relevant to them.
-
-

How to use this process code.

-
-
- +

How to use this process code

+
+
+ You should read through this process code and become familiar with its content, now—before you begin working on a specific software project. Successful procurement is built on a solid - foundation of staff capacity, collaboration, and shared understanding. It’s important ot lay that + foundation of staff capacity, collaboration, and shared understanding. It’s important to lay that foundation before you have the time pressure of a specific project.
-
- This process code will walk you through four primary phases. +
+ This process code will walk you through four primary phases:
-
-
- Orientation
 +
+
+
+
1. Orientation
-
- Planning
 +
+
+
2. Planning
-
- Assessment
 +
+
+
3. Assessment
-
- Implementation +
+
+
4. Implementation
-

- Within each phase there are number of steps. As you click through the course, each step is a page. On - that page, you’ll find key challenges, knowledge content, suggested actions, and takeaways, as well as - references and additional reading. In some cases, the actons on a page culminate in a decision - – you’ll choose to progress down one path or another. +

+ Within each phase there are number of steps. Each step contains key challenges, knowledge content, + suggested actions, and takeaways, as well as references and additional reading. In some cases, the + suggested actions culminate in you choosing to progress down one path or another.

- main-diagram v6 1 -
-
- +
+
+ The process code ends with an implementation phase that emphasizes ongoing collaboration. That is - to say, a software project is never really “finished.” In the best case, you become an active + to say, a software project is never really finished. In the best case, you become an active participant in the use, maintenance and improvement of your software, for the benefit of all public sector organizations.
-
- The fundamental purpose of the process code is to anchor a community of practice. Reach out to - the Foundation for Public Code with any questions or to learn about joining a group of - peers. +
+ The fundamental purpose of the process code is to anchor a community of practice. Reach out + to the Foundation for Public Code with any questions, and to learn about joining a group of peers. +
-
-
-
Strategic paths
-
-
- +
+
Strategic paths
+
+
+ At the end of the Orientation phase, you will have a clear sense of where your software will come - from, based on your needs, your development capacity, and the maturity of the market. At that - point, you will choose a path—purchasing existing software, customizing open source software, or - contracting a vendor who can build custom software for you—and write an RFP accordingly.
-
- + If you decide to build software in-house, you won’t write an RFP. Instead, your team will run an agile development process. Although the details of agile development are out of scope for this process code, we provide some useful resources and references. And the Orientation and @@ -863,91 +861,95 @@

Process code for software procurement

-
-
-
-
- icon.path.off-the-shelf -
-
-
Purchase existing
-

Get software off the shelf

+
+
+
+
+
+ icon.path.off-the-shelf +
+
+
Purchase existing
+

Get software off the shelf

+
-
-
-
-
-
-
-
- Union - Union - Union -
- $ -
-
-
- Vector 6 - Vector - Vector +
+
+
+
+
+
+ Union + Union + Union +
+ $ +
+
+
+ Vector 6 + Vector + Vector +
+
+
Customize OSS
+

Contract a vendor to adapt open source software

+
-
-
Customize OSS
-

Contract a vendor to adapt open source software

-
-
- -
-
-
-
-
-
- Union - Union - Union +
+
+
+
+
+
+
+
+
+ Union + Union + Union +
+ code + $
- code - $
-
-
-
Custom software
-

Contract a vendor to build software

-
-
- -
-
-
-
- Union - gear 2 +
+
Custom software
+

Contract a vendor to build software

-
-
Build in-house
-

Build software (or adapt OSS) in-house

+
+
+
+
+
+ Union + gear 2 +
+
+
+
Build in-house
+

Build software (or adapt OSS) in-house

+
-
- + +
-
-
-
Getting oriented
+
+
+
Getting oriented
-
-
- +
+ Procurement is an opportunity to evaluate how you work today, how you could work more effectively in the future, and how to align with broad municipal priorities like climate change or social equity. Orientation is about creating a solid foundation for your organization to effectively build, @@ -957,34 +959,32 @@

Process code for software procurement

-
- + Capacity-building starts long before there is any specific software project to work on. Product owners should spend time meeting staff members from various departments, hosting Q&A workshops, - debunking myths about government procurement, helping colleagues become fluent with common language (“agile” “DevOps” “exclusionary criteria”), and sharing the basics of agile software development. The process of obtaining specific software - builds on this foundation.
-
- + The next step is to use discovery research methods to understand the challenge or opportunity, define user needs, and develop ideas about potential solutions. The goal is to arrive at a precise problem statement.
-
- + A good sense of the problem allows us to evaluate potential solutions that might already exist in the market—including off-the-shelf software and open source software (OSS). If nothing good exists, the problem statement also helps with estimating the costs of building software in-house or contracting a custom solution.
-
- + These options should be evaluated in a neutral way, accounting not only for cost, but also for quality, long-term lifecycle costs of ownership and maintenance, and potential unforeseen concerns like vendor lock-in and data ownership.Process code for software procurement
-
- -
-
1b. Capacity-building
- Arrow
+ +
+
1b. Capacity-building
+ Arrow
-
- - - - -
-
-
-
-
Have a question?
+
+
+ + + + +
+
+
+
Have a question?
+ >
-