Skip to content

Commit 7ad3385

Browse files
jlarforsjlarfors
committed
first draft of devex assessment
1 parent 22bfbe1 commit 7ad3385

File tree

1 file changed

+105
-49
lines changed

1 file changed

+105
-49
lines changed

‎services_assess_devex.templ

+105-49
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ templ servicesAssessmentsDeveloperExperience() {
66
@column("") {
77
<h1 class="v-h1">Developer Experience Assessment.</h1>
88
<h4 class="mt-8 v-h4">
9-
We help assess and improve the developer experience of your teams to increase flow and productivity.
9+
Learn to measure and improve your Developer Experience to reach new heights of productivity and happiness.
1010
</h4>
1111
}
1212
@column("") {
@@ -21,60 +21,116 @@ templ servicesAssessmentsDeveloperExperience() {
2121
<div class="bg-v-gray/20">
2222
<section class="container mx-auto">
2323
@headerLine()
24-
<h4 class="v-h4">Why DevEx?</h4>
24+
<h4 class="v-h4">Why Developer Experience?</h4>
2525
<h2 class="mt-4 v-h2">
26-
Developer experience is a measure of how smooth it is for someone to perform essential tasks needed to deliver software.
27-
Better Developer Experience leads to more flow. More flow leads to more productivity.
26+
A better Developer Experience is proven to improve individuals satisfaction, engagement and retention as well increasing performance outcomes for individuals, teams and organisations.
2827
</h2>
28+
<div class="mt-8">
29+
@linkButtonSmall("Learn more", "/blog/a-study-of-developer-experience/")
30+
</div>
2931
</section>
30-
// <section class="container mx-auto">
31-
// @headerLine()
32-
// <h4 class="v-h4">Our approach.</h4>
33-
// <h2 class="mt-4 v-h2">We uses several methods for researching and assessing DevEx.</h2>
34-
// </section>
3532
<section class="container mx-auto">
3633
@headerLine()
37-
<p class="v-h4">Our approach.</p>
38-
<dl class="pt-4 space-y-6 divide-y divide-v-black ">
39-
@homeService("preparation", "Preparation") {
40-
<h4 class="mt-8 v-h4">Identify owner</h4>
41-
<p class="mt-4">The assessment owner has the mandate to drive the assessment and own the results from your side.</p>
42-
<h4 class="mt-8 v-h4">Define scope</h4>
43-
<p class="mt-4">Define a rough start and end for the assessment. Commonly we conduct planning interviews to set a structure for the assessment.</p>
44-
<h4 class="mt-8 v-h4">Start!</h4>
45-
<p class="mt-4">Based on the scope we begin the assessment with the investigation to research and learn about your current developer experience.</p>
46-
}
47-
@homeService("investigation", "Investigation") {
48-
<p class="mt-8">
49-
Below are the methods we use to investigate your current developer experience. We use a combination of these methods to get a holistic view of your current state.
50-
</p>
51-
<h4 class="mt-8 v-h4">Value Streams</h4>
52-
<p class="mt-4">
53-
We facilitate Value Stream Mapping workshops with your development teams to understand their workflows, pains, waste and opportunities for increased flow.
54-
</p>
55-
<h4 class="mt-8 v-h4">Wardley Maps</h4>
56-
<p class="mt-4">
57-
We use Wardley Mapping to understand the interface between platforms and developers. It helps us reason about the cognitive load and platform evolution.
58-
</p>
59-
<h4 class="mt-8 v-h4">Gemba Walks</h4>
60-
<p class="mt-4">
61-
We do Gemba Walks to understand the current state of your development teams. We observe and ask questions to understand their daily routine and how we can improve it.
62-
</p>
63-
<h4 class="mt-8 v-h4">Developer Surveys</h4>
64-
<p class="mt-4">
65-
Ongoing surveys that provide actionable results help us gauge the effects of change and highlight teams that may need more support.
66-
</p>
67-
}
68-
@homeService("report", "Report") {
69-
<h4 class="mt-8 v-h4">Report</h4>
70-
<p class="mt-4">We prepare a report summarizing the investigation, the pain points (i.e. waste) and our own suggestions that we can think of. This is the first version of a backlog.</p>
71-
<h4 class="mt-8 v-h4">Feedback</h4>
72-
<p class="mt-4">A discussion about the assessment and report. It is important that you understand the report and are comfortable with the implementation.</p>
73-
<h4 class="mt-8 v-h4">Build - Measure - Learn</h4>
74-
<p class="mt-4">This is where the real work of implementing change begins. It is important to do it iteratively and our crew are here to assist.</p>
75-
}
76-
</dl>
34+
<h4 class="v-h4">Why a Developer Experience Assessment?</h4>
35+
<h2 class="mt-4 v-h2">
36+
// If you are aware of the benefits of an improved Developer Experience but are unsure where to start, a Developer Experience Assessment is the perfect place to begin.
37+
// It will teach you how to measure your own Developer Experience and research methods for identifying areas of improvement.
38+
// Learn how to measure your own Developer Experience along with methods to iteratively improve it.
39+
// Developer Experience cannot be bought but must be developed. Our assessment
40+
// An Assessment is perfect for kick-starting or boosting your improvement process.
41+
You cannot buy Developer Experience, but our crew can teach you how to craft one people will remember.
42+
</h2>
7743
</section>
44+
<section class="container mx-auto">
45+
<div class="prose md:prose-lg lg:prose-xl xl:prose-2xl max-w-none">
46+
<h3>Our approach.</h3>
47+
<p>
48+
// This is more philosophical.
49+
Improving your Developer Experience is not a one-time event.
50+
It is a process of Continuous Improvement.
51+
We will teach you how to measure your Developer Experience as well as research methods you can use to identify opportunities for improvement.
52+
// We tailor it to your organisation and context. You cannot buy "off the shelf" DevEx.
53+
</p>
54+
<p class="italic">
55+
Give a team a roadmap and you feed them for an iteration. Teach them how to create the roadmap and you feed them forever.
56+
</p>
57+
<h3>What you can expect.</h3>
58+
<p>
59+
// This is what we actually do, and what you actually get.
60+
Together we will collect metrics, conduct surveys and host workshops.
61+
The data we gather will indicate a current level of Developer Experience and highlight painpoints that we can use to set goals, implement improvements and justify the investment we are making.
62+
</p>
63+
<p>
64+
The assessment can last from a few days to a few weeks depending on the size of and number of teams and the level of existing Developer Experience data you have.
65+
At the end of the assessment we will provide a report that summarises the process so far and actionable steps you can take to improve your Developer Experience.
66+
// Something about us not being average consultants...
67+
// We don't sell people to solve problems, we sell our crew...
68+
// Diverse experience: agile, vsm, devops, cloud, etc.
69+
// What you will get out of it: we tech you how to fish... the reports...
70+
</p>
71+
<h3>What happens next?</h3>
72+
<p>
73+
The assessment is your first step towards a better Developer Experience.
74+
It will provide you with an understanding of your current Developer Experience and opportunities to improve.
75+
</p>
76+
<p>
77+
Next begins the Build-Measure-Learn process of implementing changes, measuring the effects and learning from the results.
78+
Our crew are here to help guide you through the process.
79+
We can be hands-on with our <a href="/services/consulting/">consultancy services</a> or take an advisory role via our <a href="/services/coaching/">coaching services</a>.
80+
</p>
81+
</div>
82+
</section>
83+
// <section class="container mx-auto">
84+
// @headerLine()
85+
// <h4 class="v-h4">Why DevEx?</h4>
86+
// <h2 class="mt-4 v-h2">
87+
// Developer experience is a measure of how smooth it is for someone to perform essential tasks needed to deliver software.
88+
// Better Developer Experience leads to more flow. More flow leads to more productivity.
89+
// </h2>
90+
// </section>
91+
// <section class="container mx-auto">
92+
// @headerLine()
93+
// <p class="v-h4">Our approach.</p>
94+
// <dl class="pt-4 space-y-6 divide-y divide-v-black ">
95+
// @homeService("preparation", "Preparation") {
96+
// <h4 class="mt-8 v-h4">Identify owner</h4>
97+
// <p class="mt-4">The assessment owner has the mandate to drive the assessment and own the results from your side.</p>
98+
// <h4 class="mt-8 v-h4">Define scope</h4>
99+
// <p class="mt-4">Define a rough start and end for the assessment. Commonly we conduct planning interviews to set a structure for the assessment.</p>
100+
// <h4 class="mt-8 v-h4">Start!</h4>
101+
// <p class="mt-4">Based on the scope we begin the assessment with the investigation to research and learn about your current developer experience.</p>
102+
// }
103+
// @homeService("investigation", "Investigation") {
104+
// <p class="mt-8">
105+
// Below are the methods we use to investigate your current developer experience. We use a combination of these methods to get a holistic view of your current state.
106+
// </p>
107+
// <h4 class="mt-8 v-h4">Value Streams</h4>
108+
// <p class="mt-4">
109+
// We facilitate Value Stream Mapping workshops with your development teams to understand their workflows, pains, waste and opportunities for increased flow.
110+
// </p>
111+
// <h4 class="mt-8 v-h4">Wardley Maps</h4>
112+
// <p class="mt-4">
113+
// We use Wardley Mapping to understand the interface between platforms and developers. It helps us reason about the cognitive load and platform evolution.
114+
// </p>
115+
// <h4 class="mt-8 v-h4">Gemba Walks</h4>
116+
// <p class="mt-4">
117+
// We do Gemba Walks to understand the current state of your development teams. We observe and ask questions to understand their daily routine and how we can improve it.
118+
// </p>
119+
// <h4 class="mt-8 v-h4">Developer Surveys</h4>
120+
// <p class="mt-4">
121+
// Ongoing surveys that provide actionable results help us gauge the effects of change and highlight teams that may need more support.
122+
// </p>
123+
// }
124+
// @homeService("report", "Report") {
125+
// <h4 class="mt-8 v-h4">Report</h4>
126+
// <p class="mt-4">We prepare a report summarizing the investigation, the pain points (i.e. waste) and our own suggestions that we can think of. This is the first version of a backlog.</p>
127+
// <h4 class="mt-8 v-h4">Feedback</h4>
128+
// <p class="mt-4">A discussion about the assessment and report. It is important that you understand the report and are comfortable with the implementation.</p>
129+
// <h4 class="mt-8 v-h4">Build - Measure - Learn</h4>
130+
// <p class="mt-4">This is where the real work of implementing change begins. It is important to do it iteratively and our crew are here to assist.</p>
131+
// }
132+
// </dl>
133+
// </section>
78134
// <section class="container mx-auto">
79135
// @grid() {
80136
// <div>

0 commit comments

Comments
 (0)