Agile Mëtteg - Jan. 2011

AGILE ENTERPRISE
Agile Mëtteg – January 27th, 2011

ABOUT US
27 January 2010
Agile Mëtteg – Agile Enterprise
2

AGILE PARTNER SERVICES
IS Methods Services
Custom Software Development & Maintenance & Biz Solutions
Our core business to answer customer needs
IS Dev services
Thanks to our expertise we can support IT team to reach their productivity & quality objectives (Assessment, Coaching, Support, Training, Resource delegation…)
IS Users Services
We can support Product & Services owners to work closely with the IT team (Assessment, Coaching, Support, Training, Resource delegation…)
IS methods services
We can support Methods and Methodologies owners to implement agile approach within the methodologies portfolio (Assessment, Coaching, Support, Training, Resource delegation…)
1
4
Software Development & SoftwareMaintenance&Biz Solutions
2
IS UsersServices
IS Dev Services
Agility
Agility
2
3
1
Agility
27 January 2010
3
3
4

SPEAKERS
27 January 2010
4
Agile Practitioners
Scrum, Lean/Kanban

Current paradigm of an ENTERPRISE
27 January 2010
5

THE BIG PICTURE
27 January 2010
6
Customers
Business leaders
Product managers
Business Operations
Management
Support
IT Operations
Development

BECOMING AN AGILE ENTERPRISE
Paradigm optimization
27 January 2010
7

THE ENTERPRISE
27 January 2010
8
Project mgt
Strategic
Software
Project
Project
Process & operations
Process & operations
Strategic
IT
Method& Process
Biz
Key Users
Dev. team
Strategic
Project
Strategic

THE BIG PICTURE
27 January 2010
9
Customers
Business leaders
Product managers
Optimize the whole!
Business Operations
Management
Support
IT Operations
Development

LEAN SOFTWARE DEVELOPMENT
27 January 2010
10
Process
Project
Team

AGILE & LEAN VALUES
27 January 2010
11

4 VALUES
Extract from Manifesto for Agile Software Development
[…] We have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
27 January 2010
12
Source: http://www.agilemanifesto.org/

LEAN PRINCIPLES
Eliminate Waste
Create Knowledge
Build Quality In
Defer Commitment
Deliver Fast
Respect People
Improve the entire System
27 January 2010
13
Partially done work
Extra features
Relearning
Handoffs
Tasks switching
Delays
Defects

RESPONSIBILITIES
Focus on Value, Speed and Quality
27 January 2010
14

BENEFITS
Scaling agile at the entreprise level
Beyond local optimization and narrow focus on project / team / software
Create a sustainable and appropriate environment for agile development
« Fast – Flexible – Flow »
Optimized value for the Enterprise
27 January 2010
15

About you
27 January 2010
16

PARTICIPANTS
Who are you?
What is your role?
What do you know about agility?
What about your enterprise?
27 January 2010
17

THE CORE BELIEFS OF AGILE
You cannot know everything required to build a software product at the start of the project.
Customers cannot accurately tell you what they want at the start of the project; instead, they will gain clarity as the project proceeds.
You want feedback from the customer as often as possible and you want to give developers feedback on how they are doing as soon as possible.
Working code is the most accurate way of seeing the progress of the development effort.
Groups working together minimizes delays as well as the loss of information between people.
Moving test to the front of the development cycle improves the conversation between developers and customers and testers and, thus, improves the quality of the code.
While management can set expectations for what work is done, management must not demand how that work is done.
Working on one project at a time improves the productivity of a team.
27 January 2010
18
From your experience, what is true?

THE CORE BELIEFS OF LEAN
Most errors are due to the system within which people work rather than to the individuals themselves.
People doing the work are the best ones to understand how to improve the system.
Ad hoc in not an acceptable process.
Looking at when things are done in a process is a more useful guide than trying to make sure every step of the way is as efficient as possible.
Our measure for success must be related to the amount of time between when ideas come in and when they are manifested as value to our customers.
Management must work with the team to improve the way it works to improve its own efficiency.
Teams are most efficient when the amount of work is limited to their capacity.
Team efficiency improves by minimizing the amount of work in progress at any one time.
When evaluating actions, we must optimize the whole, not merely improve individual steps in the process.
There are principles in software development that must be followed in order to reduce waste.
27 January 2010
19
From your experience, what is true?

Wrap-up
27 January 2010
20

NEXT SESSIONS
The next sessions will cover all 3 areas
Business
Requirements, Portfolio Management…
Management
Kanban, Communication, Estimation…
Delivery
Clean code, modeling, TDD…
27 January 2010
21

RESSOURCES
Agile Partner: www.agilepartner.net
NEW!blog.agilepartner.net
Agile Interest Group Luxembourg:www.aiglu.org
Recommended readings
27 January 2010
22

NEXT TRAININGS & CERTIFICATIONS
27 January 2010
23
Complete calendar on: http://www.agilepartner.net/training/focus-on/

CONTACTS
Thank You
27 January 2010
24

Agile Mëtteg - Jan. 2011

by Agile Partner S.A. on Jan 28, 2011

Accessibility

Categories

Upload Details

Usage Rights

2 Embeds 56

Statistics

Agile Mëtteg - Jan. 2011 Presentation Transcript

http://blog.agilepartner.net	52
http://www.agilepartner.net	4