Tuesday, August 11, 2015

SL1 Bryan

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

Leaders are people that can make others work willingly. Managers are people who can manage the team and organize things. Scrum masters would be like leaders because they are leading the team and product owners would be managers.

  • Chapter 1: Hunter says that leadership is a skill, not something many are born with.  Do you actually believe this?  Have you always believed this?  What evidence have you seen in your life to back up your response?

I believe that it can be a skill or can be something you are born with. I think this way because I have seen leaders since I was a child and I have seen people become leaders through work and effort so that they can become the best leader that they can be.

  • 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 because it is critical to have to become a leader. I you can't influence how can you do your job as a leader?  If you can't influence people how can you get people to work?

  • Chapter 2: In what places in your life have you earned authority?  How did you get it?

I have earned authority only a few times in my life, but I got it due to respect and trust. Now, I may not be the most respectable person or trustworthy, but when I need to be authoritative I will take charge.

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

My mother has earned authority over me because she brought me into this world. That is really only the only real reason, but it is a pretty good reason.

Summary:

Leaders are people who need to be able to make others work. They need to be responsible and able to work, themselves. Leaders can be born and can be trained.


Jacob SL1

  • Chapter 1: Explain the differences between leaders and managers.  Would product owners and scrum masters be leaders, managers, both, or neither?
A leader is someone who can influence followers to work fully towards a mutual goal or gain while a manager is someone who is tasked with making things happen on time in a certain way.  A manager doesn't always have authority but they are given power over the people they are managing so they can get a task done.  Scrum masters and product owners would have to be both manager and leader since although a leader can get people to follow them, they need at least some managerial skills to handle things like deadlines and problem causers.
  • Chapter 1: Hunter says that leadership is a skill, not something many are born with.  Do you actually believe this?  Have you always believed this?  What evidence have you seen in your life to back up your response?
I am sure that leadership is a skill that can be learned and I have always been pretty sure of it.  There is probably a set of genes which, if someone grows up in the right environment, will allow people to be great leaders, but Leadership definitely isn't just genetic as evidenced by the thousands of inheritors who squandered their parents authority, power, or money.  I've also seen people become better leaders simply through practice in groups at school.
  • 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 because it is central to being a leader.  People in charge can have different kinds of influence over others; there's the "I'll get fired if I do this wrong" influence, the "that guy helped me out last week so i'd love to reciprocate" influence, and many others.  The kind of influence you have with your workforce shows what kind of a leader you are.
  • Chapter 2: In what places in your life have you earned authority?  How did you get it?
I have earned a not so small amount of authority in school based concepts.  This is especially true for math since I have consistently done well in the subject and helped other people to do the same.  I also have a significant amount of authority with my brother since I have on more than one occasion covered for or helped him in situations which he didn't necessarily know how to deal with.
  • Chapter 2: What is a legitimate use of power by the leaders of a FRC team?  How often should this be used?
Using power to make others accomplish a task is actually somewhat difficult on FRC teams since there is little to threaten a dissenter with.  Obviously somebody could be kicked off of the team or removed from a project, but since the entire FRC experience is on a voluntary basis and we really need the people we have, both of those are unlikely.  Thus, we should only use power sparingly.  If someone is preventing a deadline from being reached or causing arguments, power could be used, but just as equally someone could simply tell them what is going on and try to work it out.
  • Summary
In these chapters I learned a little bit about the difference between managers and leaders, the difference between power and authority, and how your influence with your employees depicts your leadership or management style.

Monday, August 10, 2015

Braxton SL2

Chapter 4: Describe the difference between love, the feelings, and love, the choice.

The difference between the feeling of love and the behavior of love is a big one. While love the feeling is all bout 'romance, flowers, and candy', the act of love is for more than just your close friends and family. It is about caring for your employees, colleagues, and clients. It is helping them and serving their collective needs, even before your own. It is a useful skill for good bosses and managers to possess.

Chapter 4: Four communication styles are aggressive, passive, passive-aggressive, and assertive.  What is the ideal form that we should use?  What have we primarily used in the past?

On our team, the ideal form of communication that we would use is assertive. It is honest and to the point, without causing difficulty long the way. In the past, however, we have used ll of the other forms, in different ways and with different people. There have been petty plots and feuds that fall into passive-aggressive category, moments of passivity towards people not working or taking an indefinite break, and moments of aggression towards one another. No one single type was used the majority of the time. The rare moments of assertiveness were our most productive as well. 

Chapter 5: If you had to create a survey that collected final thoughts from graduating FRC seniors, what do we need to hear from them?  How could we make them feel comfortable about being open and honest without holding things back?

