Thomas Henson

  • Data Engineering Courses
    • Installing and Configuring Splunk
    • Implementing Neural Networks with TFLearn
    • Hortonworks Getting Started
    • Analyzing Machine Data with Splunk
    • Pig Latin Getting Started Course
    • HDFS Getting Started Course
    • Enterprise Skills in Hortonworks Data Platform
  • Pig Eval Series
  • About
  • Big Data Big Questions

4 Steps to Increasing Team Productivity by 400%

February 12, 2015 by Thomas Henson Leave a Comment

The idea of getting a team to increase performance by 400% sounds crazy but it’s exactly what is happening at software startups. It is no secret that the key ingredient is using agile project management. The real secret is that those same agile principles can be applied to any startup.

team-rowing
Photo by bplanet at freedigitalphotos.net

 

Myth: Agile is only for software

Agile management practices are being implemented in all kinds of businesses. Jeff Sutherland, a founding member of agile methodology and fighter pilot, in his recent book provides an example of a condo developer using agile principles to build high rise condos. If agile principles can work for the construction of high rise condos, with a little customization they will work in your company.

When switch to an agile project management can increase your team’s productivity by 400% why are you not using it today? Maybe you have thought agile can’t work in your organization. Begin implementing these 4 steps today to jump start your team’s productivity.

  1.  Laser Like Focus – In Agile development, teams go through what is called a sprint, this is a period of 1-2 weeks where the team only works on specific tasks. These tasks are agreed upon before the sprint starts by both the team and leadership. During a sprint the team only works on tasks that will help them accomplish the goals of the sprint. By eliminating distractions the company is allowing the team to accomplish the goals of the sprint. Try it out today by instituting a no meeting day or no emails before lunch. This will give your team a distraction free time to focus on accomplishing the single most important task.
  2.  Continuous improvement – Agile teams believe in continuous improvement. One way they accomplish this is by having a meeting at the end of each sprint called a retrospective. In a retrospective the teams talks about what worked well and what did not. This meeting is a judgment free zone with the single goal of helping the team perform more efficiently. Try it out today by having meetings at the end of each week. In this meeting you act as the facilitator and allow the team to give feedback about what is working and what is not. At the end of the meeting let the team decide on the most important item. Once your team has decided on an improvement to make, set a metric to track that improvement and follow up next week.
  3. Constant Customer feedback – Agile teams take customer feedback to a new level. At the end of each sprint agile teams show what they have accomplished to the customers. So every 1-2 weeks customers are getting a prototype to play with and give immediate feedback to the developers. Try it out today by bring your customers into your own design process. Give customer early access to the project you are working on and soak in all the feedback they give you. The earlier you get feedback from your customers the less costly it is to change down the road.
  4. Information Radiator – In agile project management information about the project is placed in a common area on a whiteboard with 100’s of post-its/notecards detailing everything about the project. This board is commonly referred to as the information radiator. Anyone is allowed to look at the board because this ensures the entire company is on the same page, from accounting to the sales staff. Try it out today by setting up a whiteboard in an area where everyone will see. Write down the entire task for your project. On the white board create 3 columns with the following headers TODO, WORK IN PROGRESS, and DONE. Now place all the task in the TODO column, as the task are being worked on move them into the WORK IN PROGRESS column and then finally move them to DONE when the task is complete.
climbing mtn together
Photo by ratch0013 at freedigitalphotos.net

 

Use these steps today

Don’t let the name Agile scare you into thinking the agile principles can’t be implemented in your company just because you don’t develop software. Embrace the 4 principles in your company today and experience the increase in productivity the software industry has for the last 10 years.

Filed Under: Agile Tagged With: Agile, Management, Project Management

How to become a Certified ScrumMaster

November 24, 2014 by Thomas Henson 2 Comments

For the past couple of years I have been working on Scrum or scrum like development projects. In both my Bachelors and Masters programs we studied Scrum, so I thought I knew how the Scrum development worked. Wow was I wrong. During the past year I have worked with a team of developers who taught me the error of my ways. Since I realized my Scrumifation (copyright pending) was off a little bit I decided to get certified.

SplitShire_IMG_4354

