2. 2
Please note the following
IBM’s statements regarding its plans, directions, and intent are subject to change or
withdrawal without notice at IBM’s sole discretion.
Information regarding potential future products is intended to outline our general product
direction and it should not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment,
promise, or legal obligation to deliver any material, code or functionality. Information
about potential future products may not be incorporated into any contract. The
development, release, and timing of any future features or functionality described for our
products remains at our sole discretion.
Performance is based on measurements and projections using standard IBM
benchmarks in a controlled environment. The actual throughput or performance that any
user will experience will vary depending upon many factors, including considerations
such as the amount of multiprogramming in the user’s job stream, the I/O configuration,
the storage configuration, and the workload processed. Therefore, no assurance can be
given that an individual user will achieve results similar to those stated here.
4. 4
Enterprise Reporting Challenges
Organizational process
Different departments, different processes, not unified
Various disparate data sources
Roll-up of data doesn't compare well
Lack of visibility into organization metrics
Manual process
High Level of effort / Time consuming = $
Inaccurate / unreliable data
Outdated metrics
Individual product reporting
Lack of functionality/customization
Training & Resources = $
5. 5
Rational Insight
IBM Rational’s Performance Measurement Offering
An Enterprise Reporting solution that gets consistent metrics from across an organization
to objectively measure status and progress
Measure program, project, and team-level progress against pre-defined business
objectives through multiple views
Identify high-priority items and Become notified of high-severity items
Report & Dashboard elements viewable via
Web browser
iPads
Mobile phones
MS Office, PDF
Any tool that is JSR168 compliant
6. 6
Key Benefits
Automation
Increased Reliability
Versatile Integration support
Cross-product reporting
Traceability
Trending & historical data (DW model)
Real-time data (Live model)
Web-based tool
Custom/Interactive dashboards (Business Insight)
OOTB Collateral
XML data mappings
ETL fact builds, dimension builds, jobs
Framework Manager projects
Data Warehouse structure
Reports and Dashboards
7. 7
Insight Architecture
Based on Cognos 10 BI platform, industry proven technology
Leverages web architecture
Integration Options
REST service (adapter)
REST service (native)
Direct DB access
ODBC access
Generic XML
Very open architecture and wide-range compatibility
9. 9
What is Kanban?
Kanban – means signal card in Japanese
Kanban System – a pull system that uses card sets to control the work-in-progress (WIP)
in a manufacturing process.
10. 10
Kanban in Software Development
Taskboards can be used as the basis for visualization of a virtual kanban system.
Backlog Design Coding Testing Ready4 5 5
11. 11
Kanban in Software Development
Taskboards can be used as the basis for visualization of a virtual kanban system.
Backlog Design Coding Testing Ready4 5 5
15. Kanban Approach to Change
Principles of Kanban Method
Start with what you do NOW
Agree to pursue evolutionary change
Initially respect existing roles, responsibilities and job titles
16. 16
Kanban Core Practices
Visualize Workflow
Limit Work-in-Progress
Measure and Manage flow
Make management policies explicit
Improve collaboratively (using models and the scientific method)
18. 18
Kanban Analytics and Metrics
Cumulative Flow Diagram Analysis
Mean Delivery Rate
Avg Lead Time
WIP
19. 19
Kanban Analytics and Metrics
Throughput Trend
Throughput represents the number of items that were delivered in a given time period, such as one month.
WIs
Time
20. 20
Lead Time in Kanban
Backlog Design Coding Testing Ready4 5 5
Lead Time
21. 21
Kanban Analytics and Metrics
Lead Time Average
Shows the average of the Lead Time over time.
AverageLeadTime
Time
22. 22
Kanban – A Case Analysis using metrics with Rational Insight
A company’s software development area began facing some delays in software delivery.
The team will utilize their Kanban metrics dashboard to identify what is going wrong
Analyze WIP and Lead Time and Throughput
Identify a bottleneck of the increasing number of tasks in one of the stages of the process
24. 24
Our Demonstration Environment
Insight 1.1.1.1
Report Server
(WAS v8)
Jazz Team Server
Team Concert
4.0.2
Cognos Statistics
Plug-in
DB2 Server
Content Store
Data Warehouse
ETL Catalog
25. 25
Achievements through Kanban
Improved predictability through lead time distribution and lead time average
trend
Identified a process improvement opportunity (improve efficiency)
Identified bottleneck in the process flow (coding phase)
27. 27
Daily Apple TV giveaway
Complete your session surveys online each day at a conference kiosk or on
your Innovate 2013 Portal!
Each day that you complete all of that day’s session surveys, your name will
be entered to win the daily Apple TV!
On Wednesday be sure to complete your full conference evaluation to receive
your free conference t-shirt!