1 / 20

Lean Concepts/ Project Management Techniques

Lean Concepts/ Project Management Techniques. My Flexible Pencil www.myflexiblepencil.com Twitter: @ FlexiblePencil. David M. Kasprzak. About me. Career spent in planning, monitoring & control of major programs, primarily for USG & DoD

lloyd
Download Presentation

Lean Concepts/ Project Management Techniques

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Lean Concepts/Project Management Techniques My Flexible Pencil www.myflexiblepencil.com Twitter: @FlexiblePencil David M. Kasprzak

  2. About me • Career spent in planning, monitoring & control of major programs, primarily for USG & DoD • DEA – $90M Worldwide IT infrastructure Deployment budget development & justification • CSC – Pricing for Major proposals ($100M+) • BAE, RTN, ESA – Program Planning & Control, SDLC - Hardware Engineering & Manufacturing Production • 2009 – Introduced to Lean via 8-week training class by Greater Boston Manufacturing Partnership • 2010 – Started My Flexible Pencil blog

  3. Thoughts on Measurement • We are inundated with data and measurements Inventory Turns Mean Time Between Failures Balance Sheets Use Cases Cash Flows Aged Receivables Failure Mode Effect Analysis Page Hits Unique Daily Visitors Net Present Value Full Time Equivalents Critical Path Analysis Estimate at Completion Earned Value Management Key Performance Indicators Return on Investment Conversion Costs Statistical Process Control • “That which can not be measured cannot be managed” • While this is true Quantification is not enough to understand how people work, how organizations work, and how people within organizations work. • Data and analytics are indicators that point to where problems lie, they are not determinants of where problems begin • True understanding of how a workplace performs necessitates a qualitative understanding of behavior

  4. So what is lean? • Lean is not • A manufacturing process • A quality system • A cost reduction methodology • An efficiency protocol • Lean is a philosophy of work • Shingo Model for Operational Excellence based on principles of: • Easier • Better • Faster • Cheaper • In that order & that order Only!

  5. Lean Fundamentals • Muda is most often discussed as the driving force behind Lean • Necessary waste • Just plain waste • Muda, however, is the result of 2 “forces” • Mura • Unevenness • Muri • Overburdening • The key to eliminating these negative forces, and replacing them with more positive habits, is understanding the entire system • Process • People

  6. Waste & Value • What is Value? • Any activity that changes the product/service in a way that is desired by the customers • Wastes: • Motion • Waiting • Defects • Inventory • Transportation • Overprocessing • Overproduction • Human Creativity

  7. Manufacturing vs. Project Environments • Shop floor: Parts and products move • The space within which parts move is physical and easy to see • The parts are tangible • Minimizing the materials, space and processes necessary to assemble parts and turn them into products reduces waste • Project teams: Information and data move • The space may be physical but is primarily virtual • Very little that is physical or tangible “moves” • Minimizing the materials, space and processes necessary to assemble and share bits of information and turn them into work products reduces waste

  8. Making Projects More Efficient • Some aspects of the shop floor apply directly to the project office: • Having team members sit in single location, rather than distributed • Aligning chairs, desks, printers, etc. to minimize unnecessary foot steps • Neat, clean, orderly work environment • This focus on the physical & tangible, however, is missing the point • Since information is what is moving, we need to think about how to move the information more efficiently, and not just the people who are processing it • An examination of common behaviors within white-collar, project environments, will reveal habits that prevent or inhibit the flow of information, leading to unevenness, overburden, and inefficiency

  9. Death by PowerPoint: Overprocessing • A Project Manager has a series of meetings with sub-teams once each week. She always has slides prepared for each meeting, takes diligent notes, and expects her team leaders to have slides done, too, so that they can communicate status and identify new actions that arise from the individual contributors on each of the sub-teams. Monthly, the PM summarizes these issues in a presentation for her management. • Where’s the value? • Overprocessing occurs when additional work is performed beyond that which is necessary to produce the products specified by the customer. Any situation where there are extra steps added to a process that don’t add any additional value generates Overprocessing waste.

  10. My Gantt is Killing Me: Waiting • A project manager has the opportunity to start several tasks early, however, he is forced to wait for his counterpart’s team to complete several preceding activities. Due to the waterfall development schedule, he is caught in a “push” system where he must wait for information to be passed to him, when the counterpart is able to provide it. The inability to “pull” information from his supplier when required means he must put his team on standby until the necessary inputs arrive. • Where’s the value? • If a manufacturing cell is dependent upon the machine shop to complete fabrication of parts, and those parts are late, the cell is sitting, idle, waiting for the input it needs to do its work. • In the project environment, the exact same thing often occurs when the predecessor activity does not finish, and the dependent activity is delayed. This leaves the resources assigned to the dependent activity stuck in the mud.

  11. Hooray! I finished Early!: Inventory • A project manager habitually pulls in tasks, completing them in less time than planned, and ahead of the project schedule. At times, this requires driving his team to work some overtime. Deliverables are often stored, either physically or electronically, until customers - both internal and external – can make use of them. • Where’s the value? • It is often seen as a good thing to work ahead and deliver early.  Unfortunately, doing so could create a situation where the inputs to downstream processes are stockpiled, or “completed” before other tasks.  This can have negative consequences for cash flow, resource availability or, in the worst case, the work products resulting from those early tasks are out of synch with later developments, requiring them to be re-worked.

  12. Spammed Beyond Belief: Transportation • A project manager keeps her team updated through regular emails, and shares information she receives as quickly as possible to keep the entire team aware of on-going developments as they happen. She also has shared workspaces set up through a combination of internal wikis and shared team folders to make sure everyone has access to information at any time. • Where’s the value? • This is no different than building up a bunch of widgets and then moving them around on trucks to random destinations, simply because we have a lot of trucks. One of the major advantages of IT is that vast amounts of data can be moved rapidly from place to place.   Unfortunately, with no regard for who needs specific information exactly when, the information is carried to unnecessary destinations. Simply because it’s moving doesn’t mean that it’s adding value.

  13. I know just what you need: Defects • A project manager diligently defines the activities and deliverables of his team, making sure that the technical expertise of the group is poured into their work. By defining the quality and specifications for their own work, they assure that everything they produce is done according to their own expertise. • Where’s the value? • If performance doesn’t meet the customer’s desires, you’ve got defects.  Defects result in rework and scrap. Since things always change while trying to execute a project, especially in development environments where the path to the goal is uncertain, acceptance criteria also change.  If one party in the exchange unilaterally determines what will be delivered, defects are inevitable.

  14. Meetings on top of Meetings: Motion • A project manager spends most of her day communicating with team members, sponsors and stakeholders throughout the organization. Meetings are scheduled throughout most of the day, and most team members are invited so that information can be shared to all members of the team at once. • Where’s the value? • Getting up from the desk and heading to a conference room to share communications is wasteful, especially if no one wants or needs the information. Most meetings are held due to poor communication practices. Instead of allowing information to flow freely to those who need it, it is batched and queued until it becomes necessary to call a meeting. A much better practice is to have regular, frequent and immediate interactions, vertically and horizontally, in order to share information, detect problems, identify solutions, and take action.

  15. Going above and beyond: Overproduction • A project manager, afraid that something on his project might be missed, generated extra documentation in support of his deliverables. Experience has taught him that you can never do too much. He has also learned to keep his team busy by adding extra features into the products, even if they were not asked for. • Where’s the value? • Project teams that consistently overproduce are often in an environment of fear and will generate reams of documentation to shield themselves from the wrath of senior managers, customers, or each other. • In more hospitable environments, overproduction comes about when team members simply have too much decision-making freedom and end up trying to go above and beyond customer specs. This can be a tricky situation. Customers love to get more than they were expecting, however, there is a big difference between adding extra value to the customer and wasting a project’s resources.

  16. DevelopingCountermeasures • Wasted Human Creativity • Also referred to as wasted talent or potential, the 8th waste is controversial in that it is not a part of the original 7 wastes declared in the Toyota Production System. • Many argue that wasted human creativity is just the outcome of the other 7 – if people are busy producing waste, they aren’t engaging their own ability to innovate. • Others see wasted creativity as the 8th waste, as the root cause of all the others. • Wasted potential doesn’t come from the inability to get over inefficient processes and engage the intellect, rather, inefficient processes occur when people are downtrodden and disrespected, and their intrinsic motivation to seek excellence is all but destroyed.

  17. Fostering Innovation • Overcoming this waste is as simple as the words of General George S. Patton: • “Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity.” • People understand the need to deliver and keep customers satisfied….even delighted! • If they are not focusing on the customer, it is likely that something is distracting them. That distraction may very well be the overwhelming burden of process guidelines that force their thinking into narrow, “acceptable” boxes.

  18. Unleash the Hounds! • The rules that determine how people are supposed to go about managing their tasks, or the project as a whole, tend to thwart attempts at experimentation and the resulting process improvement. • Tight guidelines on project teams bottle up the potential that their team members are capable of. • Over-arching project management guidelines are enforced to the letter of the law by senior managers and internal auditors, to the point that they suffocate project teams and drive out their natural desire to test & learn.

  19. Good Habits, Failing Fast & Intrinsic Motivation • The Power of Habit – Charles Duhigg • Cue, Response & Reward are psychological fundamentals • Understanding how we respond to stimuli necessary for changing behavior • Developing good habits leads to greater productivity & creativity • Developing Better Habits: • The Lean Startup – Eric Ries • Constantly testing ideas as part of an experiment allows you to “Pivot or Persevere” • Drive– Dan Pink • Motivation is intrinisc. You can not motivate people, you can only de-motivate them • Imagine – Jason Lehrer • It is necessary to struggle in order to achieve mental breaks with current expectations • Wait – Frank Portnoy • Delaying a decision as long as possible leads to better outcomes

  20. Keys to Improvement • Learn to Identify & Eliminate Waste • Experiment constantly • Fail Fast to Learn quickly • Embrace Emotional Intelligence • Practice constantly • Reinforce discipline • Easier-Better-Faster Cheaper, in that order, always!

More Related