Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

  1. Assign dedicated Agile coach to introduce a new framework, or coach teams operating effectively in the existing environment 
  2. In order to support product scaling and delivery extension consider Scaled Agile frameworks like Nexus, SoS, LeSS, SAFe, Spotify, etc.
  3. In case of parallel development of same product by several teams/ streams preserve cadence and synchronization, i.e. align iteration plans and goals, resolve dependencies via cross-collaboration.
  4. Think of switching to another software development methodology or/and framework in case of any changes in complexity, duration, environment, constraints variability, stakeholders availability, etc
  5. Revisit length of iterations to make them shorter for reliable planning and less risks of changes during their execution
  6. When following Scrum, make sure to have all roles, artifacts and events in place as per the Scrum Guide. Ensure that teams understand and follow Scrum pillars and values.
  7. When following Scrum, make sure to have proper time boxing managed for the events, i.e.
    1. Sprint Planning - 2-4 hours 
    2. Sprint Review - 1 hour 
    3. Daily Standup - 15 minutes 
    4. Sprint Retrospective - 1-1.5 hours 
    5. Backlog refinement - 1 hour 
  8. If Agile is incorporated into methods of work, check on Agile values and principles to be pursued by the teams and stakeholders.

Useful materials

https://www.scaledagileframework.com

https://scrumguides.org/scrum-guide.html 

Pragmatic Agile for a Fixed-Price project 

  • No labels