So where can you get certified?

At first I didn’t know where to start since there are a couple of organizations that offer Scrum Certification. After a lot of research I decided to go with the Scrum Alliance and get the Certified Scrum Master certification. The certification is 1 of 6 possible certified by the Scrum Alliance , which is the most widely accepted scrum certifying body. The Scrum Alliance has the following certifications:

  1. Certified Scrum Developer
  2. Certified ScrumMaster
  3. Certified Product Owner
  4. Certified Scrum Professional
  5. Certified Scrum Coach
  6. Certified Scrum Trainer

It was an easy choice for me when selecting a specific Scrum certification. I like communicating and helping others so a ScrumMaster would interest and it fit into my overall career path and interests.

How to get a Scrum Master Certification

Scrum Alliance requires 2 steps to become a Certified ScrumMaster:

Attend Certified Training Course

The Scrum Alliance website had a find your class resource to aid in finding a class close to your location. I went to a session held by BrainTrust Consulting in Nashville. This class was an intense 2 day session taking me through the Scrum process from a ScrumMaster’s role. ScrumMaster training is two days of intesnse learning but it is a lot of fun as well.Day 1 starts on a team of 5-6 people and you are given a project to complete before the end of day 2. The time working on the project is broken up by learning about Scrum  then applying those steps on the project your team is working on. The class was really laid back and encouraged students to challenge the trainer to highlight areas where this wouldn’t work in the real world. As the class was ending on the second day I really found myself excited to get back to work and apply the lessons learned into our current project.

Take and Pass Exam

After attending the class you will be able to sit for the exam within 7 days of finishing the class. The test is 35 questions and you need only get 24 correct. I can’t tell you what is on the test but I can say with an awesome trainer you should be able to pass it easily. Checkout my trainer at BrainTrust. No time limit is placed on the test, but you do have to finish it in one session. The test took me under an hour. Also you want to take the exam while the content from the class is fresh.

Overall getting certified in Scrum was an easy process, but I had a good bit of experience and education before jumping into the certification. While no experience is necessary for going through the training it did seem to help me. The CSM certification helped me bring more value back to my team the first day after attending training.

Filed Under: Agile Tagged With: Agile, CSM, Project Management, Scrum Master

How to Build the case for Scrum in your Organization

November 14, 2014 by Thomas Henson Leave a Comment

So you’ve read all the great stories about how scrum can help your team produce better results. Most of your colleagues  at other companies are using Scrum and thriving because of it. Now all you have to do is sell it to your boss. You believe management won’t buy in, so what should you do? What if you could build the case for Scrum in your organization. Startup Stock Photos
Before beginning to build the case for Scrum in your organization you need to ensure your team is on-board first.. Even if management signs off on your proposal it’s not going to work unless your team is on-board. Chances are your team will be excited because, Scrum is a team first framework  based on the idea that teams are self-organizing.

So how do you build the case for Scrum in your organization?

  1. Start sending subtle hints to key decision makers in your organization – Find articles or case studies and pass them around to those decision makers. Send an email out as a by the way checkout this article. Try leaving a copy sitting in the break room or by the coffee pot. If you really want bonus points find articles that quantify how much money the company has saved or increased revenue by using Scrum. The goal here is to get the information out about Scrum.
  2. Point out missed opportunities with your current system – Try to constructively point out opportunities your team could capitalize on under a different project management methodology. For example is there a process you could update to make your team more productive. How about problems with your last project that could have been caught earlier with a more iterative process? Do your stakeholders have a voice throughout development? The goal is to pointing out the pain points of your current process.
  3. Look for ambassadors in your company – Talk with coworkers to find others in your organizations that are sympathetic to your cause. In a large organization you may find teams that are already using Scrum. Maybe some of your team members have used it with previous employers. You might even find other project leads who have wanted to take on Scrum for their teams as well. The goal is to build a collation.
  4. Build the slides – Even though you have built your case it’s still important to reiterate the points in your meeting with management.  First show the opportunities where your team could have benefited from using Scrum versus your current methodology. Next pick a use case of Scrum turning around an organization and lead with it. Third give an executive overview of the Scrum Framework. Be open and honest about what Scrum is and is not, leadership needs to have a realistic view of Scrum. Do not over sell Scrum as if it will solve world peace. Highlight any of your competitors that are using Scrum and how they beating you with it. End with a slide about the proposed roll-out of Scrum and how it will affect the current work in progress. The goal is to create a compelling slide deck.
  5. Have the conversation – Schedule a formal meeting with the decisions makers.  Invite any of your ambassadors to this meeting but be careful about bringing the team. You want to ensure leadership has an opportunity to discuss it, without feeling ambushed. If you have successfully built the case, leadership should not feel ambushed. Many organizations are slow to make decision or will need a few more meeting like this to get change to occur in the organization.

