Tuesday, July 28, 2015

Braxton SC3

Chapter 7: How does our team do a good job of supporting autonomy, mastery, and purpose for each person?  Where does it fall short?

Our team supports autonomy for its members by allowing everyone, more or less, to participate in discussion about how to build or design a part, what design our logo should have, etc. Anyone can be on an independent team or group that decides how to go about a task, and they can provide vital input on that team. Mastery is supported by the same system, as people can do any job they want, as long as they want, at least in theory. They can work at crimping wires until they have carpal tunnel, or they could CAD until they collapse from exhaustion. Purpose even falls into the same system. However, these are only in theory. At times, like the corporations of old, we can be highly divisionalised. Sub-teams and sub-sub-teams can oftentimes have their one culture and codes, putting up hypothetical barriers between each other. However, this problems is not as bad as it could be, but there is still room for improvement. 

Chapter 7: How does our team do a good job of being transparent?  Where is it opaque and unclear in its workings?  Be honest.

One of the best things our team does in terms of transparency is the team's shared folder of info. Anyone on the team can look at our financials, our survey results, our award documents, team lists, and more. Anyone can attend our meetings (most of them, at least), and offer input on how we should proceed. We all know what tasks need to be completed, and we fill in those who don't and they can look at our scrum board to see who is working on what, what's done, what needs to be done, etc. However, our team isn't ideal. Only a few of our documents in the shared folder are up-to-date, and a few are hidden in endless trains of files. I suppose if one wants to know out of date mid-season financials from 2014, or team member lists last updated 3 years ago, then these docs are for you, but otherwise, sometime in the next few months, there should be a widespread effort to update or purge the documents in there, and then organize them better for easy access. We also sometimes have problems with keeping on scrum board up-to-date at times, since its all the way down in Pethan's room, but that's only a small issue. All in all, our team is pretty transparent, but there is, as always, room for improvement.

Chapter 8: A product owner needs to be knowledgeable about the domain, empowered to make decisions, available to the team, and accountable for value.  What specifically are we looking for in a product owner for a FRC team?  Do we need more than one?

In an FRC team, we're looking for many of the same traits. For example, the product owner needs to be knowledgeable bout the tasks necessary for the robot and the team, not only knowing what they are, but also why we need to accomplish them. They need to use this knowledge to create a sizable backlog for us each sprint, and to, long with the scrum master, set up the meetings and clearly explain to everyone the situation with the sprint, what we need to do next, etc. They also, obviously, need to be available to the team. As for needing more than one, it's possible, but I'm going to say no. However, we don't know until we try during a sprint.

Chapter 8: "Prioritizing everything is prioritizing nothing."  What do you think are the five highest priority items for our FRC team?  Put them in order 1-5.

  1. Having a functional bot by competition
  2. Having a working understanding of the year's game, and how to coordinate strategy with alliance mates
  3. Securing sponsorships and funds through various channels
  4. Submitting a finished chairman's appliction for 10 points in the state rankings
  5. Submitting other award applications, finished of course
Chapter 9: Summarize one story from Chapter 9 and explain why it gets you excited about using a proper implementation of scrum with our FRC team.

The Valve story: Gabe Newell and his compatriots in Microsoft left after there were problems relating to Gabe's team structure. They left to form their own company, Valve. The new company had a flat structure and often used scrum to create their products. Nowadays, Valve is known for products such as Steam, Counter Strike, and Half-Life, wildly successful in the gaming market. This gets me excited about scrum because I use Valve products such as Steam and Counter Strike, not knowing they were the product of scrum, or that the company that made them had an extremely flat corporate structure. Now, Valve isn't perfect, but it's products are oftentimes high quality, and so a process that has worked for them, as with so many other, could work for us, and that's why this story got me excited to use scrum on our team.

End with a summary of what you learned.

In this book's final section, I learned bout some of the key aspects of scrum, such as prioritization, transparency, and autonomy. These are extremely important aspects of any scrum team, and implementing them is crucial to any successful team.

Monday, July 27, 2015

Kaitlyn SC2

Chapter 4: What is the purpose of the sprint?  What are the rules that govern a sprint?

Answer:To find things that cool and that can be built fast. Rules are that if the demo wasn't both working and cool, the lab directors killed the project.

