Lean-Agile Thinking

Thoughts and comments

Practical Expirence

From different teams and organizations, I have some good and long practical experience with below areas. For most of the processes and practices I have done some fun training and coaching of individuals and teams in Europe and Asia.

See also  View Mads Troels Hansen's profile on LinkedIn

From a management perspective

  • How to scale Scrum with many teams
  • When not to use Scrum!
  • Agile and Scrum in a Offshore setup
  • Organizational changes in an Agile transition
  • Why Scrum is so hard to start
  • Agile and the rest of the organization
  • Scrum, iterations and sustainable engineering
  • Agile and CMMI
  • Kanban driven development with flows and people not working in teams.
  • Leading the organization towards higher productivity
  • Mitigating risks in a fast and efficient way
  • Focus on maximizing ROI and increasing business value
  • Changing focus from project centric to more system oriented with value streams

Different Practices

  • Improving Agile requirements with User Stories, acceptance criteria combined with end-to-end scenarios and mockups.
  • Different type of Agile estimating for different level of planning (Planning poker, task breakdown) 
  • Working with test and QA in Agile development, inside and outside iterations. 
  • Accelerated knowledge sharing with review and estimation
  • Minimizing Cost of Change with Refactoring, testing and automation
  • Using Retrospectives to align focus and establish a heartbeat of continuous improvements
  • Emergent design and patterns

Working as Product Owner / Product Manager

  • Release planning and managing a Product Backlog (stocking)
  • How to manage the upstream processes in the organization
  • How to work with development teams with long term success
  • Working from Vision, Value Proposition and down to detailed requirements and code
  • Building trust and sustainable productivity

Working as Scrum Master / Agile Project Manager

  • Making room for the team
  • Coaching and establish the direction without defining a solution
  • Initiating self organization
  • Building trust and set focus
  • Out of the box thinking with different pragmatic tools
  • Establish different rhythms
  • Root course analysis
  • Distributed development with global teams and many nationalities

Selected tools

  • Different Pragmatic tools to enable collaboration and team dynamics
  • Kanban boards with shared focus and ownership 
  • Microsoft Team System, integrating processes, work items, documents, code and builds
  • Automated build and CI
  • Information radiators
  • Valuestream mapping
  • Burndown and burn up charts
  • Innovative games
  • My two favorites: A whiteboard and a tablet pc :-)

 

Leave a Comment

(required) 

(required) 

(optional)

(required)