Your SlideShare is downloading. ×
Cloud computing implications for project management methodologies
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Cloud computing implications for project management methodologies

2,896
views

Published on

Cloud based technologies are becoming increasingly pervasive across society and are considered by many in business as the next major disruptive innovation. For the first time, organizations can …

Cloud based technologies are becoming increasingly pervasive across society and are considered by many in business as the next major disruptive innovation. For the first time, organizations can consume, as needed, on-demand, business ready Cloud based enterprise services. This is also known as the Consumerization of IT.

Transitioning to, or deploying new IT systems and services using Cloud technologies present their own unique set of challenges to the IT Departments, Project managers and Pproject management Offices (PMO) alike.
The primary objective of this presentation is to provide a number of key considerations for Project Managers in dealing with projects involving Cloud computing technologies.

This was presented at the 25th International Project Management Institute's Global Conference in Australia on the 11th October 2011 by Rob Livingstone

Published in: Business, Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,896
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Cloud computing: Cloud Computing: Implications for Project Management Methodologies.
    ROB LIVINGSTONE- PRINCIPAL, Rob Livingstone Advisory Pty Ltd, and
    - Fellow, University of Technology, Sydney
    Brisbane, 11th October 2011
  • 2. Cloud computing: Cloud Computing: Implications for Project Management Methodologies.
    What I’ll be covering:
    Cloud computing basic definition and attributes
    Overview: Public, Private and Hybrid Cloud
    Next few years – from confusion to calm
    The consumerisation of IT effect in the enterprise
    Project Management implications
    Cloud: Some key considerations for organisations
    The future is now
    Questions and discussion
  • 3. 1. Cloud computing basic definition and attributes:
    • Cloud is a very broad term for IT systems accessed via the Internet or your browser.
    • 4. In public cloud, the various components are all run by an external party, and you do not own anything, other than the data that you load into the system.
    The primary attributes of public Cloud systems are:
    You subscribe to the service (never own)
    The system is accessed via the Internet
    You neither have control or title over the Cloud system
    You have limited to full title over the data that you upload
  • 5. 2. Overview: Public, Private and Hybrid Cloud
    Private
    Hybrid
    Public
    • No control
    • 6. No ownership
    • 7. You own data
    • 8. Apps stay behind
    • 9. You control all
    • 10. You may own
    • 11. Offers balance of security, control
    • 12. Can be more complex
  • 3. Next few years – from confusion to calm
    Gartner Hype Cycle 2011 – Cloud has very it’s own cycle
  • 13. 4. The consumerisation of IT effect in the enterprise
    … also known as the ‘democratisation’ of IT
    Fuelled by Cloud and pervasively accessible web based applications as an individual ….
    I see it, I like it, I want it, I buy it (or it’s free!), I use it – Now!
  • 14. 4. The consumerisation of IT effect in the enterprise
    Individuals have unprecedented access to all type of IT systems, from email, file storage, accounting, CRM, banking, shipping, social networking (eg Facebook™ ).. The list is almost endless.
    What is meant by ‘consumerisation’ of IT?
    • Individuals can use / buy systems as they see fit.
    • 15. Personal choice and immediacy reigns supreme
    • 16. Buy it / use it without necessarily a long term in mind
    • 17. ‘Apps’ – for iPhone™, Android™, etc
    For enterprises, however, this presents a number of challenges for the unwary, and have potentially serious implications for the PMO
  • 18. 5. Project Management implications
    Inconsistency in understanding of ‘Cloud’
    Cloud: Compression of time
    Reversal of the traditional business case: ‘buy before you try’
    Cloud, pilot projects and driving innovation
    ‘The viral cloud’ phenomenon
    Managing project boundary conditions
    Challenges for standard methodologies such as PRINCE2
    Use of cloud technologies BY project managers
  • 19. 5. Project Management implications
    a) Inconsistency in understanding of ‘Cloud’
    • While there is largely a solid understanding of what’s inside the public cloud ‘black box’ by CIOs and those in the IT industry, this is largely not the case for line-of-business executives and managers.
    • 20. As long as this asymmetry of understanding exists, the full relevance and potential of cloud computing may not be fully realised in organisations.
    • 21. Project managers also need to become familiar with specific issues and challenges associated with cloud computing, and quickly.
  • 5. Project Management implications
    b) Cloud: Compression of time
  • 22. 5. Project Management implications
    c) Reversal of the traditional business case:
    ‘Buy before you try’
    • Public cloud offers, potentially, enterprise ready applications in hours or days
    • 23. Mostly have easy to manage configuration options through a ‘control panel’
    • 24. Impatient business stakeholders want to bypass the ‘paralysis by analysis’ stages associated with the requirements gathering and analysis phases.
    • 25. ‘Better 90% on time’ is often the catch-cry of business stakeholders who are becoming increasingly impatient with the complexity and lead times on IT projects.
  • 5. Project Management implications
    d) Cloud, pilot projects and driving innovation
    • Cloud systems can be invaluable in supporting innovation initiatives in that:
    • 26. no up front capital is required,
    • 27. walk-away costs are minimised,
    • 28. Very speedy
    • 29. Often does not require IT
    • 30. The opportunity for immediate and rapid scale-up to production exists without the need provide working capital:
    • 31. Very tempting for users and business stakeholders
    • 32. Comprehensive due diligence needs to be done before production scale-up!
    • 33. Set expectations a the start that the immediate scale-up to production will not automatically occur
    • 34. Need to manage expectations
  • 5. Project Management implications
    e) The ‘viral cloud’ phenomenon
    • A viral Cloud is characterised by a localised initial installation of a Cloud system (approved or otherwise!).
    • 35. Additional subscriptions gradually purchased for others outside of the initial user pool to approve workflows, access documents, process information etc.
    • 36. The low barrier to entry could mask the potential for additional cost, unmitigated risk and breach of minimum governance standards.
    A leading Australian University experienced an unauthorised deployment of a Cloud system that was funded from one Faculty’s discretionary budget, as it fell within their prevailing local discretionary expenditure approval limits. This was only noticed when data integrity issues within their core student enrolments databases started occurring.
    Source: ‘Navigating through the Cloud ‘; Rob Livingstone
    [ISBN 13: 978-146115285], Page xvii
  • 37. 5. Project Management implications
    f) Managing project boundary conditions
    • With the increasing availability of development APIs, as well as vendor ‘applications markets’, there are a large array of satellite applications written by third parties, the quality of which may be variable.
    • 38. The Salesforce App Exchange, Android Market and the Apple iStore are examples of such eco-systems.
    • 39. Some of these applications can be implemented by ends users, and extend the boundary of projects in an uncontrolled manner
    • 40. What project governance controls can be implemented to mitigate adverse consequences?
  • 5. Project Management implications
    g) Challenges for standard methodologies such as PRINCE2
    • The comprehensive use of rigorous, large scale project methodologies such as Prince2™ are often not appropriate for all but the largest of enterprise IT projects, although key elements are universally applicable to all projects.
    • 41. The interpretation and adaptation of the various large scale project methodologies to volatile ‘implement first and modify as you go’ environments needs some careful consideration
    • 42. This is likely to present a large challenge to organisations that are impatient to get results
  • 5. Project Management implications
    h) Use of cloud technologies BY project managers
    • No need to buy PM software – just use it for the life of the project
    • 43. One of the compelling value propositions in cloud computing is universal access, and the opportunity of lowering the barrier to entry for applications by using handheld applications using iPhone and Android devices, for example.
    • 44. This could have very positive implications for geographically distributed projects, where information sharing and timely updates of project activities and status’ are important to mobile project stakeholders
    • 45. Issues for consideration:
    • 46. Can you scale down to a single user at the end of the project?
    • 47. Can you ‘park’ your PM data and electronic artifacts that are stored in the cloud for later use if needed?
    • 48. What happens to the data if you leave the cloud? Can you extract it in a useful form?
  • 6. Cloud: Some key considerations for organisations:
    Security
    Privacy
    Cost
    Commercial, legal and jurisdictional
    Vendor contracts
    Regulatory
    Strong PM to counter opacity of Cloud offerings
    Governance: System change and version control
  • 49. 6. Cloud: Some key considerations for organisations:
    a) Security
    http://trust.cased.de/AMID
  • 50. 5. The key considerations for organisations:
    b) Privacy
  • 51. 5. The key considerations for organisations:
    b) Privacy
    http://www.rogerclarke.com/EC/CCC.html
  • 52. 6. Cloud: Some key considerations for organisations:
    c) Cost
    Know the TCO over the expected life-span of the system
    Do not exclude on-premises (Private Cloud, or traditional hosted) if these options exist
    Compare on like-for-like basis
    Illustrative example only
  • 53. 6. The key considerations for organisations:
    d) Commercial, legal and jurisdictional
    What are your key drivers behind the adoption of Cloud?
    • Drive innovation?
    • 54. Lower cost?
    • 55. Increase flexibility?
    Level of protection under the contract
    • Do the remedies for service outages make commercial sense?
    • 56. Have you read and understood your vendor contract
    What is the cost of seeking legal recourse?
    • If you provider’s contract is in an overseas legal jurisdiction, how practical will it be to seek damages?
  • 6. The key considerations for organisations:
    e) Vendor contracts
  • 57. 6. The key considerations for organisations:
    e) Vendor contracts
    What’s your Cloud contract duration?
    • If this is truly utility Cloud, why commit to a contract for a long period of time? 
    If marketed on ‘per user per month’ pay on that basis.
    • Some request annual pre-payment. You are then the vendor’s banker.
    Request a copy of the draft contract early
    • The procurement cycle can be time consuming for large projects.
    • 58. All that effort could be wasted if there is a major sticking point in the contract.
    • 59. Read your contract and understand what ie means!
    Global Cloud providers are reluctant to change standard contracts
    • Standardisation is the cornerstone of Cloud
    • 60. Some vendors will amend terms if you have large buying influence
  • 6. The key considerations for organisations:
    f) Regulatory
    The International Accounting Standards Board (IASB) and the US Financial Accounting Standards Board (FASB) Planned changes in reporting off-balance sheet leasing (2012-2013)
    • All leases, regardless of their terms, should be accounted for in a manner similar to how finance leases are treated today.
    • 61. Definition of annual software subscription as a lease?
    A spectrum of regulations and standards may apply to your organisation:
    • The Privacy Act 1988
    • 62. Corporations Act 2001
    • 63. Australian Standard AS ISO 15489 - Records Management
    • 64. Australian Prudential Regulation Authority
    • 65. … and more ….
  • 6. The key considerations for organisations:
    g) Strong PM to counter opacity over key aspects in the cloud
    • One of the fundamental benefits of public cloud is the removal of IT complexity.
    • 66. It’s invisible to the end user.
    • 67. Paradoxically, this presents those organisations concerned about IT security, risk and governance with a challenge because lack of visibility of what’s ‘under the covers’ may present unacceptable risks if fully disclosed and understood.
    • 68. Effective project management governance is critical to ensuring that these risks are surfaced for scrutiny and management.
    • 69. Know which questions to ask!
  • 6. The key considerations for organisations:
    h) Governance: System change and version Control
    You get to take what is given …..and maybe when it suits you ….
  • 70. 6. The key considerations for organisations:
    h) Governance: System change and version Control
    Modify / Test Interfaces
    V1.1
    Eg: V1.1 èV2.0
  • 71. 6. The key considerations for organisations:
    h) Governance: System change and version Control
    Scenario: Upgrading your Cloud ó’other system’ interfaces
    Usual practice to take a ‘point in time’ backup as a restore point before implementing the upgrade.
    • This is in the event of needing to fallback to the pre-upgrade point should the upgrade fail for whatever reason.
    If your Cloud provider cannot restore designated elements of, or your entire system, in an acceptable timeframe*, what can you do?
    • Core to effective governance of IT is change control and recovery processes
    (eg SOX Section 404 – General controls, to name but one).
    * - eg: Restore may be needed immediately. Some providers can take a few days
  • 72. 7. Cloud – The future is now
    Cloud technology, as with any other innovation, has the potential to do things cheaper, faster and better.
    This has significant implications for both CIOs, IT Departments and Project managers
    Cloud has the potential to be a real game changer for the astute
    Organisations need to deliberately define their strategy now:
    • Be an early adopter, or
    • 73. A fast follower, and leap-frog the early adopters be capitalising on their experiences
    To achieve the real benefits of Cloud technologies, understand:
    • the true cost
    • 74. the value
    • 75. the risk
    • 76. when to buy
    • 77. what to buy, and
    • 78. when to exit the technology and/or switch horses.
  • 8. Discussions and questions
    Rob Livingstone Advisory Pty Ltd
    ABN 41 146 643 165
    W1:www.rob-livingstone.com
    W2:www.navigatingthroughthecloud.com
    E:rob@rob-livingstone.com
    P: +61 2 8005 1972
    P: +1 609 843 0349
    M : +61 419 632 673
    F: +61 2 9879 5004
    rladvisory
    © All rights reserved. Unauthorised redistribution not without prior approval