Showing posts with label tasks. Show all posts
Showing posts with label tasks. Show all posts

February 14, 2014

Size matters, and comparing sizes matters even more.

What will be the right size of a task so it will be easier to bring it into execution and action?  How can we size the effort needed to get it done And how do we know what is right for us compared to someone else performing the same task?

Kids (and adults) often mistaken their ability to get things done while getting right into action when encountering a problem or a task. Sometimes, they even are avoiding getting into action due to the fact that the task seems to be too big or too complicated to execute… I sometimes see kids getting to much homework that just looking on the size of their “homework” tasks can be frightening. Who wouldn’t prefer not to play outside instead of dealing with this giant homework assignment? Sizing those tasks has a lot to do with our ability to get them done. It allows us to better scope our attention, better control our activities related to a specific task and gain confident while getting those tasks done.

Much has been written concerning the efforts estimation of a task and its relation to ease our ability to execute it. As is commonly assumed (no matter if it is false or not) that when we know how long it will take to complete a task or what the effort entails it will be easier for us to understand when a group of tasks due to complete.  It is often assumed the same assumption about the size of a task or a problem.  

I say, When we know what’s the right size of a task according to our subjective ability to execute it, it will be easier to estimate a group of tasks and accordingly our ability to get them done.  

There are many methods that can be applied to understand a task size so it won’t be too big to deal with or too small to even consider doing it and accordingly to get it done.


If so, how do we balance the size of our tasks for ourselves or for a chield?
The answer, of courseIt depends.

Here are some tips which will help us better understand the subjective size of the task according to subjective personal ability .

One.      Create your task list and make sure it is visible and apparent.

Visibility makes things happenThe Task list should not stay in your head put it on the boardSo after seeing it, it gets easier to organize things and make decisions and certainly easier to understand what takes more time or less time comparing to other task.


Two.      Size your tasks by three types of sizes:
Small
Medium
Large
Extra large ** - Optional but not advisable

At this stage all we want to achieve is the ability to visualize tasks in deferent sizes. It is still one big wish lists of stuff we need to do or to achieve.  For better Visibility, create three columns on the board and place each task under the appropriate column, or perhaps even give a different color for each size. The main goal at this stage is that you will be able to see the differences between tasks sizes.


Three.      Listen and Learn
Remember when you were a child, places seemed bigger and greater probably more than they are today This is how a child sees tasksMuch larger than they appear to usThings that seem small and simple to us can be perceived as very large and complicated to childrenOften because they lack information or guidance, or just because that's how it is in their eyes. And yes, listening and asking questions to understand the enormity of the task in the eyes of the child is the next step we need to take.
What is a small task What is a big task What makes it large?




Four.      Once the most important tasks are on the task board, take the large tasks and split them into smaller ones. Remember only small or medium sized tasks will be executed – so make sure to split those tasks to an executable ones. Small task is one that can be completed in a relatively short period of time, defiantly not in a week or a day, and obviously appropriate for a child time frame.
As the following example.


Five.       While executing the tasks - stick to tasks that are small or medium-sized and arrange your tasks in order of action.

Six.      Select one  task at a time and start to perform Make sure to visualize your path to execution as well (To do – Doing – Done)  on the task board.






Seven.      When a task is too large to execute, do not be afraid to split I in to smaller ones.

Eight.      Not every task must be sizedIn fact, most tasks do not required sizing.
For example, let's say, the child has only two days to study for his next exam, then we can start by splitting the tasks in a very rough manner such as What to be studied today and what to be studied tomorrowWe can then discuss any task and understand it if it belongs to the first or second day and size only those tasks that seems too big to handle.
In short, let’s try to keep things simple.
Sizing a task should be "just enough" so we can get startedWe Do not need to dig too much in to the details of a tasks so we can assess accurately hours and minutes that it will take us to execute it.  Three sizes of 'small', 'medium' and 'large' can suffice.

Nine.      What will truly help get things done and understand the right size of a task for a child is parental involvement. Conversation. Children love that we talk to them, relate to what they need to do, help them understand thingsSo while this simple technique will help them better understand the task and may even reduce anxiety or focuses on what matters, what will make it really happen is the conversation with us, their parents.

Ten.    And do not forget to enjoy the ride.

January 25, 2014

Last Thing First - Back-chaining

Usually the process of teaching people how to successfully complete long sequences of is to teach how to start the task sequence and then proceed right along to the end of the chain of events. Backward chaining however refers to breaking down the steps of a task and teaching them in reverse order. The biggest advantage from the learner’s point of view is that it offers immediate satisfaction. It  minimize anxiety and provide a sense of accomplishment. This feeling of success will increase confidence and keep us motivated to learn and complete the entire sequence of steps. 


September 22, 2013

Value points with Kids chores and task board.

Kids enjoy games, especially when we win prices and especially when it’s fun, and done with us (their parents). Games and prices are huge motivators so sometimes it’s so simple to teach a technique using simple price with a simple game. Just think about video games for a moment, they are an amazing way to achieve a feeling of success, almost every video game has a reward in it.
Before we start explaining the kids tasks Value Point Game, I wanted to present this game as it was used by one of the scrum teams I worked with. The team came with this idea to use  MnM to measure visual value points of user stories.
What did they do?
Each user story in the backlog holds a deferential value, represented by points.


Each MnM color represents a deferential project portfolio type (Risk projects, Bread&Butter’ project and more)
Each flow step rewords with relevant sweeties:) according to the value this user story holds.


