Public:Scrum - Revision history

Tushar Goswami: Tushar Goswami moved page Scrum to Public:Scrum

2024-05-25T02:52:14Z

Tushar Goswami moved page Scrum to Public:Scrum

← Older revision

Revision as of 08:22, 25 May 2024

imported>Anand at 06:42, 27 April 2023

2023-04-27T06:42:38Z

← Older revision		Revision as of 12:12, 27 April 2023
Line 153:		Line 153:
	6. Is NOT / Does not a MicroManage the team <br>		6. Is NOT / Does not a MicroManage the team <br>
	7. Does not order / influence using authority <br>		7. Does not order / influence using authority <br>

			[[Category:Project Management]]

imported>Anand at 11:12, 13 October 2022

2022-10-13T11:12:14Z

← Older revision		Revision as of 16:42, 13 October 2022
Line 129:		Line 129:


	=== Characteristics for the 3 ~~scrum~~ roles ===		=== Characteristics for the 3 roles in Scrum: ===
	'''Product Owner:'''		'''Product Owner:'''

imported>Anand at 11:08, 13 October 2022

2022-10-13T11:08:42Z

imported>Anand at 11:06, 13 October 2022

2022-10-13T11:06:53Z

← Older revision		Revision as of 16:36, 13 October 2022
Line 129:		Line 129:


			=== Characteristics for the 3 scrum roles ===
	Product Owner:		Product Owner:

imported>Anand at 11:05, 13 October 2022

2022-10-13T11:05:26Z

← Older revision		Revision as of 16:35, 13 October 2022
Line 127:		Line 127:

	\|}		\|}



			Product Owner:

			Understanding of the market, Skepticism, Independent Thinker <br>
			Good in communication (Ability to say no) <br>
			Negotiation <br>
			PO should be good networker, work with partners (industry leader, visionery) <br>
			Very much available to the team (to accept and refine the backlog items) <br>

			Developers (Design, Engg, DevOps...)

			Team members should be full time on a project. <br>
			Should not be shared across projects. At any given time member should be allocated to only one project. <br>
			Cross-functional and self-organized, team members to have core skills and ability to deliver the backlog items which are picked for the sprint <br>

			Scrum Master:

			Probing on best performance out of the team <br>
			Should be Change Agent, team can communicate with out hesitnation (SM should be approachable) <br>
			Good networker <br>
			Active learner (willing to try out new approaches so team can get onto a high performance) <br>
			Enforcer of the agile discipline <br>
			Is NOT / Does not a MicroManage the team <br>
			Does not order / influence using authority <br>

imported>Anand at 10:56, 12 October 2022

2022-10-12T10:56:00Z

← Older revision		Revision as of 16:26, 12 October 2022
Line 20:		Line 20:
	\|Courage		\|Courage
	\|-		\|-
	\|~~Scrum Team~~		\|Developers
	\|Daily Scrum		\|Daily Scrum
	\|Increment (Iteration)		\|Increment (Iteration)

imported>Anand at 12:45, 26 September 2022

2022-09-26T12:45:24Z

← Older revision		Revision as of 18:15, 26 September 2022
Line 58:		Line 58:
	<br>		<br>

	'''<u>~~Key Action 4~~</u> : Sprint Planning'''		'''<u>Ceremony Event 1</u> : Sprint Planning'''

	The Product Owner will come with objective in mind and a tentative list for the upcoming spring. Product Owner, Developers will discuss and Scrum Master will facilitate to decide upon: WHAT, WHO, WHEN, HOW. Scrum team will decide on the final list of work to be worked upon in the current sprint.		The Product Owner will come with objective in mind and a tentative list for the upcoming spring. Product Owner, Developers will discuss and Scrum Master will facilitate to decide upon: WHAT, WHO, WHEN, HOW. Scrum team will decide on the final list of work to be worked upon in the current sprint.
Line 64:		Line 64:
	<br>		<br>

	'''<u>~~Key Action 5~~</u> : Daily Scrum'''		'''<u>Ceremony Event 2</u> : Daily Scrum'''

	Meeting is to help the developers to improve collaboration, knowledge and accoutability towards the sprint backlog and promote quick decision making. Developers often meet immediately with peer for a detailed discussion.		Meeting is to help the developers to improve collaboration, knowledge and accoutability towards the sprint backlog and promote quick decision making. Developers often meet immediately with peer for a detailed discussion.
Line 70:		Line 70:
	<br>		<br>

	'''<u>~~Key Action 6~~</u> : Sprint Review'''		'''<u>Ceremony Event 3</u> : Sprint Review'''

	Product Owner presents the progress towards the Product Goal and explains what Product backlog items are "Done" and what has not been done. Key chanllenges are presented by the scrum team to the stakeholders.		Product Owner presents the progress towards the Product Goal and explains what Product backlog items are "Done" and what has not been done. Key chanllenges are presented by the scrum team to the stakeholders.
Line 76:		Line 76:
	<br>		<br>

	'''<u>~~Key Action 7~~</u> : Sprint Retrospective'''		'''<u>Ceremony Event 4</u> : Sprint Retrospective'''

	Discussion with in the scrum team to inspect itself with regards to the individuals, interactions, quality, process, tools. Scrum Team will plan to increase product quality by improving the work progress or Definition-of-done. Scrum master sets the stage ensures the meeting is positive, productive and engate every team member in gathering, filtering, generating insights on Improvements. Pros & COns are discussed and action items for improvements are planned for the next sprint.		Discussion with in the scrum team to inspect itself with regards to the individuals, interactions, quality, process, tools. Scrum Team will plan to increase product quality by improving the work progress or Definition-of-done. Scrum master sets the stage ensures the meeting is positive, productive and engate every team member in gathering, filtering, generating insights on Improvements. Pros & COns are discussed and action items for improvements are planned for the next sprint.

imported>Anand at 12:28, 26 September 2022

2022-09-26T12:28:36Z

← Older revision		Revision as of 17:58, 26 September 2022
Line 97:		Line 97:
	\|Purpose		\|Purpose
	\|Decide 'WHY' are we doing this Sprint, 'WHAT' are we doing to do in the Sprint, 'HOW' are we going to do the work chosen for this Sprint		\|Decide 'WHY' are we doing this Sprint, 'WHAT' are we doing to do in the Sprint, 'HOW' are we going to do the work chosen for this Sprint
	\|Inspect the progress towords the GOAL and ~~ADAPT~~ the ~~plan~~		\|Inspect the progress towords the SPRINT GOAL using Burn down chart, review the work, discuss impediments, ADAPT a plan and update the sprint backlog
	\|Inspect the Outcome of the Sprint and Determine future adaptation		\|Inspect the Outcome of the Sprint and Determine future adaptation
	\|Way to Improve Effectiveness & Quality by Creating an ACTION List		\|Way to Improve Effectiveness & Quality by Creating an ACTION List
Line 115:		Line 115:
	\|Inputs		\|Inputs
	\|Product Backlog, Capacity, Past Performance, Last Increment, Definition of Done		\|Product Backlog, Capacity, Past Performance, Last Increment, Definition of Done
	\|Sprint Backlog		\|Sprint Backlog / Task Board
	\|Increment, Product Backlog, Sprint Backlog		\|Increment, Product Backlog, Sprint Backlog
	\|Improvements on Individuals, Interactions, Process, Tools, Definition of Done		\|Improvements on Individuals, Interactions, Process, Tools, Definition of Done
Line 121:		Line 121:
	\|Outputs		\|Outputs
	\|Sprint Backlog		\|Sprint Backlog
	\|~~Sprint Backlog~~		\|Updated sprint backlog
	\|Review of the Product Backlog, Budget, Timeline, Progress check against Product Goal		\|Review of the Product Backlog, Budget, Timeline, Progress check against Product Goal
	\|List of Action Items for improvement		\|List of Action Items for improvement

imported>Anand at 12:16, 26 September 2022

2022-09-26T12:16:51Z