Some of the things that would be helpful to hear from graduating seniors would be insight such as what improvements they would make, best moments, worst moments, how they felt about how often we met, whether they felt they got value out of being in FRC, etc. Some ways we could ensure they are comfortable with open honesty would be anonymity, a disclaimer about how these answers would be used to improve the team, etc. I'm not a professional survey-maker, so I'm not sure what more we could do on this front.

Chapter 5: "Love without discipline is not love at all."  Provide some insight into that statement.

In this case, the quote means that if you truly love your employees (verb-wise), and want to serve them, you must discipline them when they do wrong and hold them accountable. Otherwise, you hurt the other employees and yourself in the process. Therefore, you must either discipline, keeping in mind that discipline in this case is a helpful, not hurtful, process, or remove them from your organization.

Chapter 7: Change is usually initiated by friction / discomfort / pain / suffering.  If you want to change your habits, where will the discomfort come from that motivates your change?

One discomfort that could motivate change is a time inconvenience. For example, a simple task that should only take a day ends up taking a week, and this ends up happening a lot over the next few months. My productivity has tanked, and I'm suffering losses due to that. This would motivate a change.

End with a summary of what you learned.
In this section of the reading, I learned about people's characters and personalities, just what is love, different types of communication, personality, and character, and much more. This can all apply to myself and how I lead.

Wednesday, August 5, 2015

Ben SC3


  • 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 very transparent with how we feel about designs and is always vocal. We tend to get more opaque when changes are being made, since not everyone is present every day. Sometimes, leadership is opaque as well, since some leaders never actually showed up, or they were irresponsible and unhelpful.
  • Chapter 7: How does our team do a good job of supporting autonomy, mastery, and purpose for each person?  Where does it fall short?
    • I think when we distribute jobs and have each small group figure out how to complete them on their own, it does a good job at supporting autonomy. We do a pretty good job at letting people discover what subteam they belong in. People can try out mechanical, or electrical, or programming. A shortcoming of ours is that when we have people we feel are unhelpful or annoying, we tend to 'dump' them on media. I think we could spend more time working with that person and let them try out different teams, see what is the best fit for them.
  • 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. Set up and comprehend our leadership system
    • 2. Have students leading design, meetings, outreach
    • 3. Have a vast understanding of the year's game
    • 4. Efficiently build a well functioning robot
    • 5. HAVE FUN! (by winning)
  • Chapter 8: Sutherland and others say that authority and leadership should have nothing to do with each other.  Do you believe this is true?  Explain with a concrete example from your own experience.
    • I agree with this, it seems as though authority is the control over someone via punishments and rules. Not trying to start anything here, but there are cases in which teachers use authority, not their leadership, to guide students: making kids do homework not because they want to learn and develop, but with the threat of detention and failure. Leadership is motivating people to do what needs to be done, going through the adventure with them, being a guiding light. This is like when captains of a team will help their teammates up, push them to do better, watch their backs and such.
  • Summary
    • I've learned how to implement scrum, what true leadership is, knowing what is important, and the importance of whole team involvement. It is hard to have one person guiding everyone, so have many people working together, sharing ideas as equals, keeping things moving smoothly.


Ben 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? 
    • People with higher titles might feel as though they shouldn't have to do the simple and laboring tasks. People with inferior titles might be afraid to share ideas that could revolutionize the whole process. Along with the negatives, there are also positives. Titles can help with resumes and applications, but more importantly, they can indicate someones specialty. Everyone is a team member, but not everyone can handle different aspects the same as someone else.
  • Chapter 4: What is the purpose of the sprint?  What are the rules that govern a sprint?
    • A sprint is time in which a team will have assigned a number of tasks that have to be completed by the team. It is used to get a lot of work done in a small amount of time. It is governed by the jobs that need to be done.
  • Chapter 5: Why is multitasking wasteful?  When in your own life do you refuse to multitask and just focus on a single task?
    • It is easy to lose track of thoughts and ideas when multitasking. You aren't doing the best job you can, and it takes you longer to do each individual task than it would if you sat down and focused on one at a time. When working on reports, essays, and eating, you shouldn't multitask, the quality of work will suffer, and you don't realize how much you eat, causing you to over-eat. 
  • 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?
    • At the end of the regular season, we had the idea of making a robotic arm, we never completed this task. I could be wrong, but I don't think we even got started on it. 
  • 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' is that a task or product has been completed to its entirety. The product is able to do all the jobs required of it. Everyone needs to understand this because if they don't, it is very likely people will start a task and never finish it. They'll begin building or designing and decide they're bored. From there, they could think the product is complete.
  • Summary
    • We learned about the various parts of scrum, such as sprints, DoD, the wastefulness of multitasking, lack of titles, and such. They are essential to a fluid and efficient work place and need to be implemented for maximum creativity and results.

Tuesday, August 4, 2015

Jacob SC3

  • Chapter 7: How does our team do a good job of being transparent?  Where is it opaque and unclear in its workings?  Be honest.
In our team, it is easy to walk down and ask about or just look at what is being done on the robot.  We also made our general strategy pretty available as well.  That's where the transparency starts to deteriorate: changes in design (front/back load, wheel arrangement, drive train, etc) are not always communicated to all members, there is a very apparent divide between the programming, mechanical, and media people with each doing their own thing, and I personally have had to deal with the challenges of what people want while designing CAD models.  This lack of transparency caused many delays last season and it needs to be fixed.
  • Chapter 7: Sutherland talks about the importance of measuring velocity every sprint (even though it can be tedious at times).  How does knowing velocity affect a sense of growth?  Why is it needed to identify the "happy bubble"?
Any business cannot know it's success if it does not have an idea of it's velocity.  Velocity means speed in a given direction so to know ones velocity is to know how quickly a business is approaching or passing it's goal.  If it is moving rapidly in the right direction growth is good and is perceived as such.  If it is not moving, but the company is happy a happiness bubble may be forming.
  • 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 a FRC team a product owner would have to have a great understanding of the rules of the game and what role the teams robot is supposed to play.  They would also need to have an idea of what can actually be made and an idea of a time frame for these things.  This would require somebody who has at least a baseline understanding of every section and knows a great deal about the majority of pieces or is willing to work with others to arrange tasks for their weak areas.  For our team we might need more than one product owner;  this is largely due to the transparency issue I mentioned earlier since most people are rather restricted to their faction and don't know much about the others (mechanical/media).  If we fix this problem it could become feasible to have only one, but they would have to be around all the time and be well informed on just about everything.
  • 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. Prepare kids for future involving STEM principles
2. Build an amazing, functional, and legal robot
3. Recruit new people who are willing to learn
4. Raise money and awareness
5. Have fun (make it to nationals/worlds)
6 or 1. World domination (don't tell Paul we're doing it without him)
  • 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 chapter that struck me as most significant was the application of scrum in schools.  The teacher literally had the students divide themselves up into cross functional teams and organize their own learning.  This has alleviated some of my worries since this worked so well in a high school I really think it can work on our team
  • Summary
In these chapters I learned about transparency and how essential it is, how happiness affects results, and about a few real world situations where scrum was used.  The situations especially helped me to understand how our team can implement and use scrum to improve our productivity.


SC3

Chapter 7: How should the sprint retrospective work?  What questions should you ask?  Who should participate?  What should you do with the result?
Answer: This is captured at the end of each Sprint. what went right, what could have gone better, what can be made better in the next Sprint. Requires a certain amount of emotional maturity and an atmosphere of trust. Hear the feedback, take it in , and look for a solution rather than get defensive.

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

Answer:When we do a mistake we learn what not to do next time and know not to do that next time. We allow people to make mistakes but also help them if they need. Also overtime we learn things and when we do it a lot you get pretty good at it. Doing something for a while we learn different things and we could overtime master. The purpose for the person is because they can both learn and help with things that they might of not done before but they are also given a place they can be themselves. Where things cut short is when you if you have to many people and can't have more come or if someone does do autonomy as well.

Chapter 8: Sutherland and others say that authority and leadership should have nothing to do with each other.  Do you believe this is true?  Explain with a concrete example from your own experience.
Answer:Yes. I don't have much experience but I would think that they shouldn't have nothing to do with each other because if you have an authority over someone it might be a little hard to show leadership. Also when you have to show leadership, you should also do things that shows you are a leader.
 
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.
 

Answer: 
1.Working robot
2.know the game/rules
3.know how the robot works(controls, which buttons are used, etc.)
4.sponsors
5.students/mentors

Chapter 8: What does a minimum viable product (MVP) robot look like?  Who are the customers of our robot during the competition season?  Does the customer change in the post-season?
 

Answer:One that is very effective, actually works, maybe be able to do things fast. Sponsors, people who are cheering for our team. Yes.

 
Summary:
I learned that scrum is more than just helping you figure out how long something might take. It also helps you know what things should be done first before others. It shows that when working on multiply things at a time will cause then not to be done soon.