This Post is part of Scrum Master Series
Scrum is originally the American football meeting the team makes before the actual game
Scrum is a good agile way of developing and planning software programmers
It is basically have the idea of doing not discussing, if you are new to scrum meetings
You will get the impression that scrum wastes a lot of time talking and discussing things
But soon you will know that scrum is about the concept "If it doesn’t work find something else"
Scrum is more focused on the small Item "PBI" to device the big picture,
When working with scrum you have to believe in the idea of you make your small task right it will fit into the big picture right …
You don’t have to design the big picture first like waterfall design … Just focus on the small requirement and it will make the big picture after wards
Scrum is about inspecting things and adapting them, people using scrum should enjoy being
Fearlessness: have no fear of talking out loud about problems or task status
Openness: Open to talk about things and help each other reaching the target
Creative, Common Sense
Agile
is a set of principles for software development that emphasizes frequent delivery of product increments
Time boxes communication & collaboration, focusing in subtasks opposite to water fall which is more the big picture
However the product owner in scrum should make sure everybody knows the big picture
Scrum is a flavor of agile that emphasizes self-organization through
30 days iteration (sprint)
3 Roles (Product Owner, Scrum Master, Scrum Team)
3 Meetings (Sprint Planning, Daily Scrum, Sprint Review)
Presenting Scrum in a simple and small flow
Scrum is not for cowboys or developer heroes because they are not team players
And scrum depends deeply on "Swarming"
All team work together in same task so no one owns a task or specialized with one feature
[...] Scrum Introduction [...]