Rapid Deployment of BMC Remedy Solutions 2006

1,872 views

Published on

A discussion of how rapid application development (RAD) development techniques may be used for the deployment of Remedy solutions. Presented at BMC User World 2006

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,872
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
11
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Rapid Deployment of BMC Remedy Solutions 2006

  1. 1. 8/28/2009<br />Rapid Deployment of BMC Remedy Solutions <br />Antonio Rolle<br />VP of Professional Services<br />generationE Technologies<br />
  2. 2. 8/28/2009<br />©2006 BMC Software<br />2<br />Agenda<br />Issues Affecting BMC Remedy Deployments<br />A Case for a Rapid Deployment Methodology<br />The generationE BMC Remedy Rapid Deployment Methodology<br />Case Study Review<br />
  3. 3. 8/28/2009<br />©2006 BMC Software<br />3<br />Agenda<br />Issues Affecting BMC Remedy Deployments<br />A Case for a Rapid Deployment Methodology<br />The generationE BMC Remedy Rapid Deployment Methodology<br />Case Study Review<br />
  4. 4. 8/28/2009<br />©2006 BMC Software<br />4<br />Issues Affecting BMC Remedy Deployments<br />Developer Productivity (Backlogs)<br />Skills Shortage<br />Time to Market<br />Complexity<br />Momentum<br />
  5. 5. 8/28/2009<br />©2006 BMC Software<br />5<br />Agenda<br />generationE Technologies Overview<br />Issues Affecting BMC Remedy Deployments<br />A Case for a Rapid Deployment Methodology<br />The generationE BMC Remedy Rapid Deployment Methodology<br />Case Study Review<br />
  6. 6. 8/28/2009<br />©2006 BMC Software<br />6<br />What is Rapid Application Development?<br />“Rapid Application Development (RAD) is a development lifecycle designed to give much faster development and higher-quality results than those achieved with the traditional lifecycle. It is designed to take the maximum advantage of powerful development software that has evolved recently.” <br />- James Martin Information Engineering: Introduction. Prentice Hall, 1991 <br />
  7. 7. 8/28/2009<br />©2006 BMC Software<br />7<br />What is Rapid Application Development?<br />RAD is a methodology for compressing the analysis, design, build and test phases into a series of short, iterative development cycles. RAD proposes that products can be developed faster and of higher quality by: <br />Using workshops or focus groups to gather requirements <br />Prototyping and user testing of designs <br />Re-using software components<br />Following a schedule that defers design improvements to the next product version<br />Keeping review meetings and other team communication informal <br />
  8. 8. 8/28/2009<br />©2006 BMC Software<br />8<br />RAD – Goals & Properties<br />Bring together the power of IT<br />Help to deliver on the promise of ‘Activate the Business’<br />Manage the future<br />Place emphasis on user involvement and responsibility throughout the development<br />Properties<br />Specification is fluid<br />Must be delivered in 2 - 6 months <br />Split into increments if necessary <br />Each increment is implemented separately with frequent delivery of working parts of system.<br />
  9. 9. 8/28/2009<br />©2006 BMC Software<br />9<br />A Case for a BMC Remedy Rapid Deployment Methodology<br />Time to Adoption<br />Time to Market<br />Cost (Vilfredo Pareto’s 80/20 Rule)<br />Leveraging “out of the box” functionality<br />Extensibility<br />Partner Commitment<br />
  10. 10. 8/28/2009<br />©2006 BMC Software<br />10<br />A Case Against RAD…<br />PROJECT SCOPE<br />Broad scope where the business objectives are obscure or broad<br />PROJECT DECISIONS<br />Many people must be involved in the decisions on the project, the decision makers are not available on a timely basis or they are geographically dispersed<br />PROJECT TEAM<br />The project team is large, or there are multiple teams whose work needs to be coordinated<br />
  11. 11. 8/28/2009<br />©2006 BMC Software<br />11<br />Agenda<br />generationE Technologies Overview<br />Issues Affecting BMC Remedy Deployments<br />A Case for a Rapid Deployment Methodology<br />The generationE BMC Remedy Rapid Deployment Methodology<br />Case Study Review<br />
  12. 12. 8/28/2009<br />©2006 BMC Software<br />12<br />Traditional Development Cycle<br />Planning<br />Analysis<br />Design<br />Build<br />Test<br />Deploy<br />
  13. 13. 8/28/2009<br />©2006 BMC Software<br />13<br />Traditional Development Cycle<br /><ul><li>Although quality and speed of delivery are paramount, this does not mean what is good in traditional system development is thrown away. There must be:</li></ul>Effective project management<br />Appropriate & Current Documentation <br />Requirements Specifications<br />Appropriate Maintainability<br />Testing <br />Quality Assurance<br />Designs<br />Reuse<br />
  14. 14. 8/28/2009<br />©2006 BMC Software<br />14<br />RAD Core Elements<br />Prototyping<br />Iterative development<br />Time boxing<br />Team members<br />Management approach<br />RAD tools<br />
  15. 15. 8/28/2009<br />©2006 BMC Software<br />15<br />RAD Core Elements: Prototyping<br />The construction of a feature-light, reduced-scalability application in a short amount of time. The objective is to create a working application to help a user flesh out requirements.<br />The characteristics of prototyping can be summarized as:<br />Involves versions of part of a software system<br />Evaluation is done in collaboration with users to optimize quality<br />A joint learning process between users and developers<br />Facilitation of the discovery of errors (testing) <br />
  16. 16. 8/28/2009<br />©2006 BMC Software<br />16<br />RAD Core Elements: Interactive Development<br />The creation of increasingly feature-rich versions of applications in short development cycles, where each release produces user requirements that feed the next release<br />Involves splitting projects into smaller mini-projects<br />Requires initial research and analysis of the project as whole<br />Increments are self-contained systems, which are<br />developed<br />documented <br />delivered<br />Each increment typically involves iterative development and prototyping<br />
  17. 17. 8/28/2009<br />©2006 BMC Software<br />17<br />RAD Core Elements: Time Boxing<br />Supports iterative development by pushing off features to future versions in order to complete iterative cycles as quickly as possible. Time boxing is extremely important to help reduce scope creep, but it requires watchful and involved management.<br />
  18. 18. 8/28/2009<br />©2006 BMC Software<br />18<br />RAD Core Elements: Team Members<br />Teams should be small and should consist of experienced, versatile, and motivated members that are able to perform multiple roles. These roles consist of:<br />User<br />Good inter‑personal skills<br />Personal confidence<br />A non‑parochial view<br />Representative of the user community<br />Developer<br />Patience, diplomacy, perception, acceptability, objectivity, non‑ intimidating <br />Good communication skills, patience, interpersonal skills, empathy with user <br />Accepts criticism humbly<br />Project Manager<br />Open minded, prepared to be flexible, and dynamic<br />Possess excellent leadership skills<br />
  19. 19. 8/28/2009<br />©2006 BMC Software<br />19<br />RAD Core Elements: Management Approach<br />Specifies that management should be very involved in keeping development cycles short and enforcing deadlines. Furthermore management should help keep high team motivation, and should focus on clearing bureaucratic or political obstacles.<br />
  20. 20. 8/28/2009<br />©2006 BMC Software<br />20<br />RAD Core Elements: RAD Tools<br />Specifies that development speed is more important than cost of tools and so the latest technologies should be used to increase development speed<br />
  21. 21. 8/28/2009<br />©2006 BMC Software<br />21<br />BMC Remedy RAD Processes<br />Pre-Project Activities<br />Requirements Planning<br />User Design<br />Construction<br />Implementation<br />Post-Project Activities<br />
  22. 22. 8/28/2009<br />©2006 BMC Software<br />22<br />BMC Remedy RAD Processes: Pre-Project Activities<br />Develop Project Management Plan<br />Identify Risks and Mitigation Strategies<br />Define the Development Schedule<br />Identify Milestones and Deliverables<br />Identify Desired End Results<br />Identify Project Constraints<br />Identify Financial Considerations<br />
  23. 23. 8/28/2009<br />©2006 BMC Software<br />23<br />BMC Remedy RAD Processes: Requirements Planning<br />Activities<br />Research the Current Situation<br />Gather Requirements and Perform Quick Design <br />Build Prototype (Basic Interface, Demo System, Proof-of-Concept)<br />Review Prototype<br />Refine Prototype & Design Specifications<br />Deliverables<br />Design Specifications<br />Prototype<br />
  24. 24. 8/28/2009<br />©2006 BMC Software<br />24<br />BMC Remedy RAD Processes: User Design<br />Activities<br />Produce Detailed Design Document<br />Prepare Implementation Strategy<br />Obtain Approval for Construction<br />Deliverables<br />Detailed Design Document<br />Sign Off for Construction<br />Develop Outline <br />System Design<br />Refine System Design<br />Prepare Implementation <br />Strategy<br />Finalize System<br />Design<br />Obtain Approval<br />
  25. 25. 8/28/2009<br />©2006 BMC Software<br />25<br />BMC Remedy RAD Processes: Construction<br />Activates<br />Develop Unit Test Plan&apos;s)<br />System Construction<br />Generate BMC Remedy Test Data<br />Generate System Documents<br />System Testing<br />Deliverables<br />Unit Test Plan&apos;s)<br />System Test Plan<br />Tested Units<br />System Documentation<br />Developed System<br />Prepare for Construction<br />Construct System<br />Generate Test Data <br />& Documentation<br />Prepare for <br />Transition<br />Verify System <br />Construction<br />
  26. 26. 8/28/2009<br />©2006 BMC Software<br />26<br /> What is Meant by “Out-of-the-box”?<br />Industry Standards/Best Practices<br />ITIL, Six Sigma, BS 15000, ISO 9000<br />Plus 13,000 pieces of pre-configured workflow<br />Customer Requested Functionality<br />More than 10 years of industry experience and over 10,000 customers using Remedy<br />Market-Leading Innovations<br />Remedy recognized as the Thought Leader within the IT Service Management market<br />
  27. 27. 8/28/2009<br />©2006 BMC Software<br />27<br />IT Service Management Solutions from BMC Remedy<br />Built in best practices, combined with high adaptability, allow customers to rapidly achieve value, improve operational efficiency and continue to optimize to their unique needs<br />Solutions that fit any size business – around the corner and around the world<br />Automate internal business-related IT service and support processes<br />Best practices, like Information Technology Infrastructure Library (ITIL), are built-in, leading to faster time-to-value<br />Easily adapted to optimize to customers unique needs<br />
  28. 28. 8/28/2009<br />©2006 BMC Software<br />28<br />BMC Remedy RAD Processes: Implementation<br />Activates<br />Production Install<br />Data Migration<br />Train Users<br />Perform Acceptance Testing<br />Deliverables<br />Acceptance Testing Document<br />User Training Documents<br />Accepted Business System<br />Install Production<br />System<br />Perform Data Migration<br />Conduct User <br />Training<br />Acceptance Testing<br />
  29. 29. 8/28/2009<br />©2006 BMC Software<br />29<br />BMC Remedy RAD Processes: Post- Project Activities<br />Activities<br />Review & Document Project Metrics<br />Organize and Store Project Assets<br />Prepare Lessons Learned Document<br />Deliverables<br />Document Store<br />Lessons Learned Document<br />
  30. 30. 8/28/2009<br />©2006 BMC Software<br />30<br />Agenda<br />generationE Technologies Overview<br />Issues Affecting BMC Remedy Deployments<br />A Case for a Rapid Deployment Methodology<br />The generationE BMC Remedy Rapid Deployment Methodology<br />Case Study Review<br />
  31. 31. 8/28/2009<br />©2006 BMC Software<br />31<br />Case Study<br />“There are only two things of importance. One is the customer, and the other is the product. If you take care of customers, they come back. If you take care of the product, it doesn’t come back. It’s just that simple. And it’s just that difficult.”<br />– Stanley Marcus, Neiman Marcus<br />
  32. 32. 8/28/2009<br />©2006 BMC Software<br />32<br />Case Study<br />Business Profile:<br />IT infrastructure and managed services company that provides 24x7 availability for their hosted business applications, as well as disaster recovery and co-location services. <br />Existing BMC Remedy v5 solution acquired via acquisition<br />Organizational changes and business requirements not mapped to existing BMC Remedy workflow<br />Management requirements to quickly deploy the solution<br />Software Solutions:<br />BMC® Configuration Manager<br />BMC® Remedy® Asset Management Application<br />BMC® Remedy® Service Desk<br />BMC® Remedy® Service Level Management<br />BMC® Remedy ® Enterprise Integration Engine<br />
  33. 33. 8/28/2009<br />©2006 BMC Software<br />33<br />Case Study: Prototyping<br />Standard Incident & Problem templates<br />
  34. 34. 8/28/2009<br />©2006 BMC Software<br />34<br />Case Study: Interactive Development & Time Boxing<br />Leverage BMC Remedy “Out of the Box” features<br />Split project in multiple phases<br />Mapping of business requirements to ITIL best practices and BMC Remedy work flow<br />Vilfred Pareto’s 80/20 Rule for each phase<br />Strict project management procedures<br />
  35. 35. 8/28/2009<br />©2006 BMC Software<br />35<br />Case Study: Team Members & Management Approach<br />Team managed by business objectives<br />Focus on team contribution<br />Individuals co-operate<br />Deliver the best business solution<br />Developments work along side users<br />Doubtful business functions were excluded<br />Quality is measured against business benefit<br />
  36. 36. 8/28/2009<br />©2006 BMC Software<br />36<br />Case Study: Lessons Learned<br />Prototype meetings were key to success<br />Motivated users can lead to excellent systems<br />Uncritical users will lead to systems failing<br />Communication can be markedly improved<br />Incremental delivery motivates users<br />Documentation need not be a problem<br />Boundaries will shift<br />Control and estimation is difficult<br />Short delivery times can irritate developers<br />
  37. 37. 8/28/2009<br />©2006 BMC Software<br />37<br />Other Methodologies<br />XP methodology<br />breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete<br />Agile methodology<br />A form of XP, aims for customer satisfaction through early and continuous delivery of useful software components<br />Agile is similar to XP but with less focus on team coding and more on limiting project scope<br />An agile project sets a minimum number of requirements and turns them into a deliverable product<br />

×