BT Young Scientists &

Technology Exhibition

App

Risk Management

Project Risk

Staff Turnover - (Risk: Likely / Impact: Extreme / Manage as Emergency)

Would effect development of App

May take time to replace – hence project delayed

Prevention:

Tie down staff to Project Contract

Document while developing and within coding

Functionality - (Risk: Unlikely / Impact: Extreme / Manage as Proactively)

Too much functionality, not easy to navigate – could delay delivery date

Prevention:

Strip out functionality not required

Project Risk

Security - (Risk: Unlikely / Impact: Extreme/ Manage as Systematically)

Information can be taken, changed/deleted

Would damage BT’s image as provider of wifi and telephone services

Prevention:

Talk to BT and explain more time required, before launch

Poor Productivity - (Risk: Unlikely / Impact: Medium/ Manage as Proactively)

All it takes is one of the team members to produce poor work

Prevention:

Should have a back up plan/resources/quality control/document all steps/ QA

Business Risk

Content Suitable for Students & Corporate - (Risk: Medium / Impact: Medium / Manage as Strategically)

These are 2 different target markets, difficult to produce content for both

Prevention:

Talk to stakeholders and incorporate them into design process.

Monitor traffic once application is launched, Analytic tools.

50th Anniversary - (Risk: Medium / Impact: Medium / Manage as Strategically)

The focus of the Market Manager is through Linked In

Prevention:

Run a Google Ad Campaign

Facebook Page for BTYS

Business Risk

BT Resources - (Risk: Medium / Impact: Medium / Manage as Strategically)

After October 2012 BT will have to commit to resources for implementing the App

Prevention:

Team should be involved again at this stage

Year Round Exposure- (Risk: Medium / Impact: Medium / Manage as Strategically)

The App needs to change throughout the year to avoid becoming stale

Prevention:

Team need to be involved

Technical Risk

Scoping - (Risk: Unlikely / Impact: High / Manage as Systematically)

It’s not clear if the project was scoped out correctly at the start

Prevention:

Establish requirements and have BT sign off on them.

Testing/Debugging - (Risk: Likely / Impact: Medium / Manage as Systematically)

As this is a new App and functionality is changing this area is hard to estimate

Prevention:

Development & QA need more time

Compatibility - (Risk: Unlikely/ Impact: Medium / Manage as Proactively)

All Software features e.g. graphics need to be supported by IOS4&5 and HTML5

Prevention:

All features should be tested on the above platforms

Technical Risk

Synchronizing - (Risk: Likely / Impact: Medium / Manage as Systematically)

It’s not clear how BT systems will be integrated.

Prevention:

This will need to be tested and will be time consuming.

Security During the Event - (Risk: Unlikely / Impact: High / Manage as Extreme)

Can the systems handle the traffic

Prevention:

Needs to be fully tested over & over again.

Back Up Plan - (Risk: Unlikely / Impact: High / Manage as Emergency)

If App fails on the day what contingency plan is in place.

Prevention:

Need to discuss with BT.

Reputational & Political Risks

App Performance - (Risk: Unlikely / Impact: Extreme / Manage as Emergency)

Negative exposure for BT

BT will loose its year-round exposure

BT wouldn’t use Digital Skills Academy again

Prevention:

Test using large numbers e.g. students in Digital Hub

Identify critical path tasks

Negative Posts on Social Media Sites - (Risk: Likely / Impact: Medium / Manage Systematically)

Effects the event and sponsors in a negative manner

If not dealt with can escalate further

Prevention:

Embrace the negative comments

Make the relevant changes

Documentation/Training

Hand Over Document - (Risk: Unlikely / Impact: Extreme / Manage as Emergency)

It’s not clear if there is one

Training document required for BT staff

Prevention:

Document needs to be drawn up

Training plan needs to be put in place

Nature Risks

Disaster Recovery Plan - (Risk: Unlikely / Impact: Extreme / Manage as Emergency)

Fire

Flooding

Prevention:

Back up Off-Site

Daily, Weekly, Monthly.

Always use version control

Four Main Phases of BTYS Project App

Preparing for the Project• Deliverable – Specification/Scope stick to clients brief and sign off.• Delivery Date – October 2012 with LIVE DATE Jan 2013 doesn’t make sense• Budget – seems to be no budget or is there• Acceptance of Project – the Team seemed to change from the brief given.

Setting up the Project• Project Implementation Plan – Final delivery in October 2012• Technical Solution – kept changing, yet the technologies talked about are not new.• Any Contracts, Terms & Conditions – seems to be only to meet October deadline.

Implementing the Project• Risks Monitored – continuous monitoring• Manage Contract – contract seems to finish in October, 3 months before LIVE DAY• The deliverable date is October for the Team.

Review Project Implementation• Structured Review this is clearly something that the team cannot do• Requirements Met? How do they know if the requirements are 100% met, until LIVE DAY• Lesson’s Learned – if the team is not going to be around how will they be able to identify• What went wrong? – Only when the App goes LIVE will you ever know 100% what went

wrong

Conclusion

BTYS Digital Skills Academy Team

Main Risk is that Team is finished in Oct 2012

Thanking You