File
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

File

on

  • 321 views

 

Statistics

Views

Total Views
321
Views on SlideShare
321
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

File Presentation Transcript

  • 1.  
  • 2. Agenda
    • Background
      • Current Software Development Processes
      • Current Software Development Tools
    • Chosen Solution
      • Rational Unified Process (RUP)
      • IBM Software Development Platform
      • Why This Solution
    • Approach to Implementation
      • Enablement Office
      • Adoption Through Execution
      • Software Engineering Process Authority
  • 3. Background
    • The following statistics are from the Standish Group (2003)
      • Only 34% of all software projects studied were delivered on schedule and within budget
      • Average cost overrun was estimated to be 43%
      • Average time overrun was estimated to be 82%
    • How well do you think YOUR COMPANY is doing?
  • 4. Background Current State
    • Varying Software Development Processes
      • For many years we have had varying processes/methodologies in-house that are all serial or “waterfall” in nature.
      • The individual processes themselves are rarely followed consistently from one area of the organization to the next.
    • Varying Software Development Tool Products/Vendors
      • We currently have a smattering of point solution development tools that don’t play very well together.
      • Redundant tools for similar functions.
      • Tremendous overhead from workarounds that force minimal “integration”.
  • 5. IBM Rational Solutions RUP and IBM Software Development Platform
    • Rational Unified Process (RUP)
      • A configurable software development process platform that delivers proven best practices and a configurable architecture.
      • An industry-standard, prescriptive system development process.
      • Encompasses the logical activities that take place throughout a software development project.
      • Will enable us to select and deploy only the process components we need for each project as well as each stage of a project.
    The fundamental principles of the RUP apply to any type of software development, whether it is clean slate, re-platforming or legacy system evolution
  • 6. IBM Rational Solutions RUP and IBM Software Development Platform
    • IBM Software Development Platform
      • A complete solution for developing software and software-based systems.
      • Tools for analysts, architects, developers, testers and project managers that unifies software development teams.
      • Fully integrated and comprehensive platform for our end-to-end software development.
      • Will enable us to operate more efficiently and deliver innovative products that can set us apart from our competitors.
    Maximize our output Improve our time-to-value Increase our agility to the business stakeholders
  • 7. IBM Rational Solutions RUP and IBM Software Development Platform
    • Why do we need to change / why this solution?
      • We need to leverage software development to improve our business performance.
      • Closely aligning business, development & operations, and automation of our activities will enable us to identify and work towards a shared set of business goals.
      • IBM Rational Professional Bundle will supply us with all the desktop tools our enterprise needs to design, construct, and test applications on both Windows and Linux, in a single purchase with one maintenance contract.
  • 8. Implementation Approach
    • Controlled, governed, and structured approach to the enterprise implementation
    • Multi-year charter and funding
    • Creation of a formalized Enablement Office responsible and accountable for implementation
      • Assess the process adoption and tools utilization in each discipline
      • Identify and prioritize the focus areas for each discipline
      • Address the needs identified on an on-going basis
  • 9. Implementation Approach Enablement Office
    • Reporting structure:
  • 10. Implementation Approach Build the Business Case for Change
    • The process to implement the RUP and IBM Rational Solutions to an organization differs from introducing them to a project team or working group
      • Background of current state
      • Know your organization (assessment)
      • Ranking of formal (management) and informal (anyone) leaders
      • Assembling the team
      • Reviewing assessment input options
      • Gathering data, selecting interviewees
      • Interviews
      • Analysis of key areas where RUP and Rational tools add value
      • Financial calculations
      • Writing your ROI assessment
  • 11. Implementation Approach Adoption Through Execution
    • Execute RUP and tool utilization in real projects (pilots)
      • Not process definition (customization & configuration)
      • Process and tools must be executed in real projects in our environment and domain to demonstrate the value
      • Transfer skill set from our external mentors (IBM Rational Brand Services) to our internal mentees
      • Develop our RUP tailored process based on the lessons learned from the pilot projects
    At the end of the day, we will have a repeatable process that is predictable
  • 12. Implementation Approach Adoption Through Execution
    • Pilot Projects
      • Weighted and ranked criteria for selecting pilot projects
      • Learning by doing – NOT theoretical discussion
        • Supported by just-in-time training
        • Immediate mentoring on actual pilot project(s)
        • Internal mentees will be part of the core pilot project resources in respective disciplines receiving knowledge transfer from our external mentors
      • Results driven to goal of demonstrating the value of the process and tools within the context of the project
    It is in the pilot projects that the actual adoption takes place…not in creating templates and guidelines before ever executing in a real project with our resources!
  • 13. Implementation Approach Pilot Projects
  • 14. Implementation Approach Software Engineering Process Authority
    • Software Engineering Process Authority (SEPA)
      • Tightly coupled with Rational Enablement Office
      • Responsible for taking the lessons learned from the RUP pilot projects and instantiating them across the organization
      • Symbiotic relationship
        • Enablement office pilots produce lessons learned in this environment
        • SEPA takes these lessons across the organization
        • Enablement office benefits when pilots are run in these other areas from the SEPA already bringing earlier lessons learned
        • Starts over with item one…
    It is in the pilot projects that the actual adoption takes place…not in creating templates and guidelines before ever executing in a real project with our resources!
  • 15. Implementation Approach Process Owners Group Pilot 2 Pilot 1 Pilot 3 Pilot 4 SEPA SEPA Next Slide… Environment Project Management Config & Change Mgnt Deployment Test Implementation Analysis & Design Requirements Business Modeling Department 4 Mainframe Department 3 Packaged Apps Department 2 Web/J2EE Department 1 Client Server
  • 16. Implementation Approach Software Engineering Process Authority Pilot SEPA It is at these intersection points where the SEPA takes the lessons learned from the pilot projects and instantiates it across the organization in the other departments. The REO benefits from these early lessons learned being incorporated into the behavior and activities of resources when pilot projects are executed at a point in the future in those areas…
  • 17. Pilot Projects
    • How Many?
      • Look to run 1 to 3 pilots for a given type of technology
        • Take the lessons learned from each one and apply to the next
        • Validate that there are improvements to the process from the lessons learned
        • Make this the standard for all new project in that technology
    • Core Resources
      • Make sure that your core project resources have the right skills for your pilots
        • J2EE project needs developers that have coded J2EE in your environment
        • UML notation experience is needed if you are going to use ROSE/XDE
        • Piling new tools and process onto someone that does not have the right skills setting up your project for failure
  • 18. Implementation Approach Pilot Projects Time Adoption % P1 P2 P3 P4 P5 P6 P7 P8
  • 19. [email_address] For all questions, please feel free to contact me at the following email address: