Eden of Things – Day 2

Standard

Making good progress

First task of the day was swapping out the Raspberry Pis from the sensors team and replacing them with x86 based machines. The compiler for the ESP8266 is x86 based and there is no Arm-based version that we could find, we could have rebuilt it, but it was more effort than pulling apart my office and bringing in my home computer and a spare that was being built as a Pi-Net server.

So we didn’t quite fit everything we wanted to into day 1.  It was really important that the teams had a chance to play with the technology and try a bit of coding, that meant we dropped on session on understanding source control using Git.  What better way to start a Tuesday than with a deep dive into source control, commits, merges, branches and detached heads. That is once we got started, we were slightly late today, as day 2 on the job and some of the teams rocked up late.

Once everybody was completely lost with git terminology, me included, the teams got into their respective tasks under the guidance of their mentors, Byran on Sensors, Ben on Core Systems and Paul on User Interface.  The teams had a steep learning curve, with most members having never experienced C, arduino, ESP8266, php, javascript, jquery, REST, etc, etc.  The mentors have been amazing, patiently leading and training the teams in everything from configuring a linux webserver, to building breadboard circuits and initialising SMART TVs. One problem I’ve experienced with teams is our culture doesn’t encourage enough celebration or recognition of achievement.  The teams here were no different.

One problem I’ve experienced with teams is our culture doesn’t encourage enough celebration or recognition of achievement.  The teams here were no different. As the teams started on their quests to master their allocate sub-system, little victories were silently occurring all the time, but you couldn’t tell.  The UI team had a little shout when then got the Smart TV to connect to their web server and display a page, but the sensor team managed to get an LED to flash on and off via the ESP8266 and there was nothing, not a whisper. This little victories are so important to celebrate, they enable the whole team to realise that we are making progress, they add an element of fun to proceedings and they make us feel good and bond as teams.  So with a little encouragement and praise we are making progress, there are more cheers happening all the time, we are starting to generate a buzz.

After a intense day of work we had our first show and tell at 3pm.  The UI team kicked off the presentations with a great looking screen with imagery they had created earlier in the day from around the biomes and some dummy data.  Finally, a round of applause and laughter, we’re making real progress, technically and socially.

20160216_130354_Richtone(HDR)

The Core systems team followed up with a visual less impressive but fantastic technical achievement demonstrating a working php based REST server and an agreement API architecture – no small feat.  More applause.

20160216_130410_Richtone(HDR)

Finally, the sensor team keep up the run of success, having moved on from the impressive display of a flashing LED, they showed how they had deployed a websever onto the ESP8266, connected to our sometimes flakey wifi and were able to get a reading from a light sensor on demand with a simple REST call. More applause and cheering!

20160216_130323_Richtone(HDR)

All teams have proven the fundamentals of the system architecture, now to pull it together.

A review meeting decide the next steps, now we know that all the basic concept could work, was to look into the realities of the physical environment we want to deploy into.  Is there a wifi signal, how strong is it, where should we place the sensors.  We don’t want to continue developing new features until we can prove that we have a working architecture from end-to-end – a walking skeleton.

And that was pretty much it for day 2, everybody disappeared into the biomes, smart phones out measuring wifi signals and seeing how high up into the biomes that could get. The good news is they found wifi, whether it’s strong enough for the ESP8266 we’re not sure, we’ll find out tomorrow……..

Oh, and git, we’ve had some commits! https://github.com/TheEdenOfThings

Great work everybody!!!!

Advertisements

Eden of Things – Day 1

Standard

After 6 months of planning (honest there has been some planning), the first day of the Eden Of Things has arrived!

The Eden Project’s horticultural technologist, Michael Cutler, provided an idea based on measuring various aspects of the Eden Biomes with the aim of providing visitors with a different perspective on the Biomes lifecycle.

The Big Plan

Software Cornwall and Cornwall College are colloborating to provide a pilot solution for the Eden Project and work experience for students studying a computing degree.  We’ve setup a base room on site and will be here for 1 week creating a solution.

The solution comprises of three components:

  • a number of sensor stations that are free standing (no wires) based around an ESP8266.
  • a data collection and cataloguing server
  • a data presentation system able to consume the data from the data collection server and display it in interesting ways on a smart TV.

Day 1

The first day is all about induction, admin, team building and understanding the customers goals and context for the tasks. Not to mention getting all the base tech in place to enable the week to happen.

It takes a surprising amount of equipment to run the week, about an S-MAX full.  Luckily, although the Core building at the Eden Project is at the bottom of the site, we could get right to the door.