whiteboard

Building the case for Scrum is not guaranteed to work in all cases. But laying out your case in a professional fashion will give your a higher chance for success. Some organization are not ready to make the leap to Scrum but having the Scrum conversation in a professional way will help your organisation move toward Scrum. Remember for Scrum to work in your organization you will need leadership to buy in.

Filed Under: Agile Tagged With: Agile, Project Management, Scrum

Subscribe to Newsletter

Archives

  • February 2021 (2)
  • January 2021 (5)
  • May 2020 (1)
  • January 2020 (1)
  • November 2019 (1)
  • October 2019 (9)
  • July 2019 (7)
  • June 2019 (8)
  • May 2019 (4)
  • April 2019 (1)
  • February 2019 (1)
  • January 2019 (2)
  • September 2018 (1)
  • August 2018 (1)
  • July 2018 (3)
  • June 2018 (6)
  • May 2018 (5)
  • April 2018 (2)
  • March 2018 (1)
  • February 2018 (4)
  • January 2018 (6)
  • December 2017 (5)
  • November 2017 (5)
  • October 2017 (3)
  • September 2017 (6)
  • August 2017 (2)
  • July 2017 (6)
  • June 2017 (5)
  • May 2017 (6)
  • April 2017 (1)
  • March 2017 (2)
  • February 2017 (1)
  • January 2017 (1)
  • December 2016 (6)
  • November 2016 (6)
  • October 2016 (1)
  • September 2016 (1)
  • August 2016 (1)
  • July 2016 (1)
  • June 2016 (2)
  • March 2016 (1)
  • February 2016 (1)
  • January 2016 (1)
  • December 2015 (1)
  • November 2015 (1)
  • September 2015 (1)
  • August 2015 (1)
  • July 2015 (2)
  • June 2015 (1)
  • May 2015 (4)
  • April 2015 (2)
  • March 2015 (1)
  • February 2015 (5)
  • January 2015 (7)
  • December 2014 (3)
  • November 2014 (4)
  • October 2014 (1)
  • May 2014 (1)
  • March 2014 (3)
  • February 2014 (3)
  • January 2014 (1)
  • September 2013 (3)
  • October 2012 (1)
  • August 2012 (2)
  • May 2012 (1)
  • April 2012 (1)
  • February 2012 (2)
  • December 2011 (1)
  • September 2011 (2)

Tags

Agile AI Apache Pig Apache Pig Latin Apache Pig Tutorial ASP.NET AWS Big Data Big Data Big Questions Book Review Books Data Analytics Data Engineer Data Engineers Data Science Deep Learning DynamoDB Hadoop Hadoop Distributed File System Hadoop Pig HBase HDFS IoT Isilon Isilon Quick Tips Learn Hadoop Machine Learning Machine Learning Engineer Management Motivation MVC NoSQL OneFS Pig Latin Pluralsight Project Management Python Quick Tip quick tips Scrum Splunk Streaming Analytics Tensorflow Tutorial Unstructured Data

Follow me on Twitter

My Tweets

Recent Posts

  • Tips & Tricks for Studying Machine Learning Projects
  • Getting Started as Big Data Product Marketing Manager
  • What is a Chief Data Officer?
  • What is an Industrial IoT Engineer with Derek Morgan
  • Ultimate List of Tensorflow Resources for Machine Learning Engineers

Copyright © 2023 · eleven40 Pro Theme on Genesis Framework · WordPress · Log in

 

Loading Comments...