Monday, August 3, 2015

Braxton SL1

Intro: Skip to the last page of the intro.  There are three questions.  The author suggests that if your answer is no to the questions, continuing is a waste of time.  If your answer is yes to each, please also explain WHY you are willing to go through this pain, because it will be painful if you want to truly be a better leader.

My answer to each is yes, and I am willing to go through this as it will not only improve my experience and abilities in robotics, but it will also improve my skills for the future, and having the skills of servant leadership as this book discusses can be very valuable in the future.

Chapter 1: Explain the differences between leaders and managers.  Would product owners and scrum masters be leaders, managers, both, or neither?

The difference between leaders and managers is that when you lead, you inspire and influence people to work together, while when you manage, you're running day-to-day tasks in a company, team, division, etc. Our scrum masters and products owners would be both, managing the tasks of operating and constructing the robot, creating the backlog list, running meetings and planning poker, etc., as well as inspiring, motivating, cajoling, and influencing team members to actually work and make a difference on the team.

Chapter 1: The word "influence" comes up dozens of times in the first chapter.  Why does Hunter keep talking about it?

Hunter keeps talking about influence as  he says that leadership is a personal business, and that a leader is a large part on the lives of those he's leading, the cause of personal development, dinner conversations, likes and dislikes, and more. Therefore, the leader influences those he/she leads, and this emphasis is to drive home this point throughout the chapter.


Chapter 2: What is a legitimate use of power by the leaders of a FRC team?  How often should this be used?

On an FRC team, legitimate use of power is usually just applying pressure on team members laying about and not doing their job in a pinch, however that doesn't really work in the long term. In most situations where power could be applied, it is simply preferable to try to influence lazy workers to do better; late projects (but not too late) are better done by a team, not a hero; and rival designs are better tested than shouted down. Power is good for last-minute situations or as a short term solution, while authority can be permanent and long-lasting if applied correctly, and by the right person. Due to its short term nature, power should be used sparingly and for emergencies, not every day.

Chapter 3: Hunter lists a number of history's greatest servant leaders: Jesus, Ghandi, MLK, and many more.  Name one person who has earned authority over you because of their service in your life.  Give a few concrete examples of what they do that earns them authority over you.

Instead of listing one person, I'll name two: my grandparents. Since we've lived in the same town since 2007, they've helped a lot with raising my brother and I, they've chauffeured us round when we need  ride, they've provided food, a place to stay, advice, and more. 

Summary:

In this first part of the book, I learned bout the basic principles of servant leadership. I learned about the difference between power and authority, the difference between leading and managing, and the importance of influence in leadership.

Nate 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?
We are okay at getting in and getting to work.  We have people who are now very good at certain team functions and have their purpose.  The problem is we are not always letting everyone try things and find their purpose.

Chapter 7: How does our team do a good job of being transparent?  Where is it opaque and unclear in its workings?  Be honest.
Our team is good at being transparent because we tell Pethan what we are doing, whether it is a good or bad idea.  Though sometimes we tell him after we try and break something.  We also have a problem of not allowing ourselves to see when we should work and when we should take a break.  We had many problems of being unfocused during crunch time, or we tried to go too long when we had time to slow down and take a break to clear out minds.

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?
We would need someone who can stay focused for extended periods, able to work with everyone, well organized, and can keep themselves updated with what is going on.  We could use a couple people to do this (maybe 2-3) because it is difficult for people to always be there, so that job could be done with shifts as long as we had a system to keep all of them informed on what happens.

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.  Getting people to join-We rely on the interest of students and adults to join the team and build it up.
2.  Finding a place for people-It is best for us to retain team members and allow them to get good at things and try many aspects of the team.
3.  Communication-When we work as a team and collaborate efficiently, we can produce a better robot.
4.  Money-We need money to support the purpose of out team, to build a robot.
5.  Building the robot-This is the point of FRC, but the other priorities are necessary for this to happen.

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.
In the Uganda story, scrum was used to improve the lives of impoverished farm workers.  They tracked selling prices and used technology to keep plants healthy.  This increased both the yields and earnings of the food.  This get me excited because it shows how quickly the scrum method can improve situations.