With a few last minute withdraws we ended up with 13 ready to start at 9.30am.  The day starts with the obligatory introductions and health and safety, then we get into the fun stuff.  Scrum tennis gets everybody talking and interacting.  It’s a great game, everytime I run it different things happen. What happened this time:

  • Individuals became a team.  They talked, interacted, focused on a problem.
  • We learnt that failure is OK.  The team tried different approaches don’t always work, but don’t discount ideas, give it a go, but be sure to limit it, control the risk by monitoring and discussing after a defined trial period – a sprint!
  • When we try something new, it should be expected that we will fail first time.  Round zero, the number of points produced was zero. Acting as a team, not allocating blame, but inspecting and adapting the process is key.
  • Look for the bottlenecks, externally motivation doesn’t make the machine work faster.  No amount of encouragement or pressure can make the team work faster.  We need to look at what is slowing us up and work out how to remove or reduce it’s effect.  In scrum tennis we moved closer together, formed a circle, etc.
  • Don’t be bullied into accepting unrealistic targets.  Calling them aspirational or anything else doesn’t make them achievable.  The team need to agree and set it’s targets based upon experience and knowledge of the task.  When pushed, don’t just accept a bigger target to please the customer, be realistic and set expectations at the beginning.

What a great list, learnt through experience, no amount of lecturing could have got these messages home with the effectiveness of this simple game.

Next up, after team allocations and setting up workstations, was a session on how to code.  The key messages were focus on testing, strive to do TTD and work as a team, use mob and pair programming.  The session was based upon the excellent http://cyber-dojo.org, testing Bluefruit’s Head of Development, Byran, by using php rather than his preference of c++.

With all the induction training done, the team earned the much coveted Software Cornwall polo shirt!  A spot of lunch and then a customer brief from Edens Horticultural Technologist, Michael Cutler.

20160215_132849

The facts about what we – humans – are doing to our planet are stark, we’re all in this together and need to work together to look after our fragile planet and ensure it remains hospitable for our species.  This project’s real aim is to help with education, demonstrate the fragility and effect of variations upon the eco-system in the Biomes; ultimately to contribute to helping change visitors behaviour and make them more aware of they’re actions and choices and the effect this has upon our planet.  It’s a grand aim, but the team is looking forward to the challenge of using technology for good and seeing what insights can be gleaned and how we can help with the Eden Projects mission.

And they’re off!  The thinking and coding begins. Most of the day has already based, so there is only an hour or two left for getting the ground work done, links to GitHub established and user stories reviewed and plans produced.

Just enough time and the end of the day for our first retrospective.  The 4 L’s approach was taken to complete a 10 min retrospective.  Key findings:

  • We liked getting to code
  • We liked creating the team
  • We learnt about linux
  • We learnt about Raspberry Pis, Smart TVs and breadboard
  • We lacked tea and coffee
  • We lacked knowledge of PHP, linux
  • We longed for Raspberry Pis to be able to deploy code to the ESP-01
  • We longed for a tour of Eden

Some bits to fix for day two for the mentor and support team! Tea and coffee being number 1.

It was a great first day, many challenges cropped up, nearly all technical, but with a great mentoring team we managed to get everybody going.

 

Power vs Authority

Standard

Extracted from US Navy Publication – 14144 http://navyadvancement.tpub.com/14144/

AUTHORITY AND POWER

With authority comes power. Power is theability to influence people toward organizationalobjectives. However, you have limits on yourauthority and power. View your authority andpower as a funnel, broad at the top and narrowat the bottom. Always assume you have enoughauthority and power to meet your obligations, butdo not exceed that limit.

Authority Authority  only  exists  when  subordinatesaccept the idea that the supervisor has authorityover them. Subordinates can fail to recognizeauthority through disobedience, denial, or workdelays.  Subordinates  usually  accept  authorityreadily; however, abusing your authority as asupervisor can make you ineffective.Although most authority in the Navy resultsfrom a member’s rank or position in the chainof command, many types of authority exist. Mostauthority in the Navy is delegated.

LINE AUTHORITY. —Line authority is theauthority you have over subordinates in yourchain of command. This type of authoritycorresponds directly to your place within the chainof command and does not exist outside the chainof command. 

STAFF AUTHORITY. —Staff authority isthe right of staff to counsel, advise, or makerecommendations to line personnel. This type ofauthority does not give staff the right to give linepersonnel orders that affect the mission of the lineorganization.  A chief from another work center or divisioncould, by virtue of his or her rank, exercise staffauthority over a person in your work center ordivision by counseling or advising him or her toget a haircut. Failure to follow the advice orcounsel may result in non judicial punishment(NJP) for the subordinate. The other chief wouldnot, however, have the authority to enter yourwork center or division and make changes thatonly you and your superiors have the authorityto make. 

