Monday, February 6, 2017

Agile Myths

Agile Myths:      Some myths about Agile are debunked

All of the below are false

Not for operations
Not for regulatory projects
Not for Mainframe projects
Not for all projects
Not for BIG projects
Only for techies
Scope Creep
Lack of control
High risk
No discipline
No design
No planning
No architect needed
No documentation
No estimation
NO PM's needed

Distributed Agile!-   How do we do this distributed

1. Agreements
2. Standards
3. Tools
4. Processes

7 Rules of successfully distributed teams


1. Don't
2. Don't treat remotes as if they were locals
3.  Dont treat locals as if they were remote
4. Latitude hurts, longitude kills
5. Don't always be remote
6. Invest in the appropriate tools and environments
7. Establish standards and agreements


The DNA of success
1. Agile exposes capability gaps
2. Awesome Capability
3. Attitude
4. Aptitude

Agile helps create a great working culture

You don't want a toxic brilliant team not a happy dud one!
High performing teams are happy and highly capable!


Agile Pitfalls

1. Environment
    Wrong physical environment
    Lack of proper tools
    Funnel not managed - too much WIP
    Resources splintered and working on multiple projects

2.  Leadership

    Leaders don't walk the talk
    Wrong leadership style - command and control instead of servant leadership
    Lack of a clear shared purpose and strategy
    Lack of trust

3. Knowledge
    Lack of training or inaccurate material
    Teams don't know what Agile really is
    Leaders not trained and aware
    Lack of sharing
    No access to coaching
4. Capability
    Poor core capability
    Lack of capable Agile PMs and IMs
    Lack of critical thinking for problem solving
    Can't do attitude

************************************

Why change? Why Agile?


1. Happy people
2. Reduced risk and cost
3. Faster time to market
4. Improved quality
5. Increased Revenue
6. Happy customers

Increased Profitability and happy shareholders

****************

7 Key impacts of going Agile

Resource allocation
Team structure
Work environment
Work prioritization
Leadership style
Making time to collaborate
Authentic Transparency

No comments: