VSTS & Application Lifecycle Management

2,480 views

Published on

Application Lifecycle Management with TFS part 1

Published in: Technology, Business
0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,480
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
0
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide

VSTS & Application Lifecycle Management

  1. 1. Application Lifecycle Management with Team Foundation Server<br />enrico.antonacci@exsertus.be<br />Technical Architect<br />Exsertus <br />
  2. 2. Application Lifecycle Management<br />The process an organization can use for an application or software system from its conception to its retirement.<br />
  3. 3. Application Lifecycle Management<br />ALM is the glue that ties the development processes together and defines the efforts necessary to coordinate the process.<br />
  4. 4. Why do we develop Business Software and Systems<br />?<br />
  5. 5. Cool Technology<br />ASP .NET SilverLight MVC AJAX WPF Adobe AIR WCF WF XML Sharepoint<br />
  6. 6. Clever ways of solving technical & logical problems<br />
  7. 7. And the Business Value<br />?<br />
  8. 8. Business Requirements+ Business Needs<br />Business Value<br />
  9. 9. Application Lifecycle Management<br />The process that can help us deliver the<br />Business Value<br />
  10. 10. Why do we develop Business Software and Systems<br />?<br />
  11. 11. We do not write software for an enterprise to fulfill out technological wishes alone, we write it to make the business run smoother and create more value !!!<br />
  12. 12. Business Value<br />Business Needs<br />Software Development <br />Lifecycle<br />
  13. 13. 3<br />Cornerstones of Business<br />
  14. 14. Muscle = Process<br />
  15. 15. Brain = Business Rules<br />
  16. 16. Spine = Information<br />
  17. 17. Business Environment<br />
  18. 18. Competition from everywhere<br />
  19. 19.
  20. 20.
  21. 21. Deploy new Build Server<br />Budgetting for 2010<br />Investigate TDD<br />Plan lunch with Microsoft<br />Integrate with Build Server<br />? Control our ALM Process <br />
  22. 22. Forcing businesses to become more Agile, ready to gain competitve advantages<br />
  23. 23. Affecting the way we must architect and write business systems!<br />
  24. 24. Deploy new Build Server<br />Budgetting for 2010<br />Investigate TDD<br />Plan lunch with Microsoft<br />Integrate with Build Server<br />? Control our ALM Process <br />
  25. 25. Business Environment<br />
  26. 26. Business Processes can change rapidly<br />Supporting IT Systems must also be ready for quick changes<br />Visual Studio Team System<br />
  27. 27. ALM Tool<br />Without an effective development process tied closely to the business side and supported by a set of tools, we will run into problems!<br />Not only the ALM tools that are important, we need to consider the whole ALM process<br />
  28. 28. Project Health<br />Scope<br />Budget<br />Quality<br />Time<br />
  29. 29. Time<br />
  30. 30. Budget<br />
  31. 31. Scope<br />
  32. 32. Factors influencing <br />Project Success<br />
  33. 33. Business<br />Technology<br />
  34. 34. Process<br />“Cowboy”<br />Time<br />
  35. 35. Communication<br />
  36. 36. Other influencing Factors<br />Synchronization of Tools<br />Resource Management<br />Project Size<br />
  37. 37. 35%<br />Projects Succeed!<br />
  38. 38. Control our ALM Process<br />Deploy new Build Server<br />Budgetting for 2010<br />Investigate TDD<br />Plan lunch with Microsoft<br />Integrate with Build Server<br />
  39. 39. Deliver better <br />Projects<br />
  40. 40. This overall ALM process comesa mindset focused on the application from its birth as a business need to the delivered Business Value.<br />
  41. 41. An overall ALM process can help us control the project outcome better in the end, enabling us to deliver true Business Value<br />
  42. 42. Project Health<br />
  43. 43. IT Budget spending<br />CEB Corporate Executive Board 2006<br />
  44. 44. Control our ALM Process<br />Deploy new Build Server<br />Budgetting for 2010<br />Investigate TDD<br />Plan lunch with Microsoft<br />Integrate with Build Server<br />
  45. 45. Factors influencing IT spending<br />Small Changes and Fixes<br />Retirement of an Application<br />Inflexible Application Architecture<br />Infrastructure<br />Immature / No Operations Process <br />
  46. 46. ALM Roles<br />Change Request or New Release<br />Business <br />Needs<br />Business Value<br />Portofolio<br />Software<br />Development<br />Lifecycle<br />Operations<br />Retirement <br />of<br />System<br />
  47. 47. Application Lifecycle Management<br />ALM is the glue that ties all the roles and the activities they perform together<br />
  48. 48. ALM Roles<br />Business Manager<br />Project Manager<br />PMO Decision Maker<br />Business Analyst<br />Developers<br />Testers<br />Operations Staff<br />Architect<br />User Experience Team<br />Database Administrators<br />
  49. 49. 4<br />ALM views<br />
  50. 50. Software Development Lifecycle View<br />
  51. 51. ALM in SDLC<br />Enforcement of processes that span all the activities<br />Traceability<br />Reporting<br />
  52. 52. Application Lifecycle Management<br />ALM does not support a specific activity itself. Its purpose is to keep all activities in sync.<br />
  53. 53. Service Management View<br />ITIL<br />Application Development Phases<br />Service Management Phases<br />
  54. 54. ALM in Service Management<br />ALM focuses on the activities that are involved <br />with deployment, operation, support and <br />optimization of the application<br />
  55. 55. Application Portfolio View<br />Business Plan<br />The Product <br />Lifecycle<br />Operations<br />Product<br />Idea<br />Divestment<br />The Project <br />Lifecycle<br />The PMI view of ALM<br />
  56. 56. Unified or CIO View<br />Operations<br />SDLC <br />APM<br />
  57. 57. Unified or CIO View<br />Change Request or New Release<br />Business <br />Needs<br />Business Value<br />Portofolio<br />Software<br />Development<br />Lifecycle<br />Operations<br />Retirement <br />of<br />System<br />
  58. 58. 3<br />Pillars of ALM<br />
  59. 59. Change Request or New Release<br />Business <br />Needs<br />Business Value<br />Portofolio<br />Software<br />Development<br />Lifecycle<br />Operations<br />Retirement <br />of<br />System<br />Traceability<br />Process Automation<br />Visibility<br />
  60. 60. Traceability<br />
  61. 61. Process <br />Automation<br />
  62. 62. Visibility<br />
  63. 63. 1.0<br />ALM<br />
  64. 64. Requirements<br />Test<br />Build<br />Development<br />Design<br />
  65. 65. 2.0<br />ALM<br />
  66. 66. “The ‘emerging’ ALM is a platform for coordination and management of development activities, not a collection of lifecycle tools with locked-in and limited ALM features”<br />- Forrester -<br />
  67. 67.
  68. 68. Characteristics in ALM 2.0<br />Practitioner tools assembled out of plug-ins<br />Common services available across practitioner tools<br />Repository neutral<br />Use of open integration standards<br />Process support<br />

×