End with a summary of what you learned.
In this section I learned about implementing the scrum method.  It shows the necessary parts that have to be there in order to work.  Also, the last chapter proved that this method does work in many scenarios, so this method can greatly improve our team.


Bryan SC3

  • Chapter 7: How should the sprint retrospective work?  What questions should you ask?  Who should participate?  What should you do with the result?

The sprint retrospective should work by having everyone who was working in the sprint tell about what they got done and how they did it. They should be able to confidently tell us how they completed the task and how long it took as well as telling us how we could have them work more efficiently. What we should do with the result is to look at it and figure out how we can become a more efficient team.

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

Well, as a team we have started becoming student led. We have been doing well at allowing everyone to do any task that they want. Now, we didn't always have people work on prioritized things. We had some people at specific points work on only filler jobs and not high-priority jobs. 

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

Our team does a good job of organizing our tasks. We have a board in Pethan's room that tells what tasks are being done and by whom. It also tells everyone how far they are with the completion of that task. There is a problem though, Pethan's room is really out of the way and I have had experiences where I am running down to Pethan's room to only find that the person I needed to talk too had just left the room. All in all, we are very transparent for the most part.

  • 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?

We are looking at the exact same values for an FRC product owner. We need one that is knowledgeable, empowered to make decisions, available to the team, and accountable for value. I personally think that theoretically we don't need more than one, but we will most likely need a maximum of 2.

  • 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 robot
2. Having an understanding of the game
3. Having an understanding of the robot
4. Getting sponsors
5. Having solid organization

Summary:

I have learned about transparency, autonomy and how scrum works. It has really given me a solid understanding of how our team will be working in the next few years.

Sunday, August 2, 2015

Dan SC3

  • Chapter 7: How should the sprint retrospective work?  What questions should you ask?  Who should participate?  What should you do with the result?
Everyone involved in the sprint should be present, and asked about what they got done and what would allow them go get more done (what is getting in their way) and how they will do better for the next sprint.  The result should be used to increase productivity and remove obstacles stopping people from working.

  • 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 does a great job allowing anyone who wants to participate in a task to do it, and allow people to choose to an extent what they want to do, which makes them more motivated to do it.  We fall short sometimes with divisions between teams such as mechanical and electrical blaming each other for things however for the most part I don't think there is much of a division there, we have fun with it.

  • 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.  Improving community (via any method, doing well with the robot, improving stem, community service, as well as growing our team since we are improving the stem field then)
2.  Preparing participants for future in Stem
3.  Having fun 
4.  Getting capital to do #1 aka sponsors
5.  Building an awesome robot

  • 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?
We are looking for someone who understands all the fields tasks could include to an extend and understands what is most valuable given the setting during the build season.  Someone who isn't bias towards certain ideas and looks purely for what is most valuable.  I think a small team of these people would be ideal because it lessens the chance that decisions as to what is most valuable is less likely to be bias.

  • Chapter 8: The example of the security company prioritizing the lens prototype was a great example of minimizing technical risk.  What decisions should we have prioritized in recent seasons to minimize technical risk?
The type of cams we used, the type of extensions,  we could have built many different types of cams and had them all made at the same time and tested which are the best and why and be able to improve the design from there.    

  • End with a summary of what you learned.
I learned how to sustain a good scrum team, via building a team that is autonomous, motivated, and striving to improve, how to prioritize choices.

Dan SC2

  • 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? 
Titles create less ocmmunication saturation, because of the specialization, titles make people feel that they are above doing a task that isn't in their scope of the title.  Titles can be a positive thing on resumes and other applications for applying to a job or college.
  • Chapter 4: The daily scrum should be "closer to a football huddle [than individuals reporting out]".  Explain why.  
It is just to get people unblocked in what is stopping them from their task and to make sure progress as a team is being made

  • 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 of how your brain functions, it generally can only work effectively at one thing at a time, and it takes your brain time to switch gears between tasks if you are multitasking.  In my own life I refuse to multitask when driving (Mainly regarding my phone, turning the radio up or down is different), I don't feel like I can drive safely if I have a phone pinned between my cheek and neck or texting looking away from the road for multiple seconds at a 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?
If you need a hero to get things done your planning failed.

  • Chapter 6: An phrase popularized by Eisenhower says "the plan is worthless, but planning is everything".  Explain this in the context of the chapter.
You should only plan what you need to, enough to keep working but not too far in advance, as a year long plan won't remain accurate and applicable. 

  • End with a summary of what you learned.
Overall I learned that less is more sometimes to the amount of hours you contribute, and that multitasking is even more of a waste of time than I already thought it was.  

Dan SC1

  • Chapter 1: Explain the planning process for the new FBI system "Sentinal".  How was a Gantt chart used in the process?  What is Sutherland's beef with this kind of planning?

The planning process was all done before hand using the waterfall method, intelligence teams would figure out everything that needed to be done and how long it would take.  Sutherland's beef with it is when the plan meet reality it commonly falls apart, and managers hire people to make it look as if the plan is working.

  • 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?
A few of the improvements that added a large amount of value would be the temporary wooden triangles that more easily centered the totes, the triangles which allowed us to intake better, and the slants on the guide rails that made totes fall flat the first time.  Those few small things made us from an ok bot to being able to compete at state (and compete decently at state).

  • 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?
You need to do this to be able to show progress to any stakeholders as well as be able to show it to the consumer (FBI employee's) to get feedback on what they did.  Real time feedback is one of the most important things a product can have.

  • 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 implement it by around a meal having everyone stay after and have them do Southerland's paper airplane challenge, and after you have everyone reflect upon how they could apply the concepts they used to build more paper airplanes that could fly across the room to how to develop better pieces of a robot faster.

  • 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.
Our team wanting to be great, we work on our own without being told to (involving both the community and the robot), and being able to understand what everyone else is doing.

  • End with a summary of what you learned.
I learned how understanding what will improve the product most (generally via the consumer) is important (makes a lot of sense just never really thought about it), and that real time feedback is a great way of achieving this.  I also learned of how prioritizing what adds the most value is important because at a lot of times last year I feel that myself and others didn't do this and it would have greatly improved the robot.

Tuesday, July 28, 2015

Nate SC2

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?
Titles can cause people to abuse power and can slow work down.  A manager guides a group, but they take a bit of the employees voice away.  In our team waiting to check with a mentor or team lead has caused us to delay getting things done.  That being said, a title ca mediate between different ideas if there is a split in how something could be done.

Chapter 4: The daily scrum should be "closer to a football huddle [than individuals reporting out]".  Explain why.
A football huddle is a way to let everyone know what is going on, and the goal you have as a team.  In a football huddle most people will have different jobs but all be working towards the same goal.  In this technique everyone is up to date on the plan for the day, and everyone has a job they can do.

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 can't focus well on multiple things at once.  Multitasking does not get things done faster, it usually takes longer and produces a lower quality product.  In my life I always refuse to multitask.  I find focusing my energy on one thing to be much more efficient and effective.  The closest I get to multitasking is switching periodically from one assignment to another when I get stuck so I can come back with a fresh perspective.

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, this course is halfway completed.  I can't think of any we currently have half done.  But we do have a tendency to start something and not finish.  This is a problem because we forget how far we were and many times have to restart.

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 a way for people to more accurately decide what tasks are most important.  It allows for an accurate estimation and uses the Fibonacci sequence because menial tasks do not vary in difficulty much, but strenuous tasks can vary more greatly in difficulty.  It eliminates the halo effect of people automatically siding with a person.  The people who play it should be those who are familiar with the tasks and can justify their reasoning accurately.  If there is too great of a difference the highest and lowest numbers should explain their reasoning and everyone repeat the poker hand.

End with a summary of what you learned.
I learned the importance of organization during work.  It is needed to efficiently complete a task.  Prioritizing tasks allows for work to be done in a sensible order, and it organizes work in order to eliminate inefficient multitasking and less important jobs.  We do not necessarily need to work at robotics for 10 hours a day and go to school.  If we use our time wisely and recognize when we are being inefficient we can get our work done much faster.  Skills from this book can help our team a lot.