FUNCTIONAL AUTHORITY. —Certain stafforganizations are granted functional authority todirect line units within the area of the staff’sspecialty. Examples of staff organizations withfunctional authority include the Legal, EqualOpportunity, and Safety Departments.

Power In conjunction with your authority, you usepower to influence others toward the accomplishment of command goals. You can use power forpersonal gain or for the good of the organization.However, if your subordinates believe you usepower for personal gain, you will soon suffer anerosion of that power. On the other hand, ifsubordinates believe you use power to accomplishthe organizational goals, your power to influencethem will become stronger. Your power will alsobecome stronger when you share it throughdelegation of authority.Of the six types of power—reward, coercive,legitimate, informational, referent, and expert—you may use one or more in various combinations.Each situation will determine the one or ones youuse.

REWARD POWER. —Reward power stemsfrom your use of positive and negative rewardsto influence subordinates. Positive rewards rangefrom a smile or kind word to recommendationsfor awards. Negative rewards range from corrective-type counseling to placing a person on report.You will find one of the best ways to influenceyour subordinates is through the use of yourreward power. As a chief, you are responsible forstarting the positive reward process. First, writea recommendation for the award. Once there commendation  is  typed  in  the  command’sstandard award letter format, forward it up thechain of command for approval. Your job doesnot end here. Always follow-up on the recommendation, using your influence and persuasion to getthe award to the proper command level.Frequent use of positive rewards will amplifythe effect of a negative reward. Give positiverewards freely, but use restraint in giving negativerewards. If you use negative rewards frequently,subordinates  will  begin  to  expect  a  negativereward. Their expectation of a negative rewardwill lessen your power.

COERCIVE  POWER.  —Coercive power results from the expectation of a negative reward if  your  wishes  are  not  obeyed.  For  example, suppose you have counseled a subordinate twice for minor infractions of regulations. At the third counseling session, you threaten the subordinate with NJP. At the next occurrence of the un-desirable behavior, you place the subordinate on report. Coercive power works, but is not the preferred method of leading subordinates. It works best if used when all else fails and you feel sure you can carry through with a threat. Before giving a threat, you should have some insight as to how the CO will handle the case. You do not want to recommend maximum punishment only to have the CO dismiss the case at mast.

LEGITIMATE POWER. —Legitimate power comes  from  the  authority  of  your  rate  and position in the chain of command. You use this power in day-to-day business. Although legitimate power increases with added responsibilities, you can decrease that power if you fail to meet all of your responsibilities.  To increase your legitimate power, assume some of the division officer’s responsibilities. At first, the division officer will be glad to have the help. In time, the division officer will view the responsibilities as yours and formally delegate additional authority to you. That would increase your legitimate power without diminishing the power of the division officer.  Just as you can increase your legitimate power by assuming more responsibility, you can decrease that power by losing responsibility. For example, if you permit the division officer to assume some of your responsibilities, the division officer will eventually begin to view your responsibilities as his or hers. You will then have less legitimate power. However, when a subordinate wishes to assume some of your responsibilities, formally delegate those responsibilities to the subordinate.  That makes the subordinate accountable to you.  You then increase the subordinate’s power while retaining your power.

INFORMATIONAL POWER. —Informational power depends on your giving or withholding of information or having knowledge that others do not have. Use informational power when giving orders to subordinates. Give orders in such a manner that your subordinates presume the order originated at your level. When forced to comply with orders you do not agree with, don’t introduce the order by saying    “The  division  officer said.  .  .”   Phrase and present the order in a manner that leaves no doubt you initiated it.  Rely on your own resources to stay fully informed instead of depending on others. Subordinates may present unreliable information in a manner that makes it appear to be true. Superiors may become so involved with projects they forget to keep you informed of tasks being assigned or upcoming inspections. Information is power. Stay informed!

REFERENT POWER.  —Referent  power derives from your subordinates’ identification or association with you. You have this power by simply being “the chief.” People identify with the ideals you stand for. The chief has a pre-established image. You can enhance that image by exhibiting charisma, courage, and charm. An improved image increases your referent power. Always be aware of how others will perceive your actions. A negative image in the eyes of others will lessen your power and render you ineffective. Maintain a positive image!

EXPERT POWER. —Expert power comes from your knowledge in a specific area through which you influence others. You have expert power because your subordinates regard you as an expert in your rating. Subordinates may also have  this  type  of  power.  When  you  combine expert power with other types of power, you will find it an effective tool in influencing others. However, when you use it by itself, you will find it ineffective.