LSSC10 was a great conference.
InfoQ filmed many presentations.
I’m waiting for mine to be released. Meanwhile, check out Mary Poppendieck.
What is this about? Lean of course.
Posted by Christophe on June 3, 2010
LSSC10 was a great conference.
InfoQ filmed many presentations.
I’m waiting for mine to be released. Meanwhile, check out Mary Poppendieck.
What is this about? Lean of course.
Posted in LSSC10 | Tagged: Lean, lssc10, Mary Poppendieck | Leave a Comment »
Posted by Christophe on January 23, 2010
Attend this webcast and learn how the widespread adoption of agile software development is a double-edged sword. On the one hand, agile teams have reported impressive gains in productivity. On the other hand, these gains seem to plateau after a while, leaving a disquieting suspicion that something might be missing. This webinar will cover a few things that might be missing. It will help you look at your software development process and find leverage points for sustained improvement.
The webinar will look at:
Don’t miss the opportunity to hear this FREE live presentation by Mary Poppendieck. A popular writer and speaker, Mary continues to bring fresh perspectives to the world of software development.
There is no cost to attend, but you must register here
DATE: 3 February 2010
TIME: 2:00pm EST/11:00am PST
DURATION: One hour
Posted in Event, Lean, Mary Poppendieck | Tagged: IEEE, Lean, Mary Poppendieck, webinar | 1 Comment »
Posted by Christophe on December 11, 2009
Following her new book, in this video taken at UK Lean Conference 2009, Mary Poppendieck challenges the concept of plans; and demonstrates the need to replace them with decoupled experienced cross functional teams highly aware of constraints; and the the kind of leadership it takes to get the most of a system by focusing on flow rather than utilization.
Posted in Lean, Videos | Tagged: failure, Lean, Mary Poppendieck, planning, Video | 2 Comments »
Posted by Christophe on October 30, 2009
Mary and Tom Poppendieck third book just came out!
As the usage of lean in software development matures, expect specific and actionable ideas.
If you can’t wait to get the book, just buy it now.
If you have any ounce of patience, you can read the table of content, and the book sysnopsis.
Leading Lean Software Development: Results Are not the Point
Building on their breakthrough bestsellers Lean Software Development and Implementing Lean Software Development, Mary and Tom Poppendieck’s latest book shows software leaders and team members exactly how to drive high-value change throughout a software organization—and make it stick. They go far beyond generic implementation guidelines, demonstrating exactly how to make lean work in real projects, environments, and companies.
The Poppendiecks organize this book around the crucial concept of frames, the unspoken mental constructs that shape our perspectives and control our behavior in ways we rarely notice. For software leaders and team members, some frames lead to long-term failure, while others offer a strong foundation for success. Drawing on decades of experience, the authors present twenty-four frames that offer a coherent, complete framework for leading lean software development. You’ll discover powerful new ways to act as competency leader, product champion, improvement mentor, front-line leader, and even visionary.
Posted in Books, Lean, Mary Poppendieck | Tagged: book, Leadership, Lean, Mary Poppendieck | 2 Comments »
Posted by Christophe on June 21, 2008
When you look around, there are a lot of leaders recommended for software development. We have the functional manager and the project manager, the scrum master and the black belt, the product owner and the customer-on-site, the technical leader and the architect, the product manager and the chief engineer.
Clearly that’s too many leaders. So how many leaders should there be, what should they do, what shouldn’t they do, and what skills do they need?
This is a presentation and discussion Mary Poppendieck of leadership roles in software development — what works, what doesn’t and why.
Posted in Leadership, Lean, Mary Poppendieck, Videos | Tagged: Leadership, Lean, Mary Poppendieck, Videos | Leave a Comment »
Posted by Christophe on February 2, 2008
I attended to the Agile Bazaar event on January 31 2008 at the Worcester Polytechnic Institute where Mary Poppendieck presented “Appraisals and Compensation: The Elephant in the Room“. She will likely do presentation it again at the Agile 2008 conference in toronto. Not to spoil it, I will only give the thread line.
Mary went through a brief history of performance appraisals. While it all started 2,000 years ago in china, appraisals became universal (in the US) in the 90s.
So if every companies uses them, they must be extremely useful, right? Unfortunately not.
Mary exposed 8 underlying purposes supporting the mechanism (to name a few: motivatation of employees, identification of candidates for promotion, identification of training needs) and 6 faulty assumptions (including motivation as an external factor, focusing on the individual -or team- rather than the system and the delay of mainly negative feedback) .
Mary says that there is no valid research showing benefits of performance appraisals. Simply said, “it doesn’t work“. Her biggest complain is that appraisals target individuals (sometimes teams) rather the system itself. She also condemns judgment rather than feedback (system dynamic).
Mary went over the false assumptions behind individual pay-for-performance (money, motivation, individual assessment), and the negative effects they have on the system.
She finished by a case study done by HP across 13 organizations over a year 4 year period where each division implemented a different type of incentive plan. The results are just mind boggling. They all failed and got canceled.
So what is she proposing to do instead?
Provide every day for
The key here is that yearly of bi-annual appraisals are replaced by a daily engagement of management with the team. Promotions and salary adjustment are evaluated (team wide) on a regular basis – rather than once per year.
Mary closed saying that focus on training, delegation of the decision making process within an egalitarian culture, good pay and reciprocal commitment between the employees and the company are the pillars for high performance.
She also discussed a case study made around a large experiment done by HP. Wanna hear the punch line? Come by agile 08…
Now, if your organization is still mandating appraisal, check out Jeff Sutherland’s review process.
Posted in Agile Bazaar, Dilbert, Mary Poppendieck, Team Performance | Tagged: Agile Bazaar, Dilbert, Mary Poppendieck, Team Performance | 5 Comments »
Posted by Christophe on January 22, 2008
Performance reviews and compensation questions are frequently on the front seat. It is possibly one of the most deeply rooted problem to get rid of when working with agile teams.
According to Jeff Sutherland, “surveys show that 90% of companies report ratings don’t work but they still keep doing them. It is kind of like the waterfall process. In the face of overwhelming failure people keep repeating the mistake.“
Mary Poppendieck summarized this yesterday:
“Using money as a motivator is like playing with dynamite because money is a VERY effective motivator. Monetary rewards motivate people to do EXACTLY what is being rewarded – not necessarily what the organization intended to reward, but EXACTLY what is being measured to generate the reward. Therefore monetary motivators have a long track record of generating unintended consequences. If there is any apparent competition for the money, money motivates people to get as much as they can for themselves. Thus monetary motivators have a track record of suppressing collaboration. Finally, bonuses for performance rapidly come to be an expected part of the landscape, replacing passion and dedication as motivators . These are things you probably cannot change about using money as a motivator. “
A great book on the subject: Abolishing Performance Appraisals: Why They Backfire and What to Do Instead
So I asked Jeff what he is doing when you have to do performance ratings. He said that “you must take into consideration why they do not work in general and use a collaborative style to avoid the pitfalls.“
Jeff wrote a memo in 1996 on how to conduct such reviews. After contemplating many options, I think his review process is best (if you have to do one).
I kindly clarified some sections to pass the approval of our employment lawyers. Please check Jeff’s original post for reference.
Review Process for Agile Team Employees
Objective
The Review Process
The employee’s focus is to please the customer and meet their manager’s expectations in fulfilling their job responsibilities. This review process is forged as a collaborative rating system (360 degree feedback) and creates an accurate and realistic scoring without rating inflation by focusing attention on the user’s experience of the project or product being developed, along with time to deliver or market. The subjective experience of the manager is deemphasized. It requires raters to all work closely with one another to check ratings.
The Process Takes Three Meetings to Initialize
Meeting 1
Manager meets with employee and goes over the document. The employee is then asked to write his own individual review after the meeting by responding to the key individual performance questions (see below) and rate him/herself. The employee should be specific and concise and cite specific examples where appropriate. This review is designed to minimize the amount of writing that is general or vague.
Meeting 2
The second meeting occurs when the employee returns the review (along with soft copy). The manager discusses the employee’s perceptions to get a good understanding of them. After the meeting the manager carefully edits the review to incorporate his/her, the product team, senior management and customers’ perception of performance.
To gather the individual performance from the team, the manager sends a rating request using the rating scale below.
The employee’s 360 feedback will be a rating score based on the following percentages:
Meeting 3
The third meeting occurs after the manager has finished editing the review and the ratings. The updated document is discussed with the employee. Any differences in perceptions is discussed and noted accordingly. If there are disagreements regarding assessments, the employee will have an opportunity to give feedback. If there are any changes in the assessments they will be incorporated into the final review and signed off by the employee and Supervisor. The employee’s signature does not imply agreement but acknowledges receipt.
Team Performance
Performance Objectives will be determined by senior management and will be appropriate to the Team. The score will be based on the rating score below.
Team Rating of Individual’s Performance
Each selected individual will be asked to give an assessment of the employee’s work performance based on the rating scored listed below. The score is calculated as an average.
Manager’s Assessment of Performance
The manager rates the employee on a set of questions that drives the review process away from a standard list of items accomplished. These items are used to justify responses to the questions. These questions are designed to focus the performance review on the issues that are critical to company and department success. The questions lead the discussion away from the reviewer’s personal opinions and focus the discussion on the impact this person has on the work or the department.
In most circumstances, the rating scores of the manager, the team and senior management will be close. When this occurs the weighted average will be the final score. If ratings are widely different, the most extreme rating supersedes the lower.
Customer’s ratings supersede senior management, who supersedes the team who supersedes the manager.
Example 1:
We treat a 5 as no opinion. Team determines the result with a 7.
Example 2:
This person did not meet expectations of the team or the senior management. He/She is a 2 or 3. This appears that the manager is not managing the employee. How can a person meet the manager’s expectation but not meet the team or senior management’s expectations. A discussion with the manager is needed by their Supervisor.
There may be a unique case where one bad event is exaggerated and the manager feels the person is being treated unfairly. In this case, the highest score would be a 4 and the employee would be informed that this is an action item that they and the Supervisor would need to work together to devise an action plan to get the team members to raise the score.
Rating Scale
10. Trade and blog journals are writing rave reviews about employee’s work saying it is best in its class
9. Customers (externally/internally) are writing rave reviews about employee (must be documented in writing)
8. Exceeds expectation of the company senior management
7. Exceeds expectation of Product Owner and Tech Team
6. Exceeds reviewer’s expectations
5. Meets reviewer’s expectations / no-opinion
4. Does not meet reviewer’s expectations
3. Does not meet expectation of Product Owner and Tech Team
2. Does not meet of the company senior management
1. Customers are complaining about employee
0. Employee work is externally criticized by members of the technology community (e.g. PC Week)
Under this system, the manager can give a 4, 5, or 6. Any other rating requires outside input from the development team, the engineering group, senior management, customers, or the press.
Key Individual Performance Questions
The following questions can vary slightly from team to team. The manager rates the employee on a set of questions that drives the review process away from a standard list of items accomplished. These items are used to justify responses to the questions. The questions are designed to focus the performance review on the issues that are critical to company success and growth. They lead the discussion away from the Manager’s personal opinions about the person, and focus the discussion on what business impact this person has.
Feedback for a line Employee
Feedback for a manager
Overall Rating:
Career Goals:
What does this person passionately want to do?
The overriding objective of managers should be to identify what the person really wants to do and align job objectives accordingly. If this is not possible, the person should be encouraged and coached to find opportunities that will unleash energy and creativity. Super-performance teams can only be built with people who are passionate about their work. The greatest challenge of a manager is to creatively align the inner driving force of an individual with the corporate objectives required for success in the marketplace.
Training Needed:
What training is needed to move toward career goals?
Goals for next rating period (3 months):
Posted in Jeff Sutherland, Management, Mary Poppendieck, Quotes, Team Performance | Tagged: appraisals, Jeff Sutherland, Mary Poppendieck, performance reviews | 3 Comments »
Posted by Christophe on October 9, 2007
In this video (Dec 2006), Mary talks about how companies that compete on the basis of basis create a huge competitive advantage. The enemy? Complexity in the product and the process. It comes in three basic floavors:
All three flavors of complexity are rampant in software development processes, and you can’t go fast until you root them out.
Posted in Lean, Mary Poppendieck, Videos | Tagged: Lean, Mary Poppendieck | 1 Comment »