Chapter 4: Sutherland required his first scrum team to throw out all titles.  Why?  Where (inside and outside FRC) have you seen titles get in the way of getting things done?  Where can titles be a positive thing on a team?

Answer:Because if people have a special title, they tend to do only things that seem a match for that title. And to protect the power of that role, they tend to hold to specific knowledge. Jobs because if you have a higher status then a new person you can do more and can maybe get away with something. Different sub teams on robotics teams. They can be positive because it can show which person you can ask if you need help on something. Or to show what person is able to do.

Chapter 5: One section is titled "half done isn't done at all".  What are some half-done tasks we have with our FRC team?

Answer: When we were working on the chairman's award, we had some done but when we got close to the competition we worked on it till we pretty much had it done.

Chapter 5: We're used to the idea of a hero working extra hard to save the day.  Why does Sutherland hate on the hero?

Answer: That a team that depend on regular heroic actions to make its deadlines is not working the way it's suppose to work.

Chapter 6: What does the "Definition of Done" mean?  Why is it critical that the entire team understands the DoD for each task?

Answer:When the conditions needed are met and that it passes the tests needed to pass and to say that is is done. They all have the same task that they got to complete and they all have the same requirements.

Summary:
I learned that are easier ways to get stuff done without wasting to much time or money. Also when doing multi projects at a time, it takes longer to complete and and loss to context switching increases per project. I also like how they have sprints, which is an interesting challenge but it can also create cool things too.

Bryan SC2

  • Chapter 4: What is the purpose of the sprint?  What are the rules that govern a sprint?

The purpose of a sprint is to have a brief amount of time in which the team or group is extremely productive. A rule is that the amount of time has to be limited and it has to have tasks assigned to specific people or groups of people.

  • Chapter 4: Sutherland required his first scrum team to throw out all titles.  Why?  Where (inside and outside FRC) have you seen titles get in the way of getting things done?  Where can titles be a positive thing on a team?

It was just getting in the way of working because they just marked the person. This way they would be more productive rather than pulling the "I'm the boss" card. I have seen people on our team and other teams saying that since they are the whatever captain they get to control the work being done in that specific group of people and just end of not doing any of the work. Titles can be use for getting scholarships as well as being able to compete. Well, we need a safety captain due to ya know, safety as well as being able to participate in competition.

  • Chapter 5: Why is multitasking wasteful?  When in your own life do you refuse to multitask and just focus on a single task?

Multitasking is wasteful because you don't do as good of a job when you are doing multiple things at once. If you just do one thing at a time, then you can get it done faster and better. Usually, I try to multitask as much as possible and it usually turns out well, but I know that if I focus on one thing it will turn out better than both things at once.

  • Chapter 5: One section is titled "half done isn't done at all".  What are some half-done tasks we have with our FRC team?

Well, we had the Best Buy grant which I am pretty sure never even got done in time, but I could be wrong (this is just from what I heard). Also, we had the chairman's presentation maybe half done for a long time, until the night before the presentation, which should've been done way earlier. 

  • Chapter 6: What does the "Definition of Done" mean?  Why is it critical that the entire team understands the DoD for each task?

The "Definition of Done" means something has been thoroughly examined and tested and is able to be handed over to the customer or consumer for use. It is critical that the team understands the DoD for each task so we can get it done to the same standards as we need, so someone doesn't finish it when it really isn't finished at all.

Summary:

This part was to explain parts of scrum and how we should use them. They are very important parts of scrum and should be looked at as such.

Friday, July 24, 2015

Jacob SC2

  • Chapter 4: What is the purpose of the sprint?  What are the rules that govern a sprint?
A sprint is a period of time in which a team set's aside a number of tasks to be completed.  At the end of the sprint the team evaluates what happened adjusts and repeats.  A sprint is meant to get a lot of work done in a short period of time and is governed by the tasks/stories that have been laid out for it and the amount of time it takes.
  • Chapter 5: Why is multitasking wasteful?  When in your own life do you refuse to multitask and just focus on a single task?
Multitasking is wasteful because you lose time switching back and forth between tasks.  Actually multitasking is really just juggling between two things and the brain just isn't equipped to do this.  I refuse to multitask whenever I do homework since if I get distracted I tend to stay distracted for a long time.
  • Chapter 5: We're used to the idea of a hero working extra hard to save the day.  Why does Sutherland hate on the hero?
