Monday, July 20, 2015

Braxton 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 short burst of high-productivity in which a large mount of work is completed, and then the team evaluates what they've accomplished and seeks to improve the process for the next sprint. Some of the rules that govern a sprint are: holding a daily meeting with the entire team, no longer than fifteen minutes, in which team members go over their work and what will prevent them from doing it efficiently; a sprint must not be too long a period of time; and a board featuring the sprint's work divided into backlog, doing, and done columns on which post-it notes with jobs are moved to their respective station.

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?

Sutherland required his team to throw out their titles because practically all of them were simply status markers that only hinder collaboration and cross-functionality, as title-holders simply stuck to their title's job, or what they perceived as their titles job, and they often hoarded valuable info. In FRC, I've seen titles get in the way of jobs and even cause conflict, as arguments and discussions over who should have what title and what their jobs should be have occurred far more often than they needed to. Titles on the team have often caused jobs to be left unfinished, as the respective title holder would 'handle it'. However, this isn't to say that all titles are negative on an FRC team. Most titles, admittedly, are useless and just get in the way (most team leads). However, there are two titles worth keeping due to their benefits, even if they are simply honorary. The first is safety captain, a title required by FRC and an obvious title to keep. The other, overall Team Captain, is very valuable scholarship-wise, and is a title of respect granted to an individual on the team by majority vote. This title, even if simply unused and honorary, is worth keeping for its positive scholarship impact and recognition of a highly-involved student recognized by the team as a whole.


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 a wasteful activity because the human brain can only focus on so many tasks at once, and focusing on too many can cause effort to be wasted due to mistakes, backtracking, and switching projects. One of the times where I outright refuse to multitask is when I'm reading a book. I absolutely cannot read more than one book at a time outside of required reading, as it throws me off plot-wise, and I have to re-read several pages to remember where I was, rather than just a paragraph or already knowing.

Chapter 5: According to the Maxwell curve, an employee reaches peak work completion in a scrum environment at how many hours / week?  Given that we all work on robotics AFTER a full week of work or school, how many hours do you think we should be working each week during the build season to maximize how much we can get done?  How does this compare to how often we met last season?

An employee reaches their peak work completion in just under 40 hours. In robotics, I'd recommend we work around 10-15 a week, maybe more or less depending on the time of the season. This is FAR less than we worked last season, as some of the longest weekends could rack up 12 hours a day. My reasoning for wanting much fewer meeting hours is this: in long weekends, people show up early and start work, although a key person is almost always missing, resulting in blockage. For the rest of the day, people come and go, and someone is almost always out of the loop in some way, and no one knows what we did earlier except for those that were there. By the end of the day, a few hours after lunch, productivity is practically non-existent, and any work that is done is either wrong or esoteric, which is to say known only to the person who did it, who will then have to spend time informing everyone, usually individually. And now, with scrum, we are very quickly running out of work to do, resulting in a very unmotivated group of students in later hours, when the meet should already be over. The latecomers also tend to lack jobs, as they've all been done already by everyone else in 3 man teams, leaving unproductive students. These issues encourage me to petition for shorter meets each day.


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 that a story is finished with development, tested successfully, and is able to be confidently handed over to the customer, manager, or whoever the story was for. It is vital that the entire team knows what the DoD is for every task so that they may test the story themselves, and catch issues early, to prevent a huge loss due to redone work and backtracking.

Summary:

In this section of the book, I read about the different processes of scrum, and how to perform them properly. These ranged from planning poker to sprints. There was detail about the purpose of these procedures and how to implement them, as well as their rules and regulations.

