change to feature factory
This commit is contained in:
39
src/pages/posts/feature-factory.mdx
Normal file
39
src/pages/posts/feature-factory.mdx
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: An introduction to feature factory
|
||||
layout: post
|
||||
---
|
||||
|
||||
# {title}
|
||||
|
||||
From my experience, project failures mainly come by having mistrust between teams. Lead time due to team availability to solve dependencies increases.
|
||||
|
||||
In 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 will talk about agility, lean.
|
||||
|
||||
## It always comes to **showing**
|
||||
|
||||
## Showing where we are
|
||||
|
||||
## Showing where are the problems
|
||||
|
||||
## Showing what next the team has to do
|
||||
|
||||
Talking 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 in case of an edge case?
|
||||
|
||||
Dear developers, how clear is it for you the way you build an app?
|
||||
|
||||
You may answer "Easy! There are few steps:"
|
||||
|
||||
1. Talking to the client
|
||||
2. Getting the design
|
||||
3. Coding
|
||||
4. deploying to users
|
||||
|
||||
But how exactly? What does "talking to the client" really mean? And "coding" ?
|
||||
|
||||
In lean, one particular important concept is **Visual Management**: *doing by seeing*. For that, we want to be clear on how we work.
|
||||
|
||||
May I ask you some questions?
|
||||
|
||||
First, can you name your different step before having your app in production?
|
||||
|
||||
<ProductionFlow client:visible />
|
||||
@@ -1,25 +0,0 @@
|
||||
---
|
||||
title: An introduction to production flow
|
||||
layout: post
|
||||
---
|
||||
|
||||
# {title}
|
||||
|
||||
Dear developers, how clear is it for you the way you build an app?
|
||||
|
||||
You may answer "Easy! There are few steps:"
|
||||
|
||||
1. Talking to the client
|
||||
2. Getting the design
|
||||
3. Coding
|
||||
4. deploying to users
|
||||
|
||||
But how exactly? What does "talking to the client" really mean? And "coding" ?
|
||||
|
||||
In lean, one particular important concept is **Visual Management**: *doing by seeing*. For that, we want to be clear on how we work.
|
||||
|
||||
May I ask you some questions?
|
||||
|
||||
First, can you name your different step before having your app in production?
|
||||
|
||||
<ProductionFlow client:visible />
|
||||
Reference in New Issue
Block a user