When the user story is done, we can eat out its MnM’s. Just for fun.



Well, they didn't have to do any of this, it was just for fun, and it remained fun. And it was effective too,  Fun always get things done better.

How can we use this at home with our kids chores?
Simple, Decide on the amount of points that each task in the backlog holds.
Each Done task rewards the total family point’s repository with its relative points.
At the end , The points can be represented candy, MnM, or just any color Round Sticker if you like.
The goal, achieve the day points by starting from the most valuable tasks (those with more points).

For those of you who don’t know the entire agile methods, keep on reading into this blog to follow some important tips:
1.       Keep all tasks visible.
2.       Keep tasks simple.
4.       Keep tasks small and achievable.
5.       Do one thing a time.
8.       And don’t forget to have fun

Want to read more?


September 29, 2012

I Do, We Do, You Do - Agile@Home (Technique )



  
 I came across a nice post ,  which explained the “I do, we do, you do “ technique beautifully.

‘But Shirly,’ I hear you asking, ‘What IS the ‘I do, we do, you do’ technique?’.
The formal explanation is here:
“Kids internalize concepts through gradual release: a teacher models a concept or skill while kids observe (“I do”); kids engage with the concept or skill with lots of teacher support (“we do”); kids give it a shot on their own (“you do”). “    3 Quick Wins for Kids Ministry

This is a common teaching practice used with students, and is also frequently used when you introduce Agile to teams. The way I see it, kids and families can also benefit from this concept at home - especially when combined with Agile.
As always, I’ll keep it simple. If you want to read more, there are links at the bottom of this post.
Ok, let’s take the daily scrum meeting as an example to illustrate this method.

In most of the cases the scrum daily meeting is a new skill that the team needs to learn. This meeting is time boxed for 15 minutes regardless of the size of the team, and looks to review the team work progress, the team’s commitment, and help the team focus, identify and eliminate impediments to progress.
Sounds simple?
You need to learn HOW to do it. The team has to learn how to conduct this meeting in the most effective and efficient manner.
So sometimes I use the “I do , we do , you do” technique. The first time the team gathers for the scrum daily meeting, I, as a coach, will take the role of the scrum master and facilitate this meeting. I will make sure the team and the scrum masters observes (“I do”).
Next meeting, I will ask the scrum master to facilitate the meeting with me, together, (“we do”) . I will stand next to the scrum master and let him lead while I fine tune correct if and where it’s needed. Usually the ‘we do’ part takes no more than one or two sessions until the scrum master and the team feels they can do it themselves.
In the “we do” stage , its extremely important to get the team feedback and get feedback from the ‘student’, to understand if they are confident enough to manage by themselves.
The third step will be the “you do “. I stand back and let the scrum master and the teams take the lead.
At each step, I will provide the team with relevant feedback.
If I need to fine tune of a process, or introduce a new method needed teaching, I may repeat this process.

So where’s the big problem?
Well, the problem starts when we use concepts that we already know - as managers, as teachers, or as parents, and we expect new participants to immediately understand what we are talking about and follow it. In other words, we expect others to start from the ‘you do’ phase, without going through the other two phases.
For example, Management discusses and learns a new meeting process, and the developers get an email telling them what to do in their next meeting. Do we actually expect them to learn a new practice from an email? One that took the managers the better part of a day to discuss and understand?

Exactly the same thing happens at home with our kids. You can’t expect them to ‘get’ something that took you a long time to learn.
Going through these stages is necessary, and important. It makes sure that even those children who think they are fast learners follow each step, until they have really learned and understood.
Combine this technique with Agile, and it’s awesome to use at home.

Among other things, Agile brings the concept of visibility to the table, as we use the task board to reflect our progress. The advantages of visibility are widely known to be a powerful for learning and as a “get things done” tool.
Visualization as a family holds enormous value, as I’ve written before. It shows the progress, pushes us to perform as a group, enables us to get feedback, prevents singling out problematic team members, and so much more!

Agile adds the communication value and the need to plan and retrospect over our performance.
It also holds lots of mindset and empowerment aspects which enhance learning and the feeling of self capability.
And it is so simple to implement, like it’s a quick win
So when we speak about Agile and boards, specifically about the visualization aspects, we can have several of visualization and implementation options in this area.
We could just add the following columns to our board:
I do , we do , you do.

Need to learn a new subject? Make it into a sticky note, and move it across these columns, with each one representing the learning phase of a task we are in.





 To sum up - the following rules are applicable in most cases:

1.    Visualize your tasks. Visualization makes it easy to put things in order, get things done, acknowledge our progress get feedback and gain the feeling of control. Use a task board.  Make sure every learning task is on the board.
2.    As always, divide big issues into smaller ones and go ahead. Don’t use massive learning tasks with massive step as one learning issue. Split it to smaller ones.  But keep the big picture in front of you. After all, learning is not only about doing small steps. The big picture is sometimes very important for the child to be aware of.
3.    Pull one task, complete it , and then pull the next task in line.
4.    I do – model  the step yourself -  eliminate “going ahead” just because we think we know how to do something.
5.    We do - Do it together with your kid. It can be a one-on-one session, or a class session where we all do it together. At the end – place the card on the board.
6.    You do -Let them get things done – each child using his card to perform the task .
8.    If the child doesn’t succeed completing one of the stages, learn from it. It’s perfectly OK to try again, to practice some more.
9.    Of course , don’t forget the communication aspect. Talk things over, retrospect over your performance and learn
10. As always, don’t forget to have fun.

References and reading: