Delivered by Ashraf Al Shafaki ObjectivesBy the end of this course you will be able to: - Manage software projects effectively.
- Communicate well with team members.
- Complete software project on time and within budget.
- Compete within a fast changing technology and economic environment.
PrerequisiteContentIntro- Introduction to Agile Methodologies, other agile methodologies (why we need agile, agile vs. non-agile methodologies)
Issues- Product owner changes his mind about project requirements (thus frustrating developers and over-stressing the project)
People- Scrum Master
- Team members
- Product Owner
Meetings- Daily Scrum meeting
- Sprint Planning meeting
- Sprint Review meeting
- Sprint Retrospective
Artifacts- Product Backlog
- Sprint Backlog
- Burn Down Chart
Points- Workshop style
- Printed material included
- After completing the training, each participant will be provided with a certificate of attendance.
- Display of Scrum video (at Google).
- Participants will be provided with evaluation forms to provide their feedback on the training.
- Transparency (fluent communication)
- Time boxing
- Lightweight (light weight documentation)
- * Case studies (a situation at a software company, how things have developed, then questions at the end to start a discussion). Can be elicited from trainees (real situations they have faced).
- Working on mini projects to practice: sprint planning meeting.
- Diagram explaining the Scrum process in action (30 days sprint, meetings ... etc). (use in the presentation and in a prominent place in the printed documentation)
- Each iteration is a stand-alone working program.
- If a feature is said to be complete it means it has been tested.
- Scrum is about being realistic about projects and people (people need motivation, project owners change their minds ... etc).
- Scrum boosts communication (and provides transparency).
Issues- Not finishing projects on time (extending time for a project, or turning over a poor quality project).
Unrealistic Assumptions- A product owner knows exactly what he wants right from the start.
Benefits- Part of the functionality can be shipped to client even before the whole project is complete.
- Scrum is good at managing risk.
- Why scrum? It deals with rapid change, which is a sign of the days.
Exercises- Action plan (what you will do at work, trying Scrum).
|
|