← Older revision		Revision as of 17:46, 26 September 2022
Line 60:		Line 60:
	'''<u>Key Action 4</u> : Sprint Planning'''		'''<u>Key Action 4</u> : Sprint Planning'''

	~~Text~~		The Product Owner will come with objective in mind and a tentative list for the upcoming spring. Product Owner, Developers will discuss and Scrum Master will facilitate to decide upon: WHAT, WHO, WHEN, HOW. Scrum team will decide on the final list of work to be worked upon in the current sprint.
	<br>		<br>
	<br>		<br>
Line 66:		Line 66:
	'''<u>Key Action 5</u> : Daily Scrum'''		'''<u>Key Action 5</u> : Daily Scrum'''

	~~Text~~		Meeting is to help the developers to improve collaboration, knowledge and accoutability towards the sprint backlog and promote quick decision making. Developers often meet immediately with peer for a detailed discussion.
	<br>		<br>
	<br>		<br>
Line 72:		Line 72:
	'''<u>Key Action 6</u> : Sprint Review'''		'''<u>Key Action 6</u> : Sprint Review'''

	~~Text~~		Product Owner presents the progress towards the Product Goal and explains what Product backlog items are "Done" and what has not been done. Key chanllenges are presented by the scrum team to the stakeholders.
			<br>
			<br>

	'''<u>Key Action 7</u> : Sprint Retrospective'''		'''<u>Key Action 7</u> : Sprint Retrospective'''

	~~Text~~		Discussion with in the scrum team to inspect itself with regards to the individuals, interactions, quality, process, tools. Scrum Team will plan to increase product quality by improving the work progress or Definition-of-done. Scrum master sets the stage ensures the meeting is positive, productive and engate every team member in gathering, filtering, generating insights on Improvements. Pros & COns are discussed and action items for improvements are planned for the next sprint.

	===Summary of Agile Ceremonies:===		===Summary of Agile Ceremonies:===

← Older revision		Revision as of 16:38, 13 October 2022
Line 130:		Line 130:

	=== Characteristics for the 3 scrum roles ===		=== Characteristics for the 3 scrum roles ===
	Product Owner:		'''Product Owner:'''

	Understanding of the market, Skepticism, Independent Thinker <br>		1. Understanding of the market, Skepticism, Independent Thinker <br>
	Good in communication (Ability to say no) <br>		2. Good in communication (Ability to say no) <br>
	Negotiation <br>		3. Negotiation <br>
	PO should be good networker, work with partners (industry leader, visionery) <br>		4. PO should be good networker, work with partners (industry leader, visionery) <br>
	Very much available to the team (to accept and refine the backlog items) <br>		5. Very much available to the team (to accept and refine the backlog items) <br>

	Developers (Design, Engg, DevOps...)		'''Developers (Design, Engg, DevOps...)'''

	Team members should be full time on a project. <br>		1. Team members should be full time on a project. <br>
	Should not be shared across projects. At any given time member should be allocated to only one project. <br>		2. Should not be shared across projects. At any given time member should be allocated to only one project. <br>
	Cross-functional and self-organized, team members to have core skills and ability to deliver the backlog items which are picked for the sprint <br>		3. Cross-functional and self-organized, team members to have core skills and ability to deliver the backlog items which are picked for the sprint <br>

	Scrum Master:		'''Scrum Master:'''

	Probing on best performance out of the team <br>		1. Probing on best performance out of the team <br>
	Should be Change Agent, team can communicate with out hesitnation (SM should be approachable) <br>		2. Should be Change Agent, team can communicate with out hesitnation (SM should be approachable) <br>
	Good networker <br>		3. Good networker <br>
	Active learner (willing to try out new approaches so team can get onto a high performance) <br>		4. Active learner (willing to try out new approaches so team can get onto a high performance) <br>
	Enforcer of the agile discipline <br>		5. Enforcer of the agile discipline <br>
	Is NOT / Does not a MicroManage the team <br>		6. Is NOT / Does not a MicroManage the team <br>
	Does not order / influence using authority <br>		7. Does not order / influence using authority <br>