Education Post – Test

Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of “de Finibus Bonorum et Malorum” (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, “Lorem ipsum dolor sit amet..”, comes from a line in section 1.10.32.

The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from “de Finibus Bonorum et Malorum” by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham.

It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using ‘Content here, content here’, making it look like readable English. Many desktop publishing packages and web page editors now use Lorem Ipsum as their default model text, and a search for ‘lorem ipsum’ will uncover many web sites still in their infancy. Various versions have evolved over the years, sometimes by accident, sometimes on purpose (injected humour and the like).

	Scrum	Kanban	Scrumban
Best for	Teams working on projects and processes taking more than 12 months.	Teams focusing on maintenance, support services and manufacturing.	Teams working on fast-paced projects and manufacturing. It is also ideal for large-scale projects that require long term planning.
Work cycles	1-4 week iterations with regular meetings, reviews and retrospectives.	No iterations. Continuous workflow.	2-week iterations complete with regular meetings, reviews and retrospectives.
Planning	Structured. Planning takes place at the beginning of each Sprint.	Flexible. Relies on a probabilistic approach, based on past workflow data.	Need-based or on-demand planning, integrated with the work-in-progress. Planning trigger is initiated whenever the number of tasks in the ‘work-in-progress’ falls below a certain level.
Roles and Responsibilities	Team members are assigned roles and responsibilities.	No specific roles. Members select their own tasks. The team consists of either generalists or specialists.	No specific roles. Team members are allowed to select their own tasks.
Task Prioritization	Prioritization is done before each sprint.	Prioritization is done based on need and on demand.	Prioritization is done on demand. Managers designate the order of priority.
Team Members	Recommended for a team of 3-9 members.	No specific limitations.	No specific limitations.
Work In Progress Limits (WIP)	Restricted to a Sprint.	Practices limiting WIP. Limits the number of tasks that can be pulled to the in progress column.	Practices limiting WIP. Limits the number of tasks that can be pulled to the in progress column.
Tools	Product backlog. Sprint backlog. Product increments.	Kanban Board.	Scrumban Board.
Ownership	Owned by one team.	Multiple teams can collaborate.	Multiple teams can collaborate.
Change Policy	No new items can be included in a Sprint.	New items can be added depending on the availability and capacity.	New items can be added depending on the availability and capacity.