Managers Dilemma-

Preview:

DESCRIPTION

 

Citation preview

Managers DilemmaHandling a Lean Team in a Small

Organization

By

Soma Bhattacharya

Netherlands | USA | India | France | UK

SOFTWARE DEVELOPMENT DONE RIGHT

www.xebia.in; Blog :http://.xebee.xebia.in

A THINKER over a WRITERA WRITER over a SPEAKER

An Observer. A Learner

Who am I ?

My Team does Kanban

• Pushing out Features/stories

• More productivity from Teams

• Make his/her team’s work more transparent to higher management

• Reach his/her quarterly/yearly goal

• Be in charge and have the authority

• Make decisions for the team.

What a Manager wants?

• Good work environment• Good

salary/hikes/reviews• Work in a good product

and team that build his/her resume

• To be part of a winning team

• To be recognized

What a Team Member wants?

The Conflict

A single cockroach will completely wreck the appeal of bowl of cherries but a cherry will do nothing at all for a bowl of cockroaches - Rozin

Why is Culture Important?

What Inspires a Team Member?

What is a Manager Responsible For?

Dissect Roles and Responsibilities

Keep it in Ready State to Pull

The Thinking Process

Kanban in a Start Up Culture: Predictability and Visibility

Stop Moving-Stay Where You Are

Learn from Your Failures

Management is not about being at Center Stage

Value Map Steaming- Find the gaps

Know your luggage and Monitor it

Release PlanningPlanning Timeline Happens Done By Inputs Outputs

Roadmap 4 hours Once a quarter

Executive Management

• Business Epics• Architectural Epics• Goals • Vision• POC• Parking Lot

• Final Roadmap• Feasibility• Approximate Timeline• Risk Assessment

Release 4 hours 1/month PO, Domain Experts, Security Team, PM

• Final Roadmap• Teams ( Capacity +

Velocity )• POC - Arch/Secure

Design review docs• Risks ( Mitigation plan ) • Cross Team

Dependency

• Release plan per team • Release Definition of Done • Success criteria for release

Grooming 1

2 hours Every sprint PO, Team • UX (high level)• Hierarchy of stories

• Team Backlog• success criteria for feature outline

Grooming 2

2 hours Every Sprint PO, Team • UX ( detail ) • Ready backlog

• Final frozen Backlog • UX ( final ) • Security Risk Assessment• Security Impact Areas • Hierarchy of user stories • Acceptance tests for feature• Final - Release Definition of Done

Plan From the Beginning, Not @ Team Level

Thank You

Email: sbhattacharya@xebia.com

Agile Consulting and Transformation Services Scrum

XP, BDD, ATDD DSDM

FDDPoint based coaching workshops

Agile transformation readiness review

Mid-cycle intervention and correction

Agile transformation solution design and execution

Agile Consulting

Contact us @

Xebia Indiainfoindia@xebia.com

Websiteswww.xebia.inwww.xebia.comwww.xebia.fr

Thought LeadershipHtto://xebee.xebia.inhttp://blog.xebia.comhttp://podcast.xebia.com

Recommended