Please enable JavaScript.

Coggle requires JavaScript to display documents.

/\ || We are here We want to be here || \/, Sequence of…

- - - - Which Agile framework?
        
        LeSS
        
        Scaled Scrumban
        
        Scrum
        
        Kanban
        
        Scrumban
    - - Anything regular ought to be folded into an Agile event
        Anything ad-hoc = normal communication between Agile events
        Educate / train stakeholders to work with us, rather than force us to continue with waterfall practices, continuing the disconnect
  - - - Keep current board and introduce a tag to indicate which Product Team's ticket this is?
      - Three individual Product Team boards plus one umbrella board (what's the purpose of the umbrella board)?
      - Link between the detail of Jira and the need for higher level communication of what we're doing
        
        Roadmaps
        
        Jira-linked
        
        Separate from Jira
        
        Format?
        
        Lean: Later, Next, Now, Done
        
        Trello
        
        Excel
        
        Something else
        
        Roadmunk or Prodpad, for example, resulting from a DITAG discovery, would meet our needs much better (assuming they're still the same as those listed when the DITAG discovery took place). They allow users to propose ideas, which we can then attribute value / effort to in order to seamlessly prioritise in the open
        
        Who are they for?
        
        OneTISTeam & individual Product Team roadmaps
        
        Levels of detail in each
        
        Granularity of indicative times - Lean, Quarterly, Monthly, Weekly, Daily
    - - Keep as is (with a bit of a tidy up)?
      - Rebuild, with a greater Product Team split?
      - Replace with Sharepoint