large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

Published on <a href="https://blog.prototypr.io/being-agile-and-getting-your-development-team-onboard-c24d3cd28c49?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> UX Boot Camp 
<h4>#30dayUXchallenge [Day 22]</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugUBlNEQzApe1keI9LmFoA.jpeg">
If you are a designer you are probably interested on learning how to design experiences to deliver value to people.
All good right? Great.
<blockquote>I’m afraid you would be also interested to learn how to work in teams to co-create solutions or even harder, how to work in dev teams.</blockquote>
We work in world full of systems and the systems need a mechanism to make them work.
Some of us work on software development and we in somehow or another are being exposed to work in systems we didn’t create and we are not familiar with.
Why I never heard of it in the UNI?
Well, that’s true. We’ve been busy studying just design subjects and learning new design skills and that’s why some of us never heard about dev teams or how to work with them.
<h3>Agile — good or bad?</h3>
In software development we use some methods and processes to build systems. Some people like them other don’t but the reality is that we need to be aligned if we want to build things together on a team and we set processes in place to make it happens.
Dev teams are great to follow up stories and tasks and agile is a very good way to do it. As a team we can co-create and commit ourselves to deliver something in a certain amount of time.
We use standup meetings to follow up this everyday sharing experiences about what we have done yesterday and what will be the plan for today. Good visibility on everybody’s work and no blockers.
<h3>Designers and Agile</h3>
Designers have a different mindset when it comes to plan the journey or find it out how long it would take a discovery phase for example.
It’s tricky to mix our skill set within a very structured mechanism and that’s where <a href="https://blog.prototypr.io/design-thinking-dab6b9e9d69e">Design Thinking</a> is here to help.
Part of our job is to make sure that the user voice will be heard and that’s why we set up <a href="https://blog.prototypr.io/why-you-need-a-user-research-plan-19caf4438a35">research plans</a>.
Once we get that, we make the analysis with the team and make sure we are going to provide the right value to the right people.
<h3>Get your team onboard</h3>
Design activities tend to be disruptive and hard to measure but we can definitely do something more accurate facilitating some activities on a time — framed where we can definitely get all our team onboard and also proving some track o them.
Hopefully this tips can help you to frame it:
<ol>
<li>Use Design Thinking to facilitate instances where people can co create together and make sure all those activities has a ‘task’ on the board where the rest of the team has their tasks. Add and extra task to prepare de activity too.</li>
<li>In the activity, set up the scenario to talk about the Persona or the jobs to be done from an specific audience based on the research you did it previously. Make sure you have the following activities in case you need them.</li>
<li>From there, encourage the team to propose solutions to people’s problems or even creating new opportunities to improve some activities.</li>
<li>Think BIG, be creative and how we can bring BIG VALUE to our customers whenever they need to do ‘X’ or ‘Y’.</li>
</ol>
Once you have a clear big value to deliver, now we can start thinking on how can we split on small significant ones to be more agile and learn on the go.
<h3>From the Big Value</h3>
Well done, you helped your product team to create within cross functional people, the big value that you are thinking on deliver to your customers. Lovely!
Now, it’s time to make it happen. How we can move from the BIG idea to small chunks we can achieve in a certain amount of time, considering the learning as a fundamental piece of the process?
Let’s see an example here:
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYsSWRtYBX88oNTGcd6LYA.png">
<h3>Small Values then</h3>
As a team you need to co create together small chunks of value you can deliver in short periods of time.
Following up the previous example:
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M8N7IJo_ejUUpKpCh6t3IQ.png">
Once you have some small chunks of ‘values’ to deliver to people then you can frame and plan your time accordingly.
You don’t need to have the full solution in place to plan about next steps but you need to frame it correctly, leaving the space in time to manage unexpected situations or even reactions to the values.
Be again, prepared to fail, thinking on new solutions and test it back.
<h3>It’s not a matter of the method</h3>
We can do it and actually it could possible forces us to be more accurate and creative reducing the risks of being out of topic.
Good luck and happy planning!
<h3>Are you agile?</h3>
Have you found agile a good or a bad thing in your organisation? Do you work differently? Better solutions for designers? Share your thoughts and we will be happy to spread it 🙂
<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5eb5ba-2%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5eb5ba-2%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252F5eb5ba-2%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/8d5e2c740a04faf463af9accfa7e3c31/href">https://medium.com/media/8d5e2c740a04faf463af9accfa7e3c31/href</a></iframe><img alt="" src="https://cdn-images-1.medium.com/max/123/1*gRVYJu11nwFHTMt56Z93fA.png">Natalia Rey — UX Designer at RedGate, mom of 2 little creatures &amp; illustrator on her spare time
This post is part of the #30dayUXchallenge: you can read more about why we started it <a href="https://medium.com/envato/why-were-embarking-on-a-30dayuxchallenge-e3d9f1bc1ac6">here</a>, and don’t forget to follow us on <a href="https://twitter.com/ux_bootcamp">Twitter</a> and <a href="https://www.instagram.com/ux_bootcamp">Instagram</a>!
<img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=c24d3cd28c49" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="https://blog.prototypr.io/being-agile-and-getting-your-development-team-onboard-c24d3cd28c49">Being Agile and getting your development team onboard</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Being Agile and getting your development team onboard

Being Agile and getting your development team onboard

#30dayUXchallenge [Day 22]

Top Stories