Agility-Inclusion: Task Force Meeting 1

Europe/Zurich
54/R-035 (CERN)

54/R-035

CERN

6
Show room on map

Agility-Inclusion

openSE 2.0 Task Force

Basic information

Present: Rui Franqueira Ximenes, Renata Martins, Emeline Peyrat

 

Chair: Thijs Wijnands

Minutes: Jenni Kaipainen

 

Time: 3:00-4:30 pm

Date: August 28th

 

Agenda & Minutes

 

1. Introduction round

2. Introduction to the Task Forces

    1. Purpose and focus
    2. à adding flexibility seems to the direction in general

3. Introduction to Agile & Lean

Agile mindset: 4 main principles (Agile book of Thijs):

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration
  • Responding to change

à breaks down to 12 principles

à breaks down to multiple practices

 

4. Discussions

  • Projects differ. In some projects there is less flexibility; e.g. construction projects, you can’t build a roof before walls.
  • Should we focus on the project roles when discussing agility in a projects?
  • Epic
  • Agile Lifecycles
    • Many life cycle phases in the columns and following with the table the progress (as simple columns as planning, working and results even); similar to Kanban
    • Hybrid agile lifecycles: It can help when getting blocked. Maybe something in common with service design thinking
  • Scrum Master: Someone to talk with, a facilitator
  • Scrum board: Makes it easier to get an overview for people despite being from different backgrounds in the project
  • Where would risks be in relation with the lifecycle?
  • Needed for agility in CERN:
    • Awareness: training on the topic
    • Smooth transition with work that is not organized in an agile way
      • One opportunity to organize low level in agile way and then when bringing to upper level, switching the working style
  • Trying to classify which kind of projects/ parts of project the agile methods suit and which not. What constraints people have in using agility, after explaining this going into the topic more deeply.
  • If you apply agile in wrong place in wrong time it leads to troubles, as well as not using it in the right place the right time
  • Structure could be changed so that there is a toolbox for different situations/ scenarios?
  • What should be the audience? à It is for everyone .. but to what extend?
  • Trust, strong team, communication needed for agile mindset
  • Tools: e.g. Jira

Next steps

    1. Thijs collects ideas already to a powerpoint
    2. Make a proposal and write ideas down
    3. Same time, same place, 11th of September

 

 

 

 

There are minutes attached to this event. Show them.