Nate 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 FBI had people plan every step of the Sentinal project which sounds like a good idea.  They used a Gantt chart to show how these steps will work.  This ends up failing every time though.  That is the problem that Sutherland has with this kind of planning.

  • 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?
  • Last year, we had a few things that were very helpful that didn't take much work.  The front triangles to get in the box got made in about ten minutes at competition.  Also, the wooden triangles were a very quick fix to the problem of crooked totes.  These small jobs greatly increased the value of our robot to make it able to compete at a higher level.

  • 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.
  • These systems are both getting at the need to focus on a small part of the problem.  This calls for a plan with preparation for issues.  This would be great to be implemented on out team because we would have a plan, and we could allocate some of the time for the task for possilble issues that may be unseen in the plan.

  • 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 could implement this to do two things: work on team functionality and learn to design and build pars of a robot.  With this we could be givin small tasks of things to build and we would be able to learn each time and learn better processes to build a robot.  Also, if we constantly switched up teams we would be able to learn to work with everyone on the team.

  • 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?
  • Sutherland brings up the point that improving a team has a giant advantage in productivity improvement over individual improvement.  This would be great in helping our team get things done.  This would allow us to build our robot in a shorter amount of time.  That may also boost morale as we would actually see our families in the winter.  The only problem may be that someone may not feel they get enough credit for the work they did and get frustrated for going unnoticed.

  • End with a summary of what you learned.
  • I learned many things in this reading.  I learned it is best to do short term planning and improve as a team over improving as individuals.  This would allow for our team to become more efficient and create a better robot in a shorter amount of time.  It also explained why attempting to plan out every last detail may be a poor decision as unforeseen problems can occur.

SC1 Ben

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?

I think that our triangles are an example of a quick job that was extremely helpful. We did spend some time thinking of manners in which to modify it, but they still took minimal time and effort to construct.The stop switches were also beneficial in not totally wrecking our chain and gears, and it didn't take much work to decide where to place them and how to wire/program them.

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?

It is important to get constant feedback on any advancements that are made. There is always the distinct chance that modifications must be made, or maybe there are too many modifications as is.

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.

All of these systems want you to look around and see what needs to be done, what constraints there are, what materials you have at hand. Then they want you to plan out your course of action and act on it. As you carry out your plan, make sure to watch for changes, so you can make adaptations as the situation necessitates. 

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 could divide the team into small groups, each tasked with building a paper airplane with 10 minutes. We test the airplanes, and let each team observe the others' planes. From there, people take notes on what they liked and disliked, and make modifications accordingly to their own design.

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.

An FRC team that is autonomous would agree on tasks needed to be done that day and know how to do these tasks on their own. They don't need constant interruption to be told how to do something or to be told to get on task; they stay on task and know what they're doing. Cross-functional teams can do multiple things. They build a robot that isn't restricted to only one function through the duration of demanding games, they know how to raise money and can get by without loans or outside help(not including donations), and they know how to involve their community. They get people interested in STEM and host summer shops and demos. Transcendence would be characterized by results. A transcendent team would win regionals and awards. They would go out of their way to help other teams, schools, and communities, resulting in awe-struck neighboring teams. 

Summary

I have learned about the creation of scrum, how it works, and its efficiency compared to the waterfall method. I learned what characteristics a team should have, how teams ought to go about planning tasks, and adapting to any changes along the way. Finally, I learned to appreciate the easy tasks that constitute grand results. 

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

I think that the cams and the triangles in the front of the robot added a lot of value due to the small amount of effort needed to complete such tasks and how it helped a lot.

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

This is necessary and important because without feedback improvements can't be made. That said, as a team we need to get input from the drive team as well as the other sub teams and work on solutions based off of the feedback.

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

These relate to how a team functions by explaining how a team should go about their business. The team should act on what things are changing around them and plan accordingly.

  • 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 could actually make paper airplanes in groups to see who's would go the furthest using specific resources and they can observe other teams doing things. The point would be to learn how to observe and make changes based off of your observations and to decide how to do things based off of those observations.

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

On an FRC team it would look like a bunch of people working together to make the best possible robot including mentors and students. Everyone would know what to do and would be able to complete that task without much help, but if they did need help they could check in with other teams and also check in with mentors.

Summary:

I learned that even the smallest things can be the most valuable and that there are many ways to go about solving a problem. Also, that we don't always have to use our own ideas, we can use other peoples ideas to solve a problem. We can also become autonomous as a team by simply helping each other and taking responsibility.

Friday, July 17, 2015

SC1 - Chad

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 "Sentinal" planning process seemed to be like many other large companies.  Each functional group created their requirements needed by other groups, estimated the amount of time required to complete their taks.  The Gantt chart linked each functional areas activities together to generate a complex interdependent plan.  Sutherland's issue with this planning method is that it is incorrect before the team even starts implementing the plan.  So all the work that was spent creating the interdependence could have been productively spent solving problems.  From my personal experience, the person providing inputs or creating the Gantt chart is also the best person to eliminate road blocks and provide leadership for the team.

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?

Stackholders need to be updated or the scum will begin to be more like the waterfall method with no feedback until the end. With frequent updates, changes can be identified early enough to make adjustments. In many cases, the stack holders also need to have confidence that the scrum method is yielding benefits. The stackholder meeting is the venue for this update.  By the way, a great stakeholders meeting could be lunch/dinner time presentations to the entire team.  Food and a show!


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.

These ideas all feed into continuous improvement strategy.  OODA is about figuring out what needs to be done and doing it, which is for sure a lean methodology.  Inspect and adapt and PDCA have continuous improvement embedded in the definition.

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?


To start with the point.  I think that learning the skills to observe and orient are very important.  The airplane is a good example because it also incorporates a loop and small tests.  Learning the technique could be as simple as duplicate the exact activity.  For an applicable robot activity, we need something that can easily be iterated so optimizing the program is the most obvious.  The activity could center around maneuvering the robot through and obstacle course, time or hitting the fewest obstacles could be the criteria.  Between iterations changes to gains and other quickly modified parameters can be changed. 

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.

Autonomous and cross-functional are the most probably team types for an FRC team.  The mentors enabling students to make their own decisions (experience is a great teacher), the students knowing when to engage the mentors for assistance and once the input has been taken in, the team should act.  This is basically the NPR example where the executives (mentors) couldn't be reached.  The team has a choice rise and get the job done or not get focused on problem solving.  For the FRC team this is operating in the small groups developing small tests and moving the robot design / build / programming forward.  Cross functionality with the cross training would improve efficiency as it would help level the surges in work.  As the special forces communications specialist can patch up a wounded comrade with the medics can't, a marketing or programmer could spin the cad model during the build season to free up the designers to solve a problem.  Or that marketing person could be well enough versed in the design to help create concepts for solving design problems.

End with a summary of what you learned.

Coming from a place that really values Gantt charts and has several people hired just to manage the Gantt chart, I am finding this book fascinating.  

Thinking back to my work for the last 12 months, it took this book to realize why my productivity improvements have stalled.  Basically it is the small cross functional team model.  During this time my marketing and business team mates have took other jobs or retired, leaving an imbalance of skills.  In addition, other projects have ballooned such that the teams I am on are very large.  I have the perfect project that is starting August 1 to try some of these new concepts on.  There are many items that lend themselves to small batches and there is customer interface software to be developed that could, give the correct support and early adopters lend itself to the lean start up and scrum principles.  Now to get some buy in!

Thursday, July 16, 2015

  • Intro: Last build season, we discussed an ideal strategy.  This strategy had a number of leap-of-faith assumptions about how long things would take and what we could do.  Try to describe our ideal strategy, including those assumed numbers that helped us calculate how many points we could earn in a round.
Our ideal strategy was to build large stacks at the feeder and score them, we figured we could score at least 40 points a game, if we were able to get the bottom tote to land flat.  We assumed these numbers based on roughly how long it would take to lift a tote using our protobot to test.

  • Intro: At what point in the build season did we find out how accurate our assumptions really were?  Was it possible to accelerate this?  Could the assumptions be broken down into small experiments?  If so, how?
I would say we found out about half way through the build season, this definitely could have been faster.  If we had built a full protobot on the first/second week we would have been able to realize many of the important design decisions that it took us a long time to find.  We could have broken some of the assumptions down which we did do, however I think in retrospect that we should have done these small experiments sooner, if we had built a protobot quickly we could have tested the extensions idea/center of gravity problem.


  • Intro: Explain the build-measure-learn feedback loop.  What is the purpose of this loop?  Why is it a loop?
In the bml (build measure learn) feedback loop, you start by building a minimum viable product, testing it, and seeing where you can improve it.  Then you are able to improve it and make a better build, test it, and find where you can improve, making a perpetual loop of improving your product.  The purpose is to be able to build better and  better product by learning what customers want/what does and doesn't work.  It's a loop because you can improve pretty much everything, and you can keep using this process to get a better and better product.


  • Going back to some of the leap-of-faith assumptions, what would some minimum viable products (MVPs) look like that could validate these assumptions?  What would we measure with the MVPs?  Think specific to last season's game.
A MVP in First most likely will look like a protobot, being able to test anything that isn't fact, whether its being able to straddle the scoring platform or if we will tip over if we try to drive straight onto it.  If we had built our protobot sooner we could have found many design changes that would improve our real bot and have fixed them.  We did that too an extent but I think we should have done this sooner as it takes a lot of the unknown out of design.


  • Explain the words "pivot" and "persevere" in the context of a team's way of doing things.
For us to pivot is to realize that a different design choice would be better than what we are currently doing and use that idea.  Persevering for us would be deciding although something is hard and there are other options we continue to push forward because it is for the best.

Wednesday, July 15, 2015

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

In our team's last year, some of the 20% jobs that brought an immense amount of value to the team include our cam iterations. These small pieces of metal allowed our bot to lift, hold, and release totes and bins, so there were instrumental to our entire strategy. Our work on the cams my not have been the most exhaustive of anything on the robot, but certainly brought a lot of value by making our entire strategy possible.

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

This is an important and necessary function to the Sentinel team because these stakeholders re going to be the product's primary users, and their input is extremely important for the project. In addition to this, the two weeks of development is long enough for tangible progress to be realistically made, as well as short enough to prevent a large amount of waste to possibly be produced. The development team can then collaborate with the users and improve the product based on their suggestions.


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 idea that both OODA and PDCA are trying to get at is that of the fabled agile development, where teams should take in their surroundings and situation, plan accordingly, and then act upon that plan and information. After you act, you should reflect upon your actions, to see how you can improve. This is very relatable to teams, as they should follow this process when developing a product.

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?

The paper airplane idea could be implemented at a team meeting in several ways, one of which would be having everyone divide into small groups, and work on a task such as CADing a model of a part, assembling a piece, or, as we've done in the past, build marshmallow-and-toothpick towers. The point of these exercises, aside from the ambiguous concept of 'team-building', would allow the entire team to become knowledgeable on a part or process, and for everyone to give input, which could lead to new ideas being brought to the table. 

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.

On an FRC team, being able to be transcendent, autonomous, and cross-functional is extremely valuable. An FRC team that meets all three of these criteria would be similar to that of the special forces team, where each member knows how to perform another's job, in the event they are unable to do so. This kind of cross-functionality on an FRC team would be  valuable asset, as team members could still program autonomous, design in CAD, or wire the electronics board even if the people who normally do these things are gone. An autonomous team would be able to know what needs to be accomplished on that day and how to accomplish it without a long meeting. Finally,  transcendent team would be able to fluidly move through all of the motions of design, construction, and testing without hitting any roadblocks that could have been prevented.

Summary:

In this first part of the book, I read about the origins of scrum, and just what scrum is, as well. I read about the ideal size of a team, and bout how much more efficient scrum is as compared to the waterfall method. I learned about the traits that are present in the ideal team, and bout the value of just 20% of work put into a product.