Would you like to SCRUM?
Would you like to Scrum? – 0632
The benefits of this class
– Why agile methodologies?
- They were devised to address quicker response in the development of software
- Dynamic and Flexible Methodologies for Gathering Requirements/Requests, Development Cycles to improve Product to Market delivery.
- Principles (Agile Manifesto)
- Individuals and Interactions over processes and tools
- Working Software over Comprehensive Documentation
- Customer Collaboration over Contract Negotiations
- Responding to Change over Following a plan.
- Examples of Agile Methodologies – Share Common Agile Traits
- SCRUM
- XP
- Adaptive Software Development
- DSDM
- Crystal Clear
- Feature Driven Development
- Lean Development (LD)
- Commonalities among Agile Methodologies
- Self Organizing Teams
- Iterative, with a Functional deliverable at the end of the iteration
- Regular and planned communication and team interaction
- Short protected periods of time to create work product (sprint, time boxes, etc…)
- Scalable (Functions well when size/volume changes)
- Roles in Scrum
- Three primary roles
- Product Owner
- Scrum Team
- Scrum Master (Project Manager)
- Others…Users, Stakeholders, Consulting Experts.
- Three primary roles
- Work in the Backlog is a collection of User Stories
- Contains the following elements
- Informal statement of requirements
- As a (End User Role)
- I want to (Achieve a goal/the desire)
- So that I can (the rationale/value)
- What what why, not how.
- Clarification of requirements in a realistic content
- Informal statement of requirements
- Contains the following elements
- Product Backlog
- Interest of the product owner
- Sprint Backlog
- Interest of the Scrum Team
- How do we monitor?
- Daily Scrum – Standup 15 Minute Meeting (3 Questions)
- What did you do in the last 24 hours
- What are you going to do in the next 24 hours
- Is anything getting in the way of you completing your work? What obstacles need to be removed. Scrum Master is responsible for getting the obstacles out of the way.
- Burndown Chart.
- During the sprint the scrum master maintains the sprint burndown chart to show estimated work remaining, updating it after the daily scrum. Work can increase if estimates are off or if rework is required for specific tasks.
- How is a Scrum organized?
- Scrum is organized based upon the needs of the organization.
- Other skills/knowledge/decisions
- How do we help product owners prioritize their backlog
- How to develop good estimates?
- Planning poker.
- Writing good user stories
- The basic skill is facilitation… being able to effectively coordinate the efforts of others.
- Is your organization ‘ready’ for scrum?
- Simple method that is new and different… seems a bit loose but change can be a challenge.
- Daily Scrum/Standup Meeting Can be Used Now.
- During the spring… no changes are allowed in the iteration.
- No problem solving during the Daily Scrum…. Only after the meeting.
- Daily Scrum – Standup 15 Minute Meeting (3 Questions)
- Sprint Retrospective (ie. Lessons learned)
- A more frequent review of what worked well and should be repeated and what didn’t work an should be changed or abandoned.
- How is SCRUM being used by Sungard HE?
- Product development, including eLearning integration and FlexReg
- SGHE project implementations: Digital Campus approach for the SGHE Team is SCRUM based.
SCRUM U – SCRUMU.org
- Collaborative group of universities using the SCRUM method.
Can you use SCRUM in an ERP implementation?
– Consider agile values that can be applied to ERP project implementations.
- Work incrementally
- Open Communication
- Feedback to help guide the next steps
- Daily standups
- YAGNI – You are Not Going to Need It.
——————-