this repo has no description
1---
2title: An introduction to the feature flow
3layout: post
4date: 2022-11-19
5draft: true
6---
7
8# An introduction to the feature flow
9
10From my experience, project failures mainly come from having mistrust between teams. Therefor lead time due to team availability to solve dependencies increases.
11
12A kanban is a way to illustrate the needed interactions between teams to complete a feature.
13
14In this post, I would like to tell you what helped me, how we succeed to engage all the skills needed to develop a product. We'll talk about agility, about lean, about problems.
15
16## Creating flow
17
18### Define the steps
19
20## It always comes to **showing**
21
22## Showing where we are
23
24## Showing where are the problems
25
26## Showing what next the team has to do
27
28Talking is hard, comprehension between two people is hard. How many times a developper came back to the product owner to ask a few questions left in his ticket? How many times a designer was asked to update a design to see how the app will react for a specific edge case?
29
30Dear developers, how clear is it for you the way you build an app?
31
32You may answer "Easy! There are few steps:"
33
341. Talking to the client
352. Getting the design
363. Coding
374. deploying to users
38
39But how exactly? What does "talking to the client" really mean? And "coding" ?
40
41In lean, one particular important concept is **Visual Management**: _doing by seeing_. For that, we want to be clear on how we work.
42
43May I ask you some questions?
44
45First, can you name your different step before having your app in production?
46
47<production-flow client:visible />