Please enable JavaScript.
Coggle requires JavaScript to display documents.
Managing Business Analytics Projects - Coggle Diagram
Managing Business Analytics Projects
Analytics Process
CRISP-DM
Business Understanding
(1S p15)
Understanding the project objectives and requirements from a business perspective
Data Understanding
(1S p16)
Data Preparation
Can move here only when business and data understanding are clear
Modeling
(1S p21)
Evaluation
(1S p22-26)
Decision engineering
Deployment
(1S p29-42)
Development
Need to develop the implementation and operational plans
Transition / Rollout
Normally done in phases
Maintenance
Scoping considerations
(1S p51-55)
Cross-industry standard process for data mining
Project Lifecycles
Predictive Life Cycles
(2S p15)
Commonly called waterfall
Use when product to be delivered is well understood and need to deliver in full to have value
Incremental & Iterative Life Cycles
(2S p17)
Used for large projects where technology is well understood but have expanding requirements
Adaptive Life Cycles
(2S p19)
Known as agile method
Use when the scope is unpredictable, and where the highest priority is regular feedback and delivery.
Pointers in BA projects
(2S p23-29)
Disciplined Agile
(2S p35-49)
Inception
Form initial team
(2S p55-69)
Primary roles
Team Lead
Product Owner
Architecture Owner
Team Member
Stakeholder
Having stakeholder register to manage their concerns and expectations
Secondary roles
Develop Common Vision
(2S p71-73)
Align with Enterprise Direction
(2S p77)
Explore Initial Scope
(2S p79-83)
Identify Initial Technical Strategy
(2S p97-101)
Develop Initial Release Plan
(2S p85-93)
Secure Funding
(2S p103-105)
Form Work Environment
(2S p107)
Identify Risks
(2S p109-111, 121)
Construction
Produce a Consumable and Deployable Release
Needs Exploration
(3S p23-39)
Product Backlog / Work Item Stack
User Story
(3S p27, 29-30)
Technical Story
(3S p28, 31)
Story Points
Measure the effort required to complete a story
Solution Exploration
(3S p40-41)
Rolling Wave Planning
(3S p42-44)
Assurance
(3S p45-50)
Defining "Done"
(3S p46-48)
Verification and Validation
(3S p49-50)
Prove Architecture
(3S p51-54)
Validate and Verify Architecture
Ensure data governance and security compliance
Deployment Strategy
(3S p55)
Managing Project Risk
(3S p57-62)
Come out with a risk plan and risk burn down chart
Addressing Changing Stakeholder Needs
(3S p66-68)
Prioritization
Tracking and Control
Burn Down Chart
(3S p71-76)
A graphical representation of “work left to do” vs time.
Velocity Factor
(3S p77-79)
Measures how fast the team is delivering functionality in an iteration.
Used to plan the release date.
Transition
Ensure the Solution is Consumable
(3S p84)
Stakeholder Readiness
Production Readiness
Deploy the Solution
(3S p85)
Work with DevOps to plan the deployment
Release the Deployment
Review the Deployment
Review & Retrospective
(3S p86-88)
Review Product
Celebrate the Launch
Retrospective
Agile 3C rhythm
(2S p47)
Coordinate
Collaborate
Conclude
People-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value life cycle, is goal-driven, and is enterprise aware.
Rollout
(3S p93)
Review Roll-out plan
Execute Roll-out Plan
Maintenance
(3S p94)
Model Health Check / Improvements / Data Updates
UI / Reports / Data Visualization Improvements
Bug Fixes / Refactoring