PM Forum Meeting #7 In The Books

A huge shout-out to Cole Basta of Dwyer Instruments for hosting our seventh Project Management Forum meeting on Thursday.  He provided a breakfast spread, provided branded notebooks, and did an outstanding overview of Dwyer and how the Manufacturing Engineering group has journeyed over the bast 5 years in using agile principles and techniques for new product development support.

We started the session with networking, which was great as we had four first time attendees, and one second time attendee.  Just as the juices were flowing, we started our educational component.

Time Management Techniques

Our educational components was based on prioritizing the activities we perform on a daily/weekly/monthly basis using the philosophy from Scale by Jeff Hoffman and David Finkel.  The focus was on A,B,C,D activities. based on applying the pareto principle four levels deep:

  • D Time is the 80 percent mass of unleveraged, even wasteful time that produces only 20 percent of your total return. Delete, delegate, defer, or design it out (4D’s)
  • C Time is the leveraged 20 percent of  your time that delivers 80 percent of your results. This is your “Leveraged Time.”
  • B Time is the highly focused 4 percent that produces 64 percent of your results. We call this the “4% sweet spot.”
  • A Time:  Magic 1 percent generates more than 50 percent of results!

After going through and exercise to identify and share our A,B,C,D activities, we moved into what an “Ideal” week would look like.  The key is to find your most productive part of the week and pre-schedule time to work on your A&B tasks.  As this becomes a habit, you will find yourself making progress toward your strategic goals.

Agile Considerations at Dwyer      (agilealliance.org, 2018)

Agile Development is an umbrella term for a set of methods and practices based on the values and principles expressed in the Agile Manifesto.

Solutions evolve through collaboration between self-organizing, cross-functional teams utilizing the appropriate practices for their context.

Methods primarily being used in Manufacturing Engineering at Dwyer are:

  • Scrum – Cadence of meetings for prioritizing and planning work items, working through impediments, demonstrating deliverables, and continuously improving the process.
  • XP – Pair Development – two or more people work together on the same work task sharing equipment.

Agile Values

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

12 Principles of Agile

1 – Our highest priority is to satisfy the customer through early and continuous delivery of valuable software product.

2 – Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

3 – Deliver working software product frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4 – Business people and product developers must work together daily throughout the project.

5 – Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

6 – The most efficient and effective method of conveying information to and within a product development team is face-to-face conversation.

7 – Working product is the primary measure of progress.

8 – Agile processes promote sustainable product development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

9 – Continuous attention to technical excellence and good design enhances agility.

10 – Simplicity–the art of maximizing the amount of work not done–is essential.

11 – The best architectures, requirements, and designs emerge from self-organizing teams.

12 – At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile Today in Manufacturing Engineering at Dwyer

Methodology

  • Scrum work management with Kanban project prioritization
  • 2 week “Sprints”

Team Makeup

  • Product Release / Test and Calibration Team (4.5 members)
  • Automation Team (4.5 members)
  • 1 each Product Owner and Scrum Master over both teams

Meetings

  • Stakeholder Prioritization Meeting (30 minutes)
  • Team Planning Meeting (1.5 to 2 hours)
  • Daily Team Standup Meeting (15 minute)
  • Look Ahead Project Scoping / Backlog Estimation Meetings (as needed)
  • Sprint Demo and Retrospective Meeting (1.5 – 3 hours)

Retrospectives

  • Worked Well, Challenges, Start Stop
  • Happiness Index

If you are interested in learning more about our Renaissance Executive Forums PM Forum, please contact me at PMCkenriches@gmail.com.

I have a 1 hour workshop, that includes two exercises, that I look forward to presenting at your organization to help your team be more productive and effective in their daily activities and in making progress on their strategic goals.  Reach out to me at PMCkenriches@gmail or visit PMCkenriches.com.

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s