1. What are we trying to achieve?
1.1. The What & Why?
1.1.1. Not focus on the how
1.2. SDLC Gate 2?
1.3. A reference document to support the start of a project?
1.4. A step to obtaining funding?
1.4.1. When has a BPE actually stopped a project going forward?
1.5. An Indicative cost?
1.5.1. Don't forget the OPEX
1.6. An outline of the teams and effort needed?
1.7. Assist roadmap planning?
2. How Can we Improve?
2.1. Categorisation levels
2.1.1. Can we make these help the BPE process?
2.2. Use a complexity Model, standardisation of questions/items
2.3. Different BPE approaches
2.3.1. BPE lite/BPE full?
2.4. Guided templates on roles & areas to cover
2.5. Global standard approach
2.6. Look at Methodology
2.6.1. T-shirt size where we can
2.6.2. What is out there
2.6.3. Different methods for different projects
2.7. New tech - Office 365, what can it do for us
2.8. Collaboration
2.8.1. It doesn't have to be a meeting
2.9. Making annual opex form part of the BPE
2.9.1. Mindful of going to deep into a solution but call out what we know.
2.10. Do we always need to BPE, or BPE in full?
2.11. Can the BA be involved earlier in the process to help define the brief
2.12. Set a mission statement of what the BPE (or equivalent process is), make all aware
2.13. Ensure business benefit is provided and updated if need be based on BPE outcome. A quick measure to proceed or stop.
3. Today
3.1. The good
3.1.1. Collaboration amongst IT teams
3.1.2. BPE is an education for those involved
3.1.3. Done well it forces individuals to be active and decisive
3.1.4. Done well we have early engagement from the the right teams, big issues captured early
3.1.5. Sets the scope (in/out)
3.1.6. Early project Framework established
3.2. The bad
3.2.1. Everyone adds fat to their cost
3.2.2. A reluctance to provide costs on light info
3.2.3. Poor project briefs
3.2.4. The fallout when an area is missed
3.2.5. When a BPE forms the basis of a full PAR
3.2.6. Changing scope and abuse of BPE activity
3.2.7. One BPE process does not fit all
3.2.8. Different expectations to different people and roles
3.2.8.1. Expectations, line item breakdown
3.2.8.2. Go high - More detail requested, Go Low and it takes too too long.
3.2.9. US/EMEA processes different
3.2.10. cat 5 ceiling is too vague
3.3. The challenges
3.3.1. Different perception of a BPE both in the business and IT
3.3.1.1. Different purpose to different people
3.3.1.2. Acceptance this is just an estimate
3.3.2. the more you look, the more you find, the longer it takes, the more it costs etc
3.3.2.1. Just enough/just in time...but we don't do this consistently
3.3.3. A mix of solution/non solution led - completely different approach needed
3.3.4. People's time and availability
3.3.5. Cross portfolio/3rd party/US items adds complexity
3.3.6. Getting a BPE approved, especially as we tackle global items.
3.3.7. Sharing of information
3.3.8. Confidence we have captured everything
3.3.8.1. getting the message across It is ok to not know