I'm not sure that Sutherland hates people who act as a hero, but rather the fact that they have to.  If a hero is needed to finish the project on time then obviously the team isn't doing it's job right.  There is also the fact that a hero is a single person and Scrum is all about improving on the team.
  • Chapter 6: Explain how planning poker is supposed to work.  Mention the halo effect, Fibonacci numbers, who should play it, and the discussion that should occur when estimates vary too much.
Planning poker is when people use cards with numbers from the Fibonacci sequence on them  to try to rate the difficulty of a task.  It is designed to be quick and to avoid the halo effect of someone seeming like they know what they are talking about and everyone thinking themselves wrong.  Each person lays down a card with one of the numbers and as long as they are all within one of each other they are averaged.  If they are not, the high and the low each explain why they think theirs is correct and the cards are played again and averaged.
  • Chapter 6: What does the "Definition of Done" mean?  Why is it critical that the entire team understands the DoD for each task?
The definition of done refers to what needs to be accomplished for a task or story to be considered complete and moved out of in progress.  This is critical, because if definitions of done vary, one team member can think a task is done, mark it as such, and move on to the next one.  This is a problem because a task that isn't done to the set specs may not work when it is needed.
  • Summary
This section of the book covered quite a few aspects of scrum including planning poker, sprints, DOD, and others.  It also covered how to enact these and why they are used.  

Tuesday, July 21, 2015

Dan LS3

  • Chapter 9: The chapter starts with an example of stuffing envelopes in large vs. small batches.  For what reasons does Ries say the small batches are more efficient?
You know almost immediately if any problems occur in the process as well as in large batches you waste much more time sorting and organizing the different segments of the process. 

  • Chapter 9: "Hardware becoming software", "Fast production changes", and "Rapid prototyping tools" are all things that could help us build a robot more quickly.  Give an example of each of these 3 that we could do.
Hardware becoming software - This has already begun on our team but using CAD to prototype concepts, something we haven't done within CAD however that could rapidly speed things up is designing using parametric constraints which I could explain in person or using a computer but I don't know how to explain here... basically setting CAD dimensions equal to other dimensions so that if you change 2-3 base dimensions the entire object will update to the proportional size (would only be useful sometimes but would save a lot of time when it is).

Fast production changes - If we designed a robot to be flexible to multiple ideas beforehand it would be much easier to adapt quickly.

Rapid prototyping tool - If we build a protobot extremely early in the season and are able to rapidly develop (go through bml loop) it our final robot will be much better as a result.

  • Chapter 9: Both small batch examples (SGW and School of One) should feel somewhat familiar as roboticists and as students.  What do you see in these stories that we don't use at school / in robotics?
They use a feedback loop much more often in their businesses than we do in school or even robotics.  And they are able to work more effectively because of it.  They use their feedback as soon as possible to reiterate sooner.

  • Chapter 10: Shift your focus from building robots to growing our team of students, mentors, parents, and sponsors.  What is our team's engine of growth?
Our team has a sticky growth engine, we rely on getting members and retaining them.  In our specific case next year acquiring people will be more of the problem than retaining others, but in following years retention will become more important as many of the people who were in FLL will join us at least for 1 season and its up to us to make their experience good.

  • Chapter 10: We also lose people (students, mentors, parents, and sponsors).  What things cause this to happen?  Which of these can we control?
We lose people for a variety of reasons which only some of we can control, we lose people to things we cant control such as them moving (can't control) , others we can such as them having a bad experience or commandeering too much of their time (can control).  Sponsors might stop funding us because we don't show appreciation enough (easy to control), or because it just doesn't work for them (can't control).

Kaitlyn SC1

Chapter 1: Sutherland explains the 80/20 rule: 80% of the value often comes from 20% of the work.  In the last year of FRC, what were some of the 20% jobs that added tremendous value to the team?

Answer:What added tremendous value to us was the lifters and the cams. With them we were able to lift and stack totes and bins and drop then off to score points.

Chapter 1: At the end of every sprint (2 weeks in this case), the Sentinal team presented a working demo to stakeholders across the FBI.  Why is this necessary and important to do?

Answer:It can help how long something could take or How many work items they can get done during the sprint. Helps give info that could take longer with the how FBI, but when they let a  few do it then it could take less time and get the results quicker. They can also test things that might not happen now but could eventually, like someone hacking into the FBI and starts to transfer money to a different country, they were able to stop it.

