4. RayBuse•AnalyticsforSoftwareDevelopment
Your responsibilities
• Defines the schedule commitments for the product group
• Delivers the product on time against milestones
• Develops effective metrics for the product
• Approves group goals and appropriately funds projects
• From improving the team's engineering system to improving the group's engineering system
• Prevents obstacles and analyzes where and why they occur in order to prevent them
• Ensures accountability across the group
• Ensures alignment between senior management and product group commitments
• Takes responsibility for decisions and uses appropriate decision-making techniques to drive effective
decision making in the group
• Ensures the group understands its connection to customer/partner value
• Ensures effective customer/partner feedback channels and mechanisms are in place and regularly utilized
across teams
• Ensures the group is appropriately aligned with other product teams to achieve results
• Proactively identifies problems across disciplines and improves cross-discipline processes
• Effectively takes advantage of his or her personal network of key contacts across disciplines to gather
feedback and improve the product
• Ensures an appropriate organization is in place and resources are optimized for success
• Proactively optimizes the group's recruiting processes and practices
• Defines performance standards for the group
• Conducts effective performance reviews of all team members, including managers
• Has succession plans in place for top talent including own successor
• Coaches and motivates managers
• Provides critical input into the discipline's vision and strategy
• Prioritizes resource needs for the group and executes against prioritized requirements
• Effectively implements change aligned with business objectives across the group
• Ensures that the product group thoroughly understands the customer's business, including current and
future needs
14. RayBuse•AnalyticsforSoftwareDevelopment
What Happened?
What is happening
now?
What will happen?
How and why did it
happen?
What is the next
best action?
What is the best/
worst that can
happen?
Past Present Future
Information
Insight
Difficulty 0.43
Importance 0.98
Difficulty 0.51
Importance 0.88
Difficulty 1
Importance 0.84
Difficulty 0.8
Importance 1
Difficulty 0.84
Importance 0.9
Difficulty 0.88
Importance 0.8
MoreDifficult
More DifficultMore Important
19. RayBuse•AnalyticsforSoftwareDevelopment
Exploration
Search for important factors in data.
Analysis
Answer specific questions.
Experimentation
Compare to alternate scenarios.
Past Summarization Trends Modeling
Present Alerts (& Correlations) Overlays Benchmarking
Future Forecasting Goals Simulation
Software Analytics Theory
20. RayBuse•AnalyticsforSoftwareDevelopment
Description Insight Relevant Techniques
Summarization Search for important or unusual factors to
associated with a time range.
Characterize events, understand
why they happened.
Topic analysis, NLP
Alerts (&
Correlations)
Continuous search for unusual changes or
relationships in variables
Notice important events. Statistics, Repeated
measures
Forecasting Search for and predict unusual events in
the future based on current trends.
Anticipate events. Extrapolation,
Statistics
Trends How is an artifact changing? Understand the direction of the
project.
Regression analysis
Overlays What artifacts account for current
activity?
Understand the relationships
between artifacts.
Cluster analysis,
repository mining
Goals How are features/artifacts changing in the
context of completion or some other
goal?
Assistance for planning Root-cause analysis
Modeling Compares the abstract history of similar
artifacts. Identify important factors in
history.
Learn from previous projects. Machine learning
Benchmarking Identify vectors of similarity/difference
across artifacts.
Assistance for resource allocation
and many other decisions
Statistics
Simulation Simulate changes based on other artifact
models.
Assistance for general decisions What-if? analysis
