-
Notifications
You must be signed in to change notification settings - Fork 4
kanban method final #9
base: molszewski9412-kanban-method
Are you sure you want to change the base?
kanban method final #9
Conversation
final remake
* Due date - We set a maximum of two weeks to complete the tasks. | ||
|
||
The card is very important in the whole project process. Thanks to | ||
her, we measure our work and set time for each stage in the design, develop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 card is not her
. We say it is a card
not she is a card
. Please fix that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace by that way
|
||
* Title - As needed, it can be very general or low-level, | ||
* Description - With some documentation, links or to do list, | ||
* Assigne - If you want to plan something with others You can assing more than |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 Asignee
|
||
## Workflow | ||
|
||
The card life begins in Backlog, tasks here's have lowest priority and they |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 here's
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
didn't notice
waiting for select to development - but it's not a rule, sometimes we add cards | ||
with high priority directly to ToDo column. ToDo is the queue for the most | ||
important column - In Progress. From there our goal is to safely move this task | ||
to done. Of course sometimes something will happen, but by analyzing the boards |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 Of course sometimes something will happen
very vague and not professional.
we are able to find the blocker very quickly. In embedded systems company, we | ||
are dealing mostly with blockers in the form not working or missing hardware, | ||
incompatibility of the kernel with hardware, frequent changes in priorities. | ||
In case of problems we try to react quickly to not disturb the whole process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 another very trivial sentence that add not much to whole picture.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deleted
to done. Of course sometimes something will happen, but by analyzing the boards | ||
we are able to find the blocker very quickly. In embedded systems company, we | ||
are dealing mostly with blockers in the form not working or missing hardware, | ||
incompatibility of the kernel with hardware, frequent changes in priorities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 this sentence makes sense.
* In Progress have biggest priority, next is ToDo and Backlog, | ||
* Never take more than two tasks at a time - it is interesting to note that when | ||
switching between two tasks we need about 13 minutes to return to the previous | ||
concentration, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 where did you get that number ? If you quoting other documents please add source.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I heard this few times, it's not from any document
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 please indicate that this is wide spread knowledge - this may not apply to all industries.
concentration, | ||
* Do not throw unfinished tasks for verification, because due date is comming, | ||
* Listen and read communication, ask questions - takes priority tasks no focus | ||
on backlog, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 last part of this sentence is not clear to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deleted
where tasks is going fast to verification, after which it turns out that the | ||
task is incomplete and we need turn it back to the left. When the checks show | ||
such errors, we try to first determine the degree of completion of the card, and | ||
then decide whether the card must return or it is a matter of a small patch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 sometimes we split cards and move part of result to Verification and other part to ToDo.
Fix post according to @pietrushnic review
and testing solutions in embedded systems projects. Additionally inside the | ||
The card is very important in the whole project process. That way, we measure | ||
our work and set time for each stage in the design, develop and testing | ||
solutions in embedded systems projects. Additionally inside the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 testing solution phases
to done. By analyzing the boards we are able to find the blocker very quickly. | ||
In embedded systems company, we are dealing mostly with blockers in the form | ||
not working or missing hardware, incompatibility of the kernel with hardware and | ||
frequent changes in priorities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
* In Progress have biggest priority, next is ToDo and Backlog, | ||
* Never take more than two tasks at a time - it is interesting to note that when | ||
switching between two tasks we need about 13 minutes to return to the previous | ||
concentration, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 please indicate that this is wide spread knowledge - this may not apply to all industries.
deleted info about concentration and fix in part "Workflow"
|
||
> In software development, Kanban provides a visual process-management system | ||
which aids decision-making about what, when and how much to produce. Although | ||
the method (inspired by the Toyota Production System and lean manufacturing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 closing bracket is missing?
|
||
## Workflow | ||
|
||
The card life begins in Backlog, tasks here have lowest priority and they |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 they are waiting
with high priority directly to ToDo column. ToDo is the queue for the most | ||
important column - In Progress. From there our goal is to safely move this task | ||
to done. By analyzing the boards we are able to find the blocker very quickly. | ||
In embedded systems company, we are dealing mostly with blockers in the form |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 in the form of
|
||
To make kanban work, each employee must follow these rules: | ||
|
||
* In Progress have biggest priority, next is ToDo and Backlog, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 has the biggest
* Suggest changes in places where you see such a need. | ||
|
||
These rules are only a sample but improve the whole process. We know situations | ||
where tasks is going fast to verification, after which it turns out that the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 It should be either either tasks are
ore task is
|
||
These rules are only a sample but improve the whole process. We know situations | ||
where tasks is going fast to verification, after which it turns out that the | ||
task is incomplete and we need turn it back to the left. When the checks show |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 we need to
turn
by reducing the volume of communication and grouping it into individual pages. | ||
At this moment we are able to follow tasks of every employee in our company | ||
individually so now we don't have to look for another tool but maybe in future | ||
we will try to mix some metodologies for better work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@molszewski9412 methodologies
Maciej's review fixes
small correction
@macpijan please approve, if everything fixed. |
our work and set time for each stage in the design, develop and testing | ||
solution phases in embedded systems projects. Additionally inside the | ||
card we can discuss the features and see, what happened since last time. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Additionally we can discuss the features inside the cards and see..." sounds even better and more correctly
* Due date - We set a maximum of two weeks to complete the tasks. | ||
|
||
The card is very important in the whole project process. That way, we measure | ||
our work and set time for each stage in the design, develop and testing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be "develop and test"
|
||
## Workflow | ||
|
||
The card life begins in Backlog, tasks here have lowest priority and they are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"The card life begins in Backlog." This should be one sentence and "Tasks here..." another one. There is no much relation between them to separate them with comma
## Workflow | ||
|
||
The card life begins in Backlog, tasks here have lowest priority and they are | ||
waiting for select to development - but it's not a rule, sometimes we add cards |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be "waiting for selection"
## Workflow | ||
|
||
The card life begins in Backlog, tasks here have lowest priority and they are | ||
waiting for select to development - but it's not a rule, sometimes we add cards |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"..not a rule. Sometimes..." Separate it with dot.
## Summary | ||
|
||
Kanban is designed for companies looking for ways to optimize task allocation | ||
and for teams that are overloaded with tasks. It works because introducing lower |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sentence syntax is wrong "It works well, because it introduces lower task settlements and by the way it adds very good tools for work progress measuring and overproduction managing." Do not mix present continuous and present simple this way. If You start with "introducing" then it should be "adding" and if You have "adds" then write "introduces". Stick to one either continuous or simple.
of tasks into very low levels and the rules of work are very similar to the | ||
production where the downtime blocks the whole group, so choice of Kanban was | ||
very useful in our company. By using it, we have increased productivity, order | ||
in the organization of our tasks and make it easy to find the needed information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"made"
in the organization of our tasks and make it easy to find the needed information | ||
by reducing the volume of communication and grouping it into individual pages. | ||
At this moment we are able to follow tasks of every employee in our company | ||
individually so now we don't have to look for another tool but maybe in future |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put comma before "but"
progress and overproduction managing. Our specialization requires the division | ||
of tasks into very low levels and the rules of work are very similar to the | ||
production where the downtime blocks the whole group, so choice of Kanban was | ||
very useful in our company. By using it, we have increased productivity, order |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"As a result, we have..."
progress and overproduction managing. Our specialization requires the division | ||
of tasks into very low levels and the rules of work are very similar to the | ||
production where the downtime blocks the whole group, so choice of Kanban was | ||
very useful in our company. By using it, we have increased productivity, order |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try "helpful" instead of "useful"
@mscibisz at some point you should review, improve and publish this blog post. |
final remake