Electromagnetic relays used for power system .pptx
Agile- Scrum
1.
2. Introduced on early 90’s after waterfall model
Can be applied to nearly any projects
Formalized for software development projects
For projects with rapidly changing and highly emergent
requirements
Feedback loops between required product and process
implemented
Iterative and incremental approach
3. Better communication among team members
Quick decision making
Easier to cope with the changes - short “SPRINTS”
Daily meeting rules
Allows team to change direction of project at any point
TRANSPARENCY – open and honest with everyone
Maintain predictable schedule
4. A scrum team has three roles:
Scrum Team : 6 ± 3 members,
Selects works to be completed in next sprint
Scrum Master : Makes sure that team is productive,
Conducting “daily scrum” meeting
Attributes are :Responsible, Collaboration,
Committed ,Influential, Knowledgeable
Product Owner : Manage backlog ,
Has a vision of what he/she wishes to build,
Has certain skills like communication skills
5. Three Meetings:
Sprint Planning : What work is to be done
Scheduling for sprint backlog
Works accomplished (2-4 weeks)
Daily Scrum : Time Boxed (always same time and
location)
Maximum 15 minutes discussion
“What I did today, What will I do tomorrow”
Retrospective : What went well during the sprint
What could be improved in next time
6. Three Artifacts :
Product Backlog : Shortly described project documentation
Contains features desired in product
Written by Scrum Team and Product Owner
Sprint Backlog : Lists of tasks to be completed in scrum sprint
Tasks selected from product backlog
Written by Scrum Team
Burndown Charts : Publicly displayed chart
Shows remaining works in sprint backlog
Updated every day
Way for team to track progress
9. What an end user or customer wants
Any one can write user story
As a “WHO” , I want “What”, So that I can “WHY” .
Simply written on index cards or sticky notes
Content written are very important
Large user stories are known as epics
Example:
As a teacher, I want to upload my notes , so
that my students can download it.
Acceptance Criteria : - File format is pdf or doc
- Only registered students can download
- Notes cannot be deleted
10. Client /
Customer
* Presents
needs and
requirements
Product Owner
* Work with
stakeholders
* Manage Backlog
* Satisfy clients needs
* Define goal for team
* Creates a vision
Business Owner
* Special
Stakeholder
* Controls Budget
for team
Scrum Master
* Organize meetings
* Kick external burnouts in
team
* Ensures workflow is in
rhythm
* Manage Sprints
* Take team to right path
* Manage relation between
stakeholders and team
members
* Manage Backlogs and view
burn-down charts
* Ensures team works
according to backlog formed
Scrum Team
* Writes User stories
* Ensures project to be in right path
* 6± 3 members
* Follow agile scrum rules
* Attain meetings
* Lists of "TO-DO , DOING and DONE"
maintained
* Consists of Developers, SM, BO, PO,
stakeholders
Figure: Scrum Methodology Architecture
11. Ensures effective use of time and money
Large projects broken into chunks
Good for fast moving development projects
Scrum meeting makes clear visibility to team members
Better communication among scrum team members
TRANSPARENCY – open and honest
Feedback from customers and stakeholders
Short Sprint helps easy changes
Individual effort seen
12. Negligence of any team member can result into project failure
Modeling for larger teams is challenging
Daily stand up meetings can go frustrating and irritating for
some team members
If any team member leaves, the project can lead to failure
