JISC Answers

The tips from this session are listed below with the first one being their top tip.

Tips Table 1

1. Communicate as and when necessary (e.g. Google Talk, project blog)
2. Delegation as part of Team Manager allocation (PRINCE2)
3. Make sure everyone has bought into the methodology
4. Match methodology to work cultures

Tips Table 2

1. A Change Manager that’s business side and concentrates on the benefits
2. Involve users at all stages even the running, delivery and supporting the project
3. Perception mapping (Triz). Reconciling different views of requirements
4. Project Manager needs to understand the project
5. Understand the different motivations that all people involved in the project have
6. Relationships are key – get to know people

Tips Table 3

1. Initial eliciting and requirements gathering are valuable
2. Light design early, code as late as possible
3. Flexibility – review requirements as you go, allow change
4. Daily responsibility for decisions about what changes to accept
5. Beware transition to a service – dates and dependency

Tips Table 4

1. Anti-pattern – applying methodology from wrong cultural perspective. Match approach to local culture and language
2. Build shared understanding of how you are working
3. JISC reporting templates do not suit Agile approaches
4. Blogging as part of methodology – matches a recognition that change is part of the process (plus as a means of reflection)
5. Any methodology requires discipline
6. Test cases as basis of shared understanding of function

Tips Table 5

1. Flexibility to engage users (lunches, video conferences)
2. Establish regular meetings with stakeholders (formal/informal)
3. Psychological transition of change
4. Knowing where you are in progress (moving on from the plan)
5. Using audio-visual-kinesthetic to engage people (coaching)