Remedy rapid deployment 1
-
Upload
anand-raj -
Category
Technology
-
view
549 -
download
1
description
Transcript of Remedy rapid deployment 1
04/09/23
Rapid Deployment of BMC Remedy Solutions
Antonio RolleVP of Professional ServicesgenerationE Technologies
04/09/23 ©2006 BMC Software2
Agenda
› Issues Affecting BMC Remedy Deployments› A Case for a Rapid Deployment Methodology› The generationE BMC Remedy Rapid Deployment Methodology› Case Study Review
04/09/23 ©2006 BMC Software3
Agenda
› Issues Affecting BMC Remedy Deployments› A Case for a Rapid Deployment Methodology› The generationE BMC Remedy Rapid Deployment Methodology› Case Study Review
04/09/23 ©2006 BMC Software4
Issues Affecting BMC Remedy Deployments
› Developer Productivity (Backlogs)› Skills Shortage› Time to Market› Complexity› Momentum
04/09/23 ©2006 BMC Software5
Agenda
› generationE Technologies Overview› Issues Affecting BMC Remedy Deployments› A Case for a Rapid Deployment Methodology› The generationE BMC Remedy Rapid Deployment Methodology› Case Study Review
04/09/23 ©2006 BMC Software6
What is Rapid Application Development?
“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.”
- James Martin Information Engineering: Introduction. Prentice Hall, 1991
04/09/23 ©2006 BMC Software7
What is Rapid Application Development?
› 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:
– Using workshops or focus groups to gather requirements – Prototyping and user testing of designs – Re-using software components– Following a schedule that defers design improvements to the next product
version– Keeping review meetings and other team communication informal
04/09/23 ©2006 BMC Software8
RAD – Goals & Properties
› Bring together the power of IT› Help to deliver on the promise of ‘Activate the Business’› Manage the future› Place emphasis on user involvement and responsibility throughout
the development› Properties
– Specification is fluid– Must be delivered in 2 - 6 months – Split into increments if necessary – Each increment is implemented separately with frequent delivery of working
parts of system.
04/09/23 ©2006 BMC Software9
A Case for a BMC Remedy Rapid Deployment Methodology
› Time to Adoption› Time to Market› Cost (Vilfredo Pareto’s 80/20 Rule)› Leveraging “out of the box” functionality› Extensibility› Partner Commitment
04/09/23 ©2006 BMC Software10
A Case Against RAD…
PROJECT SCOPE› Broad scope where the business objectives are obscure or broad
PROJECT DECISIONS› 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
PROJECT TEAM› The project team is large, or there are multiple teams whose work
needs to be coordinated
04/09/23 ©2006 BMC Software11
Agenda
› generationE Technologies Overview› Issues Affecting BMC Remedy Deployments› A Case for a Rapid Deployment Methodology› The generationE BMC Remedy Rapid Deployment Methodology› Case Study Review
04/09/23 ©2006 BMC Software12
Traditional Development Cycle
› Planning› Analysis› Design› Build› Test› Deploy
04/09/23 ©2006 BMC Software13
Traditional Development Cycle
– Effective project management– Appropriate & Current
Documentation – Requirements Specifications– Appropriate Maintainability
– Testing– Quality Assurance– Designs– Reuse
› 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:
04/09/23 ©2006 BMC Software14
RAD Core Elements
› Prototyping› Iterative development› Time boxing› Team members› Management approach› RAD tools
04/09/23 ©2006 BMC Software15
RAD Core Elements: Prototyping
› 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.
› The characteristics of prototyping can be summarized as:– Involves versions of part of a software system– Evaluation is done in collaboration with users to optimize quality– A joint learning process between users and developers– Facilitation of the discovery of errors (testing)
04/09/23 ©2006 BMC Software16
RAD Core Elements: Interactive Development
› The creation of increasingly feature-rich versions of applications in short development cycles, where each release produces user requirements that feed the next release
› Involves splitting projects into smaller mini-projects› Requires initial research and analysis of the project as whole› Increments are self-contained systems, which are
– developed– documented – delivered
› Each increment typically involves iterative development and prototyping
04/09/23 ©2006 BMC Software17
RAD Core Elements: Time Boxing
› 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.
04/09/23 ©2006 BMC Software18
RAD Core Elements: Team Members
› Teams should be small and should consist of experienced, versatile, and motivated members that are able to perform multiple roles. These roles consist of:
– User• Good inter‑personal skills• Personal confidence• A non‑parochial view• Representative of the user community
– Developer• Patience, diplomacy, perception, acceptability, objectivity, non‑ intimidating • Good communication skills, patience, interpersonal skills, empathy with user • Accepts criticism humbly
– Project Manager• Open minded, prepared to be flexible, and dynamic• Possess excellent leadership skills
04/09/23 ©2006 BMC Software19
RAD Core Elements: Management Approach
› 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.
04/09/23 ©2006 BMC Software20
RAD Core Elements: RAD Tools
› Specifies that development speed is more important than cost of tools and so the latest technologies should be used to increase development speed
04/09/23 ©2006 BMC Software21
BMC Remedy RAD Processes
› Pre-Project Activities› Requirements Planning› User Design› Construction› Implementation› Post-Project Activities
04/09/23 ©2006 BMC Software22
BMC Remedy RAD Processes: Pre-Project Activities
› Develop Project Management Plan› Identify Risks and Mitigation Strategies› Define the Development Schedule› Identify Milestones and Deliverables› Identify Desired End Results› Identify Project Constraints› Identify Financial Considerations
04/09/23 ©2006 BMC Software23
BMC Remedy RAD Processes: Requirements Planning
› Activities– Research the Current Situation– Gather Requirements and Perform Quick Design – Build Prototype (Basic Interface, Demo System, Proof-of-Concept)– Review Prototype– Refine Prototype & Design Specifications
› Deliverables– Design Specifications– Prototype
04/09/23 ©2006 BMC Software24
BMC Remedy RAD Processes: User Design
› Activities– Produce Detailed Design Document– Prepare Implementation Strategy– Obtain Approval for Construction
› Deliverables– Detailed Design Document– Sign Off for Construction
Develop Outline System Design
Develop Outline System Design
Refine System DesignRefine System Design Prepare Implementation Strategy
Prepare Implementation Strategy
Obtain ApprovalObtain Approval
Finalize SystemDesign
Finalize SystemDesign
04/09/23 ©2006 BMC Software25
BMC Remedy RAD Processes: Construction
› Activates– Develop Unit Test Plan's)– System Construction– Generate BMC Remedy Test Data– Generate System Documents– System Testing
› Deliverables– Unit Test Plan's)– System Test Plan– Tested Units– System Documentation– Developed System
Prepare for ConstructionPrepare for Construction
Construct SystemConstruct System Generate Test Data & Documentation
Generate Test Data & Documentation
Prepare for Transition
Prepare for Transition
Verify System Construction
Verify System Construction
04/09/23 ©2006 BMC Software26
What is Meant by “Out-of-the-box”?
Industry Standards/Best PracticesITIL, Six Sigma, BS 15000, ISO 9000
Plus 13,000 pieces of pre-configured workflow
Customer Requested FunctionalityMore than 10 years of industry experience and over 10,000 customers using Remedy
Market-Leading InnovationsRemedy recognized as the Thought Leader within the IT Service Management market
04/09/23 ©2006 BMC Software27
IT Service Management Solutions from BMC Remedy
› 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
– Solutions that fit any size business – around the corner and around the world
– Automate internal business-related IT service and support processes
– Best practices, like Information Technology Infrastructure Library (ITIL), are built-in, leading to faster time-to-value
– Easily adapted to optimize to customers unique needs
04/09/23 ©2006 BMC Software28
BMC Remedy RAD Processes: Implementation
› Activates– Production Install– Data Migration– Train Users– Perform Acceptance Testing
› Deliverables– Acceptance Testing Document– User Training Documents– Accepted Business System
Install ProductionSystem
Install ProductionSystem Perform Data MigrationPerform Data Migration Conduct User
Training
Conduct User Training
Acceptance TestingAcceptance Testing
04/09/23 ©2006 BMC Software29
BMC Remedy RAD Processes: Post- Project Activities
› Activities– Review & Document Project Metrics– Organize and Store Project Assets– Prepare Lessons Learned Document
› Deliverables– Document Store– Lessons Learned Document
04/09/23 ©2006 BMC Software30
Agenda
› generationE Technologies Overview› Issues Affecting BMC Remedy Deployments› A Case for a Rapid Deployment Methodology› The generationE BMC Remedy Rapid Deployment Methodology› Case Study Review
04/09/23 ©2006 BMC Software31
Case Study
“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.”
– Stanley Marcus, Neiman Marcus
04/09/23 ©2006 BMC Software32
Case Study
› Business Profile:– IT infrastructure and managed services company that provides 24x7 availability for
their hosted business applications, as well as disaster recovery and co-location services.
– Existing BMC Remedy v5 solution acquired via acquisition– Organizational changes and business requirements not mapped to existing BMC
Remedy workflow– Management requirements to quickly deploy the solution
› Software Solutions:– BMC® Configuration Manager– BMC® Remedy® Asset Management Application– BMC® Remedy® Service Desk– BMC® Remedy® Service Level Management– BMC® Remedy ® Enterprise Integration Engine
04/09/23 ©2006 BMC Software33
Case Study: Prototyping
› Standard Incident & Problem templates
04/09/23 ©2006 BMC Software34
Case Study: Interactive Development & Time Boxing
› Leverage BMC Remedy “Out of the Box” features› Split project in multiple phases› Mapping of business requirements to ITIL best practices and BMC
Remedy work flow› Vilfred Pareto’s 80/20 Rule for each phase› Strict project management procedures
04/09/23 ©2006 BMC Software35
Case Study: Team Members & Management Approach
› Team managed by business objectives› Focus on team contribution› Individuals co-operate› Deliver the best business solution› Developments work along side users› Doubtful business functions were excluded› Quality is measured against business benefit
04/09/23 ©2006 BMC Software36
Case Study: Lessons Learned
› Prototype meetings were key to success
› Motivated users can lead to excellent systems
› Uncritical users will lead to systems failing
› Communication can be markedly improved
› Incremental delivery motivates users
› Documentation need not be a problem
› Boundaries will shift
› Control and estimation is difficult
› Short delivery times can irritate developers
04/09/23 ©2006 BMC Software37
Other Methodologies
› XP methodology– breaks a project into tiny phases, and developers cannot continue on
to the next phase until the first phase is complete
› Agile methodology– A form of XP, aims for customer satisfaction through early and
continuous delivery of useful software components– Agile is similar to XP but with less focus on team coding and more on
limiting project scope– An agile project sets a minimum number of requirements and turns
them into a deliverable product