Scrum is an approach of agile development concept.
Let says there are pigs and chickens. Based on this joke:
A pig and a chicken are walking down a road. The chicken looks at the pig and says, “Hey, why don’t we open a restaurant?” The pig looks back at the chicken and says, “Good idea, what do you want to call it?” The chicken thinks about it and says, “Why don’t we call it ‘Ham and Eggs’?” “I don’t think so,” says the pig, “I’d be committed but you’d only be involved.”
Now we see: Pigs are people which are committed and fully involved. They are so ‘dead’ if this project fails. But Chickens are interested on the project but not really affected since they are not committed but only involved.
Who are pigs?
- Product Owner
- Scrum Master (coach, fixer, gatekeeper -similar to project manager)
- Developer/Team
Who are chickens?
- Users
- Stakeholders
- Managers
And what do we do in Scrum. Take a look at this figure:

Let starts with what pigs do. Product owner will simply administer product backlog, which will contains list of requirement or maybe ‘wish-lists’ and the priority level of it.
Sprint backlog is a list of tasks for current sprint. It will be how and what to do for current sprint not more than 16 hours. If it is more than 16 hours it should be broken down further. Sprint is usually within period of 15-30 days.
Each day, there will be daily sprint burn down to list down the remaining tasks.
Why sprinting and why Scrum-ing?
By creating deliverable on each sprint stage, risk and possible problems can be seen at the early stage, and customer can be involved on development stage.
If there is any requirement changes, it can be done from early stage with reducing risk and minimal losses.
Okay pig, let’s get started!
*footnote of a struggling small pig in the end of the year.












