Do you know the word "to do"?
Even if you hear words such as "to do management", "todo list" and "todo ticket", i do not understand the true meaning, i do not understand well! i think that there are many people.
what is project management to do? first of all, when
"to do" is summarized, it means
"list of things that need to be done" and "things that should not be forgotten".
the title "project management todo" literally includes "time-limited responses", "task management", and "project memorandum" that occur in the execution of the project.
as we carry out the project, i think we will see the following situations.
CASE1
subordinate: "excuse me, i noticed a leak in a task i completed earlier..." apologize to the customer and respond as soon as possible!"
CASE2
subordinate : "i'm sorry, i completely lost my work..." boss : "i understand. be careful next time!"
It can be inferred that many of these CASES are due to neglecting todo management. And if we can prevent such mistakes, I think that the project will proceed smoothly. This time, I would like to consider the problems of real
"project management to do"
occurring in the project field and how to implement "project management to do" based on them through the function of our project management tool "SI Object Browser PM (hereinafter HEREAFTER OBPM)".
project management todo: issues with "time-limited response" one day Subordinate: "I'm sorry, I'm not sure what
to do by when with this work..." I'll explain it properly, so take notes!" Boss : "Responding to failures that came out of the ○○ project, solving the problem of PC failure, and all the minutes of yesterday's meeting tomorrow.
Subordinate: "Yes!
I understood it well!!"
next day
Boss : "Did you do everything
you explained verbally yesterday?" subordinate : "Yes, I did it!" ○○I finished the response of the failure that came
out in the project and the minutes of the meeting" Boss : "Oh, how do you solve the problem of PC failure?" subordinate : "Oh, ah. I forgot!! I'm sorry..."
- I think that the above-mentioned conversation is painfully flying around in the office.
- It is a conversation that I often hear between my boss and new employees and young employees who are unfamiliar with work.
- Listening to such a conversation at work will make the surrounding air worse and you don't want to listen as much as possible.
- Aside from that, let's consider the above problems here.
First, from the problem of the boss.
I'm going to tell you too much verbally about various tasks at once.
There is a limit to the amount that can be handled and the amount that can be heard in humans. Even if I tell you, it may be over with "I just told you!".
What would have happened if this could be left as a "character" such as an email or management tool?
Next, the problem of the subordinate.
This is simple, I didn't know what I was going to understand and that I neglected to check the tasks I had to do again. It is common for new employees and young employees.
Such a problem, even if you think that it can be prevented if you think that you want to prevent it, if you put a new employee who is unfamiliar with work after a student, or if you are spending a busy day that you can not drink a sip of juice, it may be a part that you will come out by all means.
In order to prevent such problems, I feel that it is important every day that "you are in a situation where you can check what you are going to do many times by when", "being able to centrally manage the corresponding tasks", and "being able to manage whether or not a task is completed".
From the next section, we will explain concrete examples of the use of project management "todo" through OBPM.
try managing todo tasks for projects you're responsible for
As mentioned above, if you can manage what to do by when you implement project management, I think that the number of times you are angry with task omissions and bosses will be reduced.
When project management is performed in OBPM, these can be realized by using the functions "Ticket (TO DO) management" and "Incomplete ticket (TO DO)".
Below is the obpm "Incomplete Ticket (TO DO)"
It is a function that can manage each task and event that occurs during the course of the project as a deadline and priority ticket (todo). In addition, for each individual's incomplete tasks, it is usually managed separately, such as each document and individual's memo, but OBPM can "centrally manage" these.
1.
The level of management of todo varies. In some projects, do not bother to manage [risk] [problem]! Some of the design books are reviewed from a single sentence.
The extent to which you do it in detail depends on the size of the project and the person in charge, but the above features can be adapted to any level. Being able to centrally manage in this way will clarify what each individual needs to do and prevent task omissions.
In addition, OBPM's project management todo can set a "deadline" for when to respond, and tasks that have not been completed will continue to appear on the screen. Now, let's imagine the journey from the actual occurrence of the todo task to completion!
This is an example of a scene where [failure] occurred in system development. In the event of a failure, specify the person who wants to respond on the OBPM and "Register the failure". Then, the task with a time limit is displayed on the screen of the person who wants to respond, as shown in the following red frame. At this time, we will ask those who wish to respond with the meaning of "Please respond!!". If you don't call out and see the responder secretly registered only for the disorder, you may feel a little dry (sweat) I derailed a little, but I move on to the main subject. From here, I described the image of the failure registered by the responder until the response was completed.
2.
when you press the blue link button of the registered failure, you will be taken to the failure registration screen. then, the work is carried out in order from 1 to 3 below.
when a failure occurs, first check the "failure" and "response contents", and then check the "response deadline" and "priority". ※refer to the blue frame below.
next, let's move on to the corresponding work of 1.
when 2 is completed, fill in the "response date", "response contents", and "cause". ※refer to the red frame below.
3.
This is the flow to the completion of the todo task. If you respond to 3, the failure response will be completed, and the individual 'Failure] task will disappear from the list on the "Incomplete Ticket (TODO)" screen.
* The task disappeared from the list on the screen = The todo task is completed.
4.
how was it to see the flow so far?
i think that it was smooth from the occurrence of the task to the completion. we were able to achieve an easy-to-understand and simple management method that clearly displayed what we had to do on the screen and disappeared from the list when the task was completed. i think that this todo management function can prevent task leakage even for new employees and busy people. also, if you can manage at this level, project management todo will work.
devise a project management to do!
as discussed above, "project management to do" is something that can be missed without a detailed perspective.
- convey various things at once.
- communicate the task only verbally.
- there are a lot of situations around the area where leaks are likely to occur.
even in such a situation, if you are carrying out a project, i think it is necessary to acquire a todo management method that adapts to each individual and make it a habit. if the management method itself is not bad, but if the task omission occurs even though the management was thoroughly carried out, i think that "plus α" is necessary for the management method.
"plus α" is surprisingly easy.
for example, when you signed a lease to move.
let's say the real estate says, "please transfer money by ○○!"
i think that it will be polarized to the person who forgets it and the person who makes the transfer exactly if it is so far.
however, in addition to this, let's say you fill out a reminder email from real estate or in your personal schedule book, "transfer by this date!"
then, it can be imagined that the result will naturally change.
The "plus α" of the story here is that it is "left in the character".
Implementing project management to do isn't just about preventing on-the-spot task leaks.
what tasks have you had in the past?
What did you do at that time?
you can check. the more to do management you manage, the more assets you will be in the future. therefore, let's add a device to the management method that we are currently implementing so that to do management does not leak.
last but not least, when i ask the person in charge what the factors were in our successful project, i hear that most of them were "less reworked or task omissions." i heard that what i did every day to eliminate rework and task omissions was that we thoroughly managed to do.
if "to do management" fails, it seems that he practiced adding a device to it.
No comments:
Post a Comment