It's kind of amazing how we have so much information at our fingertips, yet rarely take advantage of that information. Due to systems that fix spelling errors pretty well, we often type something in sort of like what we wanted and assume it will be fixed.
I like to know what acronyms stand for and what technical terms mean before I use them. For example, I work with Gantt charts regularly. I am amazed how often people who should know better use all sorts of alternate names for the chart.
I hear Gnatt regularly. Like the insect. I see it written as GANTT, as if it were an acronym. There are a lot of acronyms in project management (PERT, RACI, PMI, BCWP, WBS), but it isn't Graphical Analysis of Numerical Task Timelines. It also isn't gantt. It's a last name. The chart was invented by Henry Gantt (or least that's who got credit for it).
You get into sketchy territory with some names, such as the Apgar test used to check newborn health and improvement within the first few minutes of birth. It is a 10 point scale, with 5 characteristics, which can be given a 0, 1, or 2. It was created by Virginia Apgar, a doctor in the 1950s. She came up with the 5 items, which were later given the eponymous backronym of Appearance, Pulse, Grimace, Activity, and Respiration (APGAR). How awesome is it that it is her name but also a mnemonic to help remember the points? Isn't it good to take a few minutes and learn where it came from before you use it? I was working with a group of nurses on a curriculum development project several years ago, and we were all surprised by the origin of the acronym. I feel like the nurses shouldn't have been.
I think Henry Gantt would agree.
Sunday, March 31, 2019
Wednesday, February 27, 2019
FLL Competition
Last month we had the final competition for the Lego Robotics team. I say final, because it was the last one for us, although it was actually the qualifier for the state competition. Spoiler alert: we didn't qualify for state. And that's okay.
The competition was on a Saturday (back in January). It was cold and early, but it wasn't very far from our house, which I appreciated. There were 11 teams, including two from our school. I think there was supposed to be 10 teams, but due to some lack of communication all around, our team got registered late, and they were kind enough to let us still register. Poor communication was something I fought with the entire season.
We showed up early and set up on our table. Each team had a table about two and a half feet by two and a half feet in the hallway to set up our things on. We didn't have a poster like many other teams did. We had a laptop with a PPT presentation for our research problem, so we fired that up and would run through it with those who stopped to take a look.
There were several tables set up in an open area right next to us, which we could practice the missions on. We found that on one of our missions the robot was running short for some reason. I don't know how that happened, but it did, and the kids fixed it.
There are four main aspects to the judging. The first is the most obvious - points scored in actual competition. We ran three times and took our highest score. The second is the robot design discussion, where the team meets with some judges and talks to them about how they designed the robot, both physically and the programming behind it. The third is a research problem related to the theme for the year (this year was space - last year was water). The fourth is team dynamics - how well everyone gets along and works together.
We had four missions we attempted. There are some others we could have done if the team had more focus. Two missions we pretty much had solid. One was so-so, and the other one we pretty much knew it wasn't going to work. In all three runs, the robot got stuck at some point and had to be rescued, which is a small penalty. Only having to grab it once each was pretty good, I thought. After the first run, the kids thought of a way to add some rubber pieces to add more grip to the robot arm to help it accomplish the task they were struggling with. After the second run, they decided to bag the mission that they knew wasn't going to work and just focus on the one they had a chance with. In the third run, they were able to get the third mission completed by running the mission several times, utilizing the extra time they saved by not attempting the one they knew wasn't going to work. I was so proud of them. They were as focused as they had ever been and worked well as a team. The were troubleshooting and adjusting and improving each time.
In the robot design portion, they did okay. We had a large team, and the judges noted that with so many team members, we should have been able to accomplish more missions. That said, at the coaches meeting in the morning, other team coaches were surprised that both teams from our school were the max size (10). I think the coaches recognized something that the judges didn't, which was that more people on the team doesn't mean more work gets done. The phenomenon is clearly addressed in one of my favorite books, The Mythical Man Month (Brooks). The three second version is that just adding more people to your project doesn't mean you're going to get more work done in less time. I can see how having a team of 3 or 4 would be much more effective and efficient than dealing with 10 (we actually had 12, which was over the official limit).
In the research project portion, they had talked about a variety of space-related problems, such as getting attacked by aliens and how to sleep without floating around the space station. They ended up going with scratching your nose with a space suit on. I had turned the kids over to another volunteer to work on deciding what problem to go with, and that's what they came up with. They did really well with it. They started by showing the below video, stepped through several possible ideas they came up with (the best was a trained pet squirrel that could move around in the suit and scratch where you needed), and then showed why their solution was the best choice to provide relief safely, while keeping the hands free to work on the space walk. The judges appreciated both the video to show that it was a real problem and the prototypes they made and brought.
The part that we prepared for the least and that they performed the worst on was the core values (or team building) portion. I hadn't spent much time looking into what that part of the competition would look like, so we kind of winged it going into it. Each team member had one core value that they provided a brief description of. After discussing each of the values, the judges had the team solve a problem together. They had some sand in a little foil tray and a pile of straws and rubber bands and popsicle sticks and had to build a Mars lander that could sit on the surface and not get blown away by the fierce Martian wind. I'll just say they provided good counterexamples to most of the values they had so aptly described moments earlier. The highest score they got on the rubric was related to the team working on their own without interference from the coach, since I pretty much turned around and looked out the window as I couldn't watch. That said, I honestly think it was a fair approximation of how we worked together throughout the season. They did work well in most of the competition other than this component, but our twice-weekly meetings were very chaotic.
I really was proud of them, and so was our principal who attended the competition. A few weeks later in February, we had a STEM night at the school and met one more time just before that event to talk about what we would do for a demonstration. The team was all wondering why we weren't still meeting and wanted to continue working on things even though the competition was over. I appreciated that and gave them one of the secret mission challenges to work on. It was fun to work on it, but it reinforced to me that it was time to be done meeting. Having the competition to work towards was one of the few things keeping them mildly focused.
Based on how things went last year and this year, I think the thing to do is to have a couple levels of teams. I think having an introductory team that meets in the second half of the year to learn basic skills and then from that group have tryouts for next year's competition teams would help. The competition teams need to be 5 or fewer team members, made up of only those with enough technical skills and maturity/focus. We had something like 50 or 60 students sign up wanting to do the team, so we maxed out our teams to get as many involved as we could, while still not being able to include everyone. The competition team needs to be chosen before the year even starts, so that in August, they can set up the missions and immediately begin working. Both this year and last year, we lost a lot of time due to the mission field not being set up. We had a variety of skill levels on the team, with some members very advanced and able to perform complex tasks, and others that just wanted to build random things out of Legos and couldn't write a program to make a robot drive in a straight line. Having an introductory team to draw from based on observing their work would make the competition team much stronger, as well as allowing more time to teach some of the basic skills to those that were brand new to robotics.
The competition was on a Saturday (back in January). It was cold and early, but it wasn't very far from our house, which I appreciated. There were 11 teams, including two from our school. I think there was supposed to be 10 teams, but due to some lack of communication all around, our team got registered late, and they were kind enough to let us still register. Poor communication was something I fought with the entire season.
We showed up early and set up on our table. Each team had a table about two and a half feet by two and a half feet in the hallway to set up our things on. We didn't have a poster like many other teams did. We had a laptop with a PPT presentation for our research problem, so we fired that up and would run through it with those who stopped to take a look.
There were several tables set up in an open area right next to us, which we could practice the missions on. We found that on one of our missions the robot was running short for some reason. I don't know how that happened, but it did, and the kids fixed it.
There are four main aspects to the judging. The first is the most obvious - points scored in actual competition. We ran three times and took our highest score. The second is the robot design discussion, where the team meets with some judges and talks to them about how they designed the robot, both physically and the programming behind it. The third is a research problem related to the theme for the year (this year was space - last year was water). The fourth is team dynamics - how well everyone gets along and works together.
We had four missions we attempted. There are some others we could have done if the team had more focus. Two missions we pretty much had solid. One was so-so, and the other one we pretty much knew it wasn't going to work. In all three runs, the robot got stuck at some point and had to be rescued, which is a small penalty. Only having to grab it once each was pretty good, I thought. After the first run, the kids thought of a way to add some rubber pieces to add more grip to the robot arm to help it accomplish the task they were struggling with. After the second run, they decided to bag the mission that they knew wasn't going to work and just focus on the one they had a chance with. In the third run, they were able to get the third mission completed by running the mission several times, utilizing the extra time they saved by not attempting the one they knew wasn't going to work. I was so proud of them. They were as focused as they had ever been and worked well as a team. The were troubleshooting and adjusting and improving each time.
In the robot design portion, they did okay. We had a large team, and the judges noted that with so many team members, we should have been able to accomplish more missions. That said, at the coaches meeting in the morning, other team coaches were surprised that both teams from our school were the max size (10). I think the coaches recognized something that the judges didn't, which was that more people on the team doesn't mean more work gets done. The phenomenon is clearly addressed in one of my favorite books, The Mythical Man Month (Brooks). The three second version is that just adding more people to your project doesn't mean you're going to get more work done in less time. I can see how having a team of 3 or 4 would be much more effective and efficient than dealing with 10 (we actually had 12, which was over the official limit).
In the research project portion, they had talked about a variety of space-related problems, such as getting attacked by aliens and how to sleep without floating around the space station. They ended up going with scratching your nose with a space suit on. I had turned the kids over to another volunteer to work on deciding what problem to go with, and that's what they came up with. They did really well with it. They started by showing the below video, stepped through several possible ideas they came up with (the best was a trained pet squirrel that could move around in the suit and scratch where you needed), and then showed why their solution was the best choice to provide relief safely, while keeping the hands free to work on the space walk. The judges appreciated both the video to show that it was a real problem and the prototypes they made and brought.
The part that we prepared for the least and that they performed the worst on was the core values (or team building) portion. I hadn't spent much time looking into what that part of the competition would look like, so we kind of winged it going into it. Each team member had one core value that they provided a brief description of. After discussing each of the values, the judges had the team solve a problem together. They had some sand in a little foil tray and a pile of straws and rubber bands and popsicle sticks and had to build a Mars lander that could sit on the surface and not get blown away by the fierce Martian wind. I'll just say they provided good counterexamples to most of the values they had so aptly described moments earlier. The highest score they got on the rubric was related to the team working on their own without interference from the coach, since I pretty much turned around and looked out the window as I couldn't watch. That said, I honestly think it was a fair approximation of how we worked together throughout the season. They did work well in most of the competition other than this component, but our twice-weekly meetings were very chaotic.
I really was proud of them, and so was our principal who attended the competition. A few weeks later in February, we had a STEM night at the school and met one more time just before that event to talk about what we would do for a demonstration. The team was all wondering why we weren't still meeting and wanted to continue working on things even though the competition was over. I appreciated that and gave them one of the secret mission challenges to work on. It was fun to work on it, but it reinforced to me that it was time to be done meeting. Having the competition to work towards was one of the few things keeping them mildly focused.
Based on how things went last year and this year, I think the thing to do is to have a couple levels of teams. I think having an introductory team that meets in the second half of the year to learn basic skills and then from that group have tryouts for next year's competition teams would help. The competition teams need to be 5 or fewer team members, made up of only those with enough technical skills and maturity/focus. We had something like 50 or 60 students sign up wanting to do the team, so we maxed out our teams to get as many involved as we could, while still not being able to include everyone. The competition team needs to be chosen before the year even starts, so that in August, they can set up the missions and immediately begin working. Both this year and last year, we lost a lot of time due to the mission field not being set up. We had a variety of skill levels on the team, with some members very advanced and able to perform complex tasks, and others that just wanted to build random things out of Legos and couldn't write a program to make a robot drive in a straight line. Having an introductory team to draw from based on observing their work would make the competition team much stronger, as well as allowing more time to teach some of the basic skills to those that were brand new to robotics.
Thursday, January 3, 2019
Almost There
The Lego robotics team met several times in December and are now in January, with the competition in two days!
We have pretty much put together their space-related problem presentation. We had decided initially on several possible issues and voted on the one they wanted to go with. There were a lot of unrealistic things, such as alien attacks and so forth, which got dropped out of the running. At the end of the day, they voted on the problem of sleeping while weightless and something to keep them tethered so they wouldn't float around. On the day they were working on the presentation, I was helping one group and someone else another group, and the problem somehow got changed to scratching an itch on your nose while on a spacewalk. So that's what we're going with.
We have four missions they are going to attempt. One of them pretty much works 90% of the time. Another works about 75% of the time. On both of them, it comes down to whether they can get the robot positioned in the right place when it starts. We practiced having every team member know where to place the robot in case anyone doesn't make it. Last year, we had the issue of someone who didn't come for the final presentation and he was the only one who knew where to place the robot to make his program run. On the other two, they work maybe 10% of the time.
Suddenly yesterday, with just one meeting before the competition, we had some of the team members come up with some new ideas, hey, why don't we change the arm on this one and why don't we try to do this other mission, too? I basically told them that those would be great things to do if we had more time, but with the competition Saturday, there's not time to get it just right and practice it so it is polished.
We have pretty much put together their space-related problem presentation. We had decided initially on several possible issues and voted on the one they wanted to go with. There were a lot of unrealistic things, such as alien attacks and so forth, which got dropped out of the running. At the end of the day, they voted on the problem of sleeping while weightless and something to keep them tethered so they wouldn't float around. On the day they were working on the presentation, I was helping one group and someone else another group, and the problem somehow got changed to scratching an itch on your nose while on a spacewalk. So that's what we're going with.
We have four missions they are going to attempt. One of them pretty much works 90% of the time. Another works about 75% of the time. On both of them, it comes down to whether they can get the robot positioned in the right place when it starts. We practiced having every team member know where to place the robot in case anyone doesn't make it. Last year, we had the issue of someone who didn't come for the final presentation and he was the only one who knew where to place the robot to make his program run. On the other two, they work maybe 10% of the time.
Suddenly yesterday, with just one meeting before the competition, we had some of the team members come up with some new ideas, hey, why don't we change the arm on this one and why don't we try to do this other mission, too? I basically told them that those would be great things to do if we had more time, but with the competition Saturday, there's not time to get it just right and practice it so it is polished.
Wednesday, December 5, 2018
Progress Check-in
On Wednesday and Thursday the first week of December, we're at a pivotal point. We're a month into meeting and have about a month left until the competition. It's the halfway mark.
As we continued working on the rocket launch mission where they have to hit the launcher and make the spaceship fly up a certain height, we were trying to find something heavy enough, and one of the kids suggested using the metal sphere that serves as a wheel on the back of the robot. You can use any Lego pieces, and that is from Lego, so it's legal. We're still trying to figure out how to make sure to hit it accurately every time, but with a heavier hammer, there's a better chance of it working.
I asked the kids to demonstrate at the end of one of the team meeting times all the missions and how close they were. They didn't have to work 100%, just sort of work, enough that we could see the idea that the robot would travel and make an action that seemed like it could accomplish the mission. Even if it missed or didn't hit hard enough or whatever, I just wanted them to be able to demonstrate where they were at, more for themselves, to help figure out how much more they have to go. At some point, we will need to connect all the missions, mostly including having the robot return to base where the arm can be swapped out and the robot aimed at the next mission.
The demonstration was okay. Half the missions they demonstrated were things they hadn't worked on in a couple weeks and while they were supposed to be practicing with them to be ready to demonstrate, some of them they hadn't even found the code or re-tested it once. The robot is a little different shape than it was previously with changing out the back wheel for the hammer, so what they programmed before didn't exactly work. I tried to make the point that this is what they were supposed to be preparing for.
We also talked today about the project. I had sort of maybe kind of known there was this other part to the competition but hadn't really looked at this part very hard, since we didn't actually do a competition last year. I remember looking at the challenge a year ago, but since we did a demonstration at the school and not an actual competition, the project didn't feature into what we were doing.
The short description of it is that they pick a problem related to the theme of the year - space, this year - and research a solution to the problem. They were sent home with a homework assignment to come back next week with an idea of a possible problem and solution pair that we could use. They do a presentation that takes under 5 minutes. It can be creative - doesn't have to be totally realistic or ultra-professional. They just have to show they are working together and creatively problem-solving. I think the project sounds kind of fun. One of the kids said, "that sounds boring." I explained that it will be boring if they make it boring or interesting if they make it interesting. So there we are. We'll see tomorrow what they come back with.
As we continued working on the rocket launch mission where they have to hit the launcher and make the spaceship fly up a certain height, we were trying to find something heavy enough, and one of the kids suggested using the metal sphere that serves as a wheel on the back of the robot. You can use any Lego pieces, and that is from Lego, so it's legal. We're still trying to figure out how to make sure to hit it accurately every time, but with a heavier hammer, there's a better chance of it working.
I asked the kids to demonstrate at the end of one of the team meeting times all the missions and how close they were. They didn't have to work 100%, just sort of work, enough that we could see the idea that the robot would travel and make an action that seemed like it could accomplish the mission. Even if it missed or didn't hit hard enough or whatever, I just wanted them to be able to demonstrate where they were at, more for themselves, to help figure out how much more they have to go. At some point, we will need to connect all the missions, mostly including having the robot return to base where the arm can be swapped out and the robot aimed at the next mission.
The demonstration was okay. Half the missions they demonstrated were things they hadn't worked on in a couple weeks and while they were supposed to be practicing with them to be ready to demonstrate, some of them they hadn't even found the code or re-tested it once. The robot is a little different shape than it was previously with changing out the back wheel for the hammer, so what they programmed before didn't exactly work. I tried to make the point that this is what they were supposed to be preparing for.
We also talked today about the project. I had sort of maybe kind of known there was this other part to the competition but hadn't really looked at this part very hard, since we didn't actually do a competition last year. I remember looking at the challenge a year ago, but since we did a demonstration at the school and not an actual competition, the project didn't feature into what we were doing.
The short description of it is that they pick a problem related to the theme of the year - space, this year - and research a solution to the problem. They were sent home with a homework assignment to come back next week with an idea of a possible problem and solution pair that we could use. They do a presentation that takes under 5 minutes. It can be creative - doesn't have to be totally realistic or ultra-professional. They just have to show they are working together and creatively problem-solving. I think the project sounds kind of fun. One of the kids said, "that sounds boring." I explained that it will be boring if they make it boring or interesting if they make it interesting. So there we are. We'll see tomorrow what they come back with.
Wednesday, November 28, 2018
Double Up
For the last week of November and moving forward, we've added an extra session each week. Instead of just meeting on Wednesdays right after school, we will be meeting on both Wednesdays and Thursdays. There is a lot to get done with the competition coming up fast.
We broke out on Wednesday and Thursday of this week into groups and had various people working on different missions. One of the missions is close, with the group that has been focusing and working on things. Focus is definitely an issue, as we have a lot of kids and it's difficult to get them all on task at the same time. We've had some parents coming in to help with crowd control a bit, which has been good.
We did have some of them working on a new mission, which functions kind of like the big mallet and bell at a carnival, where you hit the target with the mallet or sledgehammer and it makes the weight go up and hit the bell, except it's a spaceship that has to go high enough to get into orbit. It's a fun one to work on, although to me it seems more error-prone. I assigned one of the team to be in charge of thinking about risk vs. reward and the likelihood of something working or not working to help us focus on the things we know we can accomplish and get some points out of. Not that we shouldn't try hard things, but we want to get some points.
We did confirm the name Digicorns. I guess they're all set on that, so there we go.
We broke out on Wednesday and Thursday of this week into groups and had various people working on different missions. One of the missions is close, with the group that has been focusing and working on things. Focus is definitely an issue, as we have a lot of kids and it's difficult to get them all on task at the same time. We've had some parents coming in to help with crowd control a bit, which has been good.
We did have some of them working on a new mission, which functions kind of like the big mallet and bell at a carnival, where you hit the target with the mallet or sledgehammer and it makes the weight go up and hit the bell, except it's a spaceship that has to go high enough to get into orbit. It's a fun one to work on, although to me it seems more error-prone. I assigned one of the team to be in charge of thinking about risk vs. reward and the likelihood of something working or not working to help us focus on the things we know we can accomplish and get some points out of. Not that we shouldn't try hard things, but we want to get some points.
We did confirm the name Digicorns. I guess they're all set on that, so there we go.
Wednesday, November 14, 2018
The Mission
For our second meeting on November 14, we talked about name options some more. The two top names ended up being Digicorns (portmanteau of Digital and Unicorns) and Rockets. My preferred name from last year, Botrockers, didn't make the final list, which was unfortunate. I told them we would decide between the two names the next week after they had a chance to think about it and make sure they felt good about it.
We also finished building the stock robot this day. A few of the missions were built, so we could show how to do them. We also watched some videos of other people solving the various missions. They had a homework assignment to go home and watch some videos of the various missions and decide which ones they wanted to work on, based on what they thought they could realistically accomplish.
A big issue at this point was realizing the competition is going to be on January 5, instead of February 2, giving us a month less time to get ready.
We also finished building the stock robot this day. A few of the missions were built, so we could show how to do them. We also watched some videos of other people solving the various missions. They had a homework assignment to go home and watch some videos of the various missions and decide which ones they wanted to work on, based on what they thought they could realistically accomplish.
A big issue at this point was realizing the competition is going to be on January 5, instead of February 2, giving us a month less time to get ready.
Wednesday, November 7, 2018
New Team New Name
I haven't been keeping up with writing down what we've been doing each week. So I'm going to try to go back and reproduce things here as to what we've done over the past month. Our first meeting was on November 7. We kept things fairly simple and talked about team name ideas, introduced everyone, and talked about what some of the missions would be.
We also started building the basic robot. The field wasn't put together yet, but the plans were to have it ready in the next week or two.
We also started building the basic robot. The field wasn't put together yet, but the plans were to have it ready in the next week or two.
Wednesday, October 31, 2018
No, really
I thought we were ready to start our season earlier than we did last year. I guess we will be starting about the same time. We have an official competition in 3 months, so we have a more firm deadline than we had last year.
We have a good mix of those who have experience from last year and new team members. We also have a mix of boys and girls, which I think will be good. We had a lot of bouncing off the walls on last year's team.
I think we are setting a good foundation for the next couple years with several younger students. Our first meeting is next week, so here we go! No, really this time.
We have a good mix of those who have experience from last year and new team members. We also have a mix of boys and girls, which I think will be good. We had a lot of bouncing off the walls on last year's team.
I think we are setting a good foundation for the next couple years with several younger students. Our first meeting is next week, so here we go! No, really this time.
Tuesday, September 25, 2018
New Year, New Lego Challenge
We are starting earlier with our Lego teams than we did last year. Last year we had our initial information meeting in October and didn't start meeting until November and didn't have the challenge kit set up until weeks after tournaments had already taken place after the first of the calendar year. This year, we had an information meeting in early September and almost have the teams all nailed down.
There are two or three times as many students interested in doing Lego Robotics this year compared to last year. There are many new students and many who have experience. We went into things last year knowing we were just setting the stage for this year. I look forward to seeing how it goes.
There are two or three times as many students interested in doing Lego Robotics this year compared to last year. There are many new students and many who have experience. We went into things last year knowing we were just setting the stage for this year. I look forward to seeing how it goes.
Tuesday, August 28, 2018
Subscribe to:
Posts (Atom)