As I read books, I note the contents that I think are most important - for me. You might find it useful, but consider reading the book for yourself:
Jim Highsmith: Agile Project ManagementThis is one of the best books I've read about agile development so far. I highly recommend it to anyone who works with agile projects. It is a must have in any book shelf.
Linear thinking, prescriptive processes, and standardized, unvarying practices are no match for today's volatile product development environment.We value:
- Individuals + Interaction over Process + Tools
- Working Code over Comprehensive Documentation
- Customer Collaboration over Contract Negotiation
- Responding to Change over Following a Plan
Documents are no suitable replacement for direct customer contact. Meeting protocols are, best case: noticed - worst case: an impediment.
Encourage exploration.
Build adaptive teams (self organized + self disciplined)
Favor Simplicity.
Deliver Customer Value on each iteration.
Employ Iterative, Feature-Based Delivery
Champion technical excellence (which leads to adaptability)
You
manage things, you
lead people. Management deals with complexity, leadership with change. Both are necessary. The more exploratory the project, the more important is leadership.
Leaders are leaders because of who they are: they depend on influence derived from respect, which in turn is based on integrity, ability, fairness, truthfulness - in short: character. Authority is earned bottom-up, not bestowed from above.
Managers fear change, leaders encourage it. Exploration can cause anxiety and fear. Good leaders create a safe environment, where it is OK to voice outlandish ideas.
PMs who focus on diagrams, budget and histograms are dooming their team to mediocrity. Innovative teams are led, not managed.
Teams need a purpose, goal, vision. That does not change - execution of the task does. They need encouragement to explore, make mistakes and regroup.
Shared space: Interaction by using demos, prototypes, simulations. Managers, customers, developers, marketers have a better time discussing when there is something tangible to base the discussion on. Requirement documents are too abstract - not visual, not common. Create tangible artifacts - you have to know who needs to interact, and what those people can base their interaction on. Not all artifacts are common-place and can be understood by anyone.
Vision: Targeted deadlines (+ reasons for those deadlines), high priority features (only few + reasons for them)
Architectural overview, component + interface description. Not too detailed.
Interaction: Trust and respect lead to meaningful debate, and vice versa.
With too little coordination, teams will diverge so far that integration becomes a nightmare. Too much coordination, and teams will be clogged by meetings and information overload.
Cooperation first, documentation second. Useful information is based on cooperation 70%, documentation 30%
Insist on Accountability: Individual commitments to delivering a feature in an iteration -> accepts accountability when PM is involved, provides requirements + information, resolves impediments.
Commitment -> hold accountable.
Hold each others to commitments.
Meet commitments -> builds trust.
Trust is the foundation of collaboration.
Create an adaptable, self-organizing team: grant as much autonomity as possible, destructure to the extent possible, then coach individuals and get rid of those wo don't fit.
Make unilateral decisions at times if necessary, make decisions with team involvment, but primarily delegate decisions to the team.
Self Disciplined Individuals:- Accept accountability for results
- Contemt reality through rigorous thinking
- Engage in intense interaction and debate
- Work willingly in self-organizing framework
- Respect colleagues
If you get the right people, self-discipline comes more easily. Get the wrong ones, imposed discipline creeps in, destroys trust, respect and egaliterian atmosphere (p.72). Note: this is emphasized because it was the problem on my team.
Simplicity:
When you want your boat to go fast, it is easier to cut anchors than to add horse power.
Simplify your process by taking out the detailed tasks and compliance work -> force people to interact. The only rule: Us your good judgement. Be quick, but don't hurry.
- Simplify the process
- Simplify the activities
- Simplify compliance
Agile Development + Framework:
Encourage
- Thinking
- Acting
- Interacting
If your goal is reliable innovation, your process must be organic, flexible and easy to adapt.
Explore:
- Deliver planned features
- Create a collaborative, self-organizing project community
- Manage interactions with customers and PM
After your envision phase, interactions will consist of the following loop:
- Speculate
- Explore
- Adapt
- Speculate...
This requires good judgement!
Envision:Create a clear, compelling vision
- is hard
- takes work
- takes leadership
Elevator Test Statement:For (target customer) who (statement of need or opportunity), the (product name) is a (product category) that (key benefit, compelling reason to buy). Unlike (primary competitive alternative), our product (statement of primary difference).
Product Vision Document:- Mission Statement
- Target Customers + their needs
- Customer Satisfaction Measures
- Key Technology
- Critical Product Constraints
- Competitive Analysis
- Key Financial Indicators
Get The Right PeopleThe top 20% of people produce about 50% output.
Key Qualities are: a) Capability b) Self Discipline
Speculate/Planning- Formulate Features that are understandable to customers: features act as interface to customers
- Feature Cards: Front: Feature information for planning, Back: technical Task information to estimate effort
- Have a Product Feature List (backlog)
- Feature = Piece of a product that delivers value to the customer
Feature Cards:Name, ID, Description (in customer terms), type (customer/technical), dependencies, estimated effort, acceptance test
Iteration planning:- Take high risks early, before high values
- Have iteration themes (a.k.a. sprint goals)
Risks:- Inherent schedule flows <--> Iterations, Regroup
- Requirement Inflation <--> != Evolution!
- Employee turnovers <--> Collaboration
- Specification breakdown <--> Decide!
- Poor productivity <--> Morale + People
Project people need to be visionary, positive and brutally honest about the risks.
On Paper...APM advocates less up-front planning, architecture and requirements gathering because information is gathered as the project unfolds.
Up-Front paper is lying to the management.. but that's just my take on it.
Arichtecture...
...needs to have a good mix of up-front and just-in-time.
Get the right people
- Appropriate technical ability
- right behaviour
- getting the right people on the bus is more important than where the bus is going
- most companies build bueraucracy to manage the small amount of wrong people, driving away the right people, creating the need for even more bureaucracity -> wrong people work on delivery, right people work more on compliacne work
Release/Iteration PlanWork- or task driven plans often degenerate into very detailed, prescriptive plans.
Teams often get lost in intermediate artifacts, that have little bearing to progress.
Feature driven planning helps overcome this problem.
Technical Deptlip service about technical excellence and being pushed into hurrying lead into technical dept.
CoC (cost of change) raises slowly first, but rapidly later...
- no allowance for periodic refactoring
- poorly maintained test data
- constant pressore to cut time
are DEADLY.
Without firm dedication to long term technical dept management, development teams are pressed into the trap:
- dept leads to delays
- delays lead to pressure
- pressure lead to hurrying
- hurry leads to dept
The secret to long term dept management is: do it early, at lower cost, easier to justify.
Handling technical dept can result in architectural changes. Holding the CoC down by not changing architecture means that when change has to happen, neither code nor people will be ready for it.
If not done:
- Loose customers to more responsive competition
- Good agile team will work faster with technical excellence
- Excellence costs a little more, but reduction in compliance work will more than pay off
Simple DesignRemain grounded on what you know rather than what you anticipate. ADAPT to change, don't ANTICIPATE it. Good architectures encompass aspects of both. Anticipate known change only.
Value adaption over anticipation, but value both.
Coaching + Team Development- Focus on delivering results - revisit key constraints and tradeoffs
- Cheerleader: members want a boost occasionally
- No blabla: facts, even negative ones
- Key motivator: understand what outcome is expected
- Right people find their own way, if they know where to go and how to travel
Core elements needed to attract, focus and keep key employees:
- Understand expected outcome
- Understand why what they do is important
- Work with a team that is committed to quality
Don't give a vision that is too far away, otherwise there might be doubts about its possibility. A 2 year plan can be daunting, a 2 month vision easier.
Molding a team
- Trust. No trust -> superficial interaction
- Interaction. No interaction -> focus on individual goals
- Satisfactory Conflict Reolution. Not done -> reduced trust
- Participary Decision Making. If not participary -> undermine commitment to team
Trust and respect are closely tied together.
If, fundamentally, you don't trust people, then there is no line, no pointin time, beyond which people suddenly become trustworthy.
Some failures will occur, don't impose strict controls. Get rid of untrustworthy individuals instead of abusing the entire organization with rigurous controls.
Channel debates to build trust and respect rather than undermining them. Focus on issues, not individuals.
Manage team mood by managing your own mood.
Interaction drives innovation. No interaction -> no synergy
Each team member must take initiative to confront others when they are not performing or behaving according to team rules. This includes calling the PM if situation dictates. No
exemptions.
Discussions need to be focused on getting all relevant information onto the table.
Mood, or "emotional intelligence" in leaders has much larger impact on performance than imagined. Team members pick up the mood of the leader within a couple of hours.
Rules of engagement:
- Everyone has an equal voice
- Everyones contribution is valuable
- Attack issues, not people
- Keep privacy within the team
- Respect each other and your difference
- Everyone participates
Very difficult, but important: confront team members who violate behavioral or performance standards. If they aren't confronted, mistakes aren't identified, and no learning occurs. Failing to address these issues is one of the greatest complaints against project managers.
Reviews and adaptive actions- Reflect, Learn, Adapt
- Change Pace: Relaxed Review Day
Customer Focus Groups
focus on discovering + recording desired changes, do not gather detailed requirements.
Technical Reviews, Team Performance Evaluations: Retrospectives.
- What went well?
- What didn't go well?
- How do we improve next iteration?
- What don't we understand?
Project status reports
The Agile Vision- Are you delivering innovative products to your customers?
- Are you excited about going to work every day?
Agile Processes and Agile People lead to Agile Products.
Project cultures and management controls for exploration usually are at odds with each other. Exploration is key.
Don't work in Dilberts company.
Don't be Dilbert.
APM Style:
Leadership and Collaboration
(NOT: command and control)
Leading is more difficult and rewarding. PM + P leaders
champion the vision.
Leadership includes staff selection, deployment and ongoing encouragement. Leaders help the team focus on delivery while minimizing compliance work.
Steer people towards role that match their abilities + talents, develop technical and behavioral skills, encourage people through frequent feedback.
Create environment of "no fear".
Soft skills are hard.
Hard skills are easy.
Use your god damned common sense.