Chapter 2: "OODA (Observe, Orient, Decide, Act)", "inspect and adapt", and "PDCA (Plan, Do, Check, Act)" are all getting at the same core idea.  Explain this idea and how it relates to the way a team functions.

Answer: We observe what area we would work best then we would figure out a way to make us gather stack things faster. And if something goes wrong just do what you think could be best at that time.
 We make plans then when we are ready we do or build it when we have built it we check if it is good enough then we act and do our best.

Chapter 2: Explain how we would implement the paper airplane example to practice a OODA cycle at a team meeting.  What would be the point?

Answer:Before doing things we observe what we are going to do. We will then orient it and decide what will be done. After that they we will act and work on it. See if the things will work or 

Chapter 3: What evidence does Sutherland bring up when justifying a focus on team improvement over individual improvement?  Do you think that should apply to our FRC team?  In what cases does it not?

Answer:Managers. I think it could help because people how haven't been in robotics or are still a little new they could learn from the people who are managers. But it also wouldn't work because sometime teams or places don't need a manager but everyone has a part and they can all help and teach each other.


Summary:
It think book will give us and myself good advice that we could use at robotics but not only that but other places too. This can be very helpful, when doing something because it might take less time to do then you might of  thought before. In the book it also says studies that they have done and have worked. This could help everyone and help reduce the time that is needed for somethings and get them done faster.

Jacob SC1

  • Chapter 1: Sutherland explains the 80/20 rule: 80% of the value often comes from 20% of the work.  In the last year of FRC, what were some of the 20% jobs that added tremendous value to the team?
We had a few small items that had huge impacts on our bot including the cams, the slants on the guide rails, and a few other things. The cams were extremely small and relatively simple, but without them or even with the first version of them our bot would have been nonfunctional.  The slants on the guide rails allowed us to get the first tote flat and relatively center and fixed our yellow tote problem, but they were a late addition that would have helped immensely earlier on.
  • Chapter 2: "OODA (Observe, Orient, Decide, Act)", "inspect and adapt", and "PDCA (Plan, Do, Check, Act)" are all getting at the same core idea.  Explain this idea and how it relates to the way a team functions.
The core idea is that you need to check that what you are doing is making progress towards a true end and pivot if it is not.  All three end with action of some sort; whether this is to change what you are doing or to encourage your team to keep at it, you must make a decision based on what you have observed.  In teams this is used to keep moving in a good direction.  When a team understands what went wrong/right in a scenario and takes action to improve, they become faster and more efficient.
  • Chapter 2: Explain how we would implement the paper airplane example to practice a OODA cycle at a team meeting.  What would be the point?
We would break down into small groups with less than 7 people per and then assign a task.  Time would be set aside for planning, doing, and thinking over how things went and then the process would be repeated again.  The point of this would be to teach students the basic principles of Scrum while building team  bonds and morale.
  • Chapter 3: What evidence does Sutherland bring up when justifying a focus on team improvement over individual improvement?  Do you think that should apply to our FRC team?  In what cases does it not?
The largest evidence that Sutherland brings forward is in how the best teams compare to the worst teams which has a ratio much greater than 10:1 (the comparison of best vs. worst students in a college class).  Sutherland also points to how much teams can accelerate their pace while a single person has their limits.  I think that focusing on team improvement to our team should be incredibly important since we can't rely on one person to get everything done.  The only case I can think of where this principle would not be true would be in single person sports since a single great person can win on their own.
  • Chapter 3: The best teams are transcendent, autonomous, and cross-functional.  In your OWN words, what does this actually look like on an FRC team?  It may help to reference examples from the West Point, NPR, and Special Forces case studies.
The best kind of FRC team realizes that the purpose of their team is to introduce to and teach people about STEM and works towards that goal with a good robot being a side effect (a nice side effect) of the learning.  This kind of team lets the students test and make decisions based on their results that affect the robot directly.  Lastly, in a great team, everyone has a basic understanding of what everyone else is doing and knows what they are all working towards.  This would be a great FRC team and would exhibit transcendent, autonomous, and cross-functional characteristics.
  • Summary
I learned a few things about scrum and how it works such as what a sprint is and how scrum came to be.  I also learned about small teams being efficient, the waterfall method and why not to use it, and how inefficiently teams have been working because "that's the way it's always been done".