Ten things you need to know about ALM (UNICOM webinar, Jan 2013)

366 views
278 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
366
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • “Without the business signing up for aggressive app rationalisation, IT can never do enough server virtualisation to significantly impact the budget. IT is just re-arranging the deck chairs on the Titanic if it does not engage the business on eliminating applications.”Forrester report Business execs increase direct IT spend to support systems of engagement
  • Ten things you need to know about ALM (UNICOM webinar, Jan 2013)

    1. 1. UNICOM ALM Webinar 25 January 2013 12 Ten things you need to know about Application Lifecycle Management Mark Smalley, IT Paradigmologist @marksmalley & mark.smalley@aslbislfoundation.org1 1
    2. 2. 2 2
    3. 3. Participants Where is home? 1. UK 2. Europe 3. Americas 4. Australasia 5. Rest of the world3 3
    4. 4. IT Paradigmologist Smalley.IT Happiness (%) Paradigmologist4 4
    5. 5. Oslo Bratislava Kuala Lumpur CopenhagenStockholm London Singapore MalmöMinneapolis / St Paul Bangkok Gold Coast Dallas 5
    6. 6. Topics ● Definitions ● Demand-supply ● Decommissioning ● Business IT alignment ● Hybrid landscapes ● Application strategy ● Economic significance ● Agile for maintenance ● Standards/frameworks ● Cloud computing & SaaS6 6
    7. 7. Definitions “When I use a word,” Humpty Dumpty said, in rather a scornful tone, “it means just what I choose it to mean – neither more nor less.”7 Lewis Carroll, Through the Looking Glass 7
    8. 8. Definitions ● Application ● Application Lifecycle ● Application Management ● Application Development ● Application Lifecycle Management8 8
    9. 9. People and things interact… Person Person Thing Thing9 9
    10. 10. …and have information systems… IS IS Person Person Thing Thing IS IS10 10
    11. 11. …that are connected IS IS Person Person Thing Thing IS IS11 11
    12. 12. Information systems comprise hardware, software and data… Information system DataPerson Application Software & Technical dataThings Infrastructure Hardware, Software & Technical data Facilities 12
    13. 13. ..with apps and devices as the user interface Information system Data DataPerson Appl Appl SW & SW & T. data T. dataThings Dev Infra HW, SW HW, SW & T. data & T. data Facilities 13
    14. 14. An application exists in several dimensions… Dimensions 1. Analytical: hardware, software, data, procedures, people, things 2. Informational: input, processing, storage, transport, output 3. Functional: … 4. Temporal: …14 14
    15. 15. …one of which is often troublesome to pin down Dimensions 3. Functional: „that which is served‟ “Information systems exist to serve, help or support people [and things] taking action in the real world, and it is a fundamental proposition that in order to conceptualize, and so create, a system which serves, it is first necessary to conceptualize that which is served, since the way the latter is thought of will dictate what would be necessary to serve or support it” Checkland and Holwell, 199815 15
    16. 16. Statement #1 An application is software that people and things use to support „something‟ in the real world16 16
    17. 17. Longevity of applications How long does an average application remain in use? 1. <1 year 2. 1-5 years 3. 5-10 years 4. 10-20 years 5. >20 years17 17
    18. 18. In the life of an application… Dimensions 4. Temporal: • identification • justification • realization • operation • evaluation 12 years “between 3 months and 30 years” • modification • decommissioning18 18
    19. 19. …the benefits start at the operation stage Dimensions 4. Temporal: • identification……… • justification………… • realization…………… • operation………………… • evaluation……………… • modification……………… • decommissioning…………………………………19 19
    20. 20. Statement #2 The application lifecycle starts with identification of needs and ends with decommissioning20 20
    21. 21. Economics of ALM What percentage of application lifecycle costs are spent after the initial development? 1. <20% 2. 20-40% 3. 40-60% 4. 60-80% 5. >80%21 21
    22. 22. 20% of the costs influence the other 80% Dimensions 4. Temporal: • identification • justification 20% • realization • operations • evaluation 80% • modification • decommissioning22 22
    23. 23. 80% is spent during ‘run’ but… Pre-run 20% Run 80%23 23
    24. 24. …what proportion of IT costs are application-related? Appl Infra Pre-run 20% Run 80%24 24
    25. 25. Economics of ALM What percentage of total IT costs are spent on applications? 1. <20% 2. 20-40% 3. 40-60% 4. 60-80% 5. >80%25 25
    26. 26. People say… 40% 60% Appl Infra Pre-run 20% AD Run 80% AM26 26
    27. 27. Statement #3 40% of IT costs are application related, 80% of which occur after initial development27 27
    28. 28. Small ALM & Big ALM ● ALM „just‟ refers to the activities for longer- term planning and policy-making ● ALM encompasses all application-related activities, starting with acquisition and development, and including longer-term planning and policy-making28 28
    29. 29. Your ALM? Which definition of ALM do you use? 1. Small (just longer-term plans and policy) 2. Big („everything‟) 3. Other (feel free to share your definition) 4. None29 29
    30. 30. Statement #4 „ALM‟ always refers to longer-term planning and policy-making and sometimes also to all other application-related activities30 30
    31. 31. ‘Full blown’ ALM as a black box Support Service level agreement • Operational support • Workarounds Run Service • Ensured availability &requests performance Change ALM Maintain (People, Knowledge, Process,requests Tooling, Partners) • Patches & Releases Projects Enhance • Releases Guide Applications • Recommendations • Strategic guidance Extra services • Support with Req & AT31 31
    32. 32. There’s no hard demarcation between AD & AM AD AM Initial development  Projects   Changes   Support 32 32
    33. 33. Statement #5 „Projects‟ are executed by both application development and application management33 33
    34. 34. Your ALM? Which generic term does your organisation use to refer to projects after the initial development? 1. Application development 2. Application management 3. Both 4. Other (feel free to share your terminology)34 34
    35. 35. Standard ISO 12207 Software Lifecycle Processes35 35
    36. 36. Multiple (potential) Supply- Acquisition relationships Enterprise External Internal Business Customer IT supplier IT dept dept Employee36 36
    37. 37. Statement #6 There are multiple demand-supply relationships and therefore multiple „occurrences‟ of ALM37 37
    38. 38. Position in the IT Foodchain Where do you work? (employed or contractor) 1. Business department 2. IT department 3. External IT service provider 4. Consultant / Trainer 5. Other Consultant Trainer Ext. Manuf. IT Bus. Customer IT serv IT comp. dept. dept. Citizen prov38 38
    39. 39. Business IT Alignment Degree to which IT (business asset) provides value ● Spending right time and money on IT? ● Time and money spent well? ● Decision-making: accountability1) & information ● Execution: competences & relationships 1) Power paradigm39 39
    40. 40. Statement #7 Business IT „Alignment‟ is still one of the most crucial but challenging areas40 40
    41. 41. 41 41
    42. 42. Top IT concerns What‟s your organization‟s highest IT priority? 1. Lowering cost of IT 2. Improving reliability of IT 3. Increasing speed of change of IT 4. Using IT to improve business efficiency 5. Using IT to improve business revenue42 42
    43. 43. Framework ASL 243 43
    44. 44. Framework ASL 2 44
    45. 45. Framework ASL 2 45
    46. 46. How to assess application quality ● Functional quality ● Importance of supported business processes ● Contribution to business processes ● Technical quality ● Maintainability ● Availability of technical knowledge ● Availability of application knowledge ● Ease of maintenance ● Operationability ● Reliability (outages) ● Efficiency (resources) ● Continuity (security, distaster recovery) ● Manageability (monitoring)46 46
    47. 47. Application Lifecycle Management47 47
    48. 48. Assessment application quality A Low – Functional Quality - High B Replace Renew C D E F Retire Reassess G H Low - Technical Quality - High48 48
    49. 49. There are various ways to extend the life of an application Source: CapgeminiSustain Re-platform Replace RemediateConsolidate Extend/enhance Migrate Decommission49
    50. 50. Statement #8 Application decommissioning and other forms of rationalization are more challenging than development50 50
    51. 51. Get a grip on your application landscape● Are your applications a heavy-duty trains or light-weight scooters?● Do you have appropriate policies, processes and practices for each category?● The application landscape is and will remain hybrid● So build your new city within the old citySource: Capgemini 51
    52. 52. Statement #9 Hybrid application landscapes need differentiated approaches52 52
    53. 53. Statement #10 Determining application strategy is more about people than process53 53
    54. 54. Agile ● A group of software development methods ● based on iterative and incremental development, ● where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams ● It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change Source: wikipedia54 54
    55. 55. Agile55 Source: www.digdes.com 55
    56. 56. Agile is attractive... ● Quicker time to market because functionality and therefore business value is delivered earlier in short iterations (20% quicker) ● Lower IT costs because knowledge is retained in permanent teams (5-10% lower costs) ● Less frustration in working with IT because of closely collaborative approach (250% more first time right) ● Lower risk of IT disruptions to business processes because of better collaboration between apps and ops (80% more productivity)56 56
    57. 57. …also for maintenance if… ● Software quality is enforced, ensuring maintainability and good documentation ● Financial risks are mitigated by focusing on business value, not just fixed price per individual change or release ● Deployment us speeded up by using automated testing and Lean ● Agile ALM teams are equipped to deal with urgent problems, avoiding costly separate teams ● Complex retrofits across multiple teams are57 coordinated / synchronized 57
    58. 58. Statement #11 „Agile‟ can also be applied to maintenance but specific concerns need to be addressed58 58
    59. 59. Cloud computing & SaaS • Technology tends to standardize and commoditize • IT Service Providers have to constantly create more value for the business Cloud Computing • shifts ownership and location of assets and staffing • to a specialized third party • who provides benefits • that are closely associated with • economies of scale and standardization59
    60. 60. An I afford the benefits? • • Living with a standard solution Indirect control of provider SaaS • External data storage • Interfaces with other apps • Continuity & retransitioning • Intelligent integrator capabilities60
    61. 61. Significant capability shift ● High-level (architectural) comprehension of applications and in particular the interaction between applications ● Ability to interact with third parties using „communicate & collaborate‟ and „agree & adapt‟ ● Willingness and ability to live in a hybrid world ● Ability to adapt to using standard components and refrain from non-differentiating customization ● External orientation and a conviction that „not invented here‟ gives you an advantage ● Out-of-the-box ability to see creative combinations of services that generate business benefits61
    62. 62. Cloud computing as a medicine ● Relieves pain associated with speed of business change, changeable demand and limited capital ● Can cause serious headaches and stomach trouble if not prepared to conform to the standard62
    63. 63. Statement #12 Management of SaaS from a customer point of view requires a significant investment in competences63 63
    64. 64. Join us in London on 28th Feb Session 1 (Introduction): ● Current state in Application Development and Lifecycle Management ● Define and identify core lifecycle functions Session 2 (Applications methods): ● Enterprise Web 2.0 and strategies for web based collaboration ● Cloud computing ● Mobile application development and lifecycle ● Application rationalisation Session 3 (Business issues): ● Using ALM to improve productivity and reduce administration ● Ways to build and adapt applications that support new business initiatives ● How to coordinate an organisation‟s Application Delivery Process Session 4 (Tool applications): ● Agile Project Management and Test Management ● Agile methodologies – their impact on ALM ● How development can be improved by new processes and methods to support ALM solutions64
    65. 65. Recap – Q&A 1. An application is software that 6. There are multiple demand-supply people and things use to support relationships and therefore multiple „something‟ in the real world „occurrences‟ of ALM 2. The application lifecycle starts with 7. Business IT „Alignment‟ is a crucial identification of needs and ends with but most challenging area decommissioning 8. Application decommissioning and 3. 40% of IT costs are application other forms of rationalization are related, 80% of which occur after more challenging than development initial development 9. Hybrid application landscapes need 4. „ALM‟ always refers to longer-term differentiated approaches planning and policy-making and 10.Determining application strategy is sometimes also to all other more about people than process application-related activities 11.„Agile‟ can also be applied to 5. „Projects‟ are executed by both maintenance but specific concerns application development and need to be addressed application management 12.Management of SaaS from a customer point of view requires65 investment in competences 65
    66. 66. Please connect and keep in touch!mark.smalley@aslbislfoundation.org www.linkedin.com/in/marksmalley marksmalley @ Twitter Smalley.IT www.aslbislfoundation.org Free downloads Newsletter 66

    ×