Public:Agile Ceremonies - Revision history

Anand Sathiyaseelan: Anand Sathiyaseelan moved page Agile Ceremonies to Public:Agile Ceremonies

2023-12-13T09:37:01Z

Anand Sathiyaseelan moved page Agile Ceremonies to Public:Agile Ceremonies

← Older revision

Revision as of 15:07, 13 December 2023

imported>Anand at 06:42, 27 April 2023

2023-04-27T06:42:31Z

← Older revision		Revision as of 12:12, 27 April 2023
Line 37:		Line 37:
	File:Agile calendar.png\|Agile Calendar		File:Agile calendar.png\|Agile Calendar
	</gallery>		</gallery>

			[[Category:Project Management]]

imported>Anand at 19:17, 10 March 2023

2023-03-10T19:17:27Z

← Older revision		Revision as of 00:47, 11 March 2023
Line 1:		Line 1:
	Agile ceremonies are recurring events that enable teams to plan, collaborate, and review their work. The most common ceremonies in Agile methodology are Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective. These ceremonies help to ensure alignment, transparency, and continuous improvement throughout the development process.		Agile ceremonies are recurring events that enable teams to plan, collaborate, and review their work. The most common ceremonies in Agile methodology are Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective. These ceremonies help to ensure alignment, transparency, and continuous improvement throughout the development process.

	[[File:Agile_Ceremonies.jpg\|alt=Agile ~~Calendar~~\|~~500px~~\|center\|thumb\|Agile ~~Calendar~~]]		[[File:Agile_Ceremonies.jpg\|alt=Agile Ceremonies\|600px\|center\|thumb\|Agile Ceremonies]] <br>

	~~[[File:Agile calendar.png\|alt=Agile Calendar\|thumb\|Agile Calendar]]~~
	'''<u>Product Backlog Alignment</u>''':		'''<u>Product Backlog Alignment</u>''':
			[[File:Agile calendar.png\|alt=Agile Calendar\|350px\|right\|thumb\|Agile Calendar]]
	# PO on regular basis to add '''''customer ideas''''', '''''feature requests''''', '''''defect incidents''''', '''''internal team’s improvement input''''' to the '''<u>product roadmap</u>'''		# PO on regular basis to add '''''customer ideas''''', '''''feature requests''''', '''''defect incidents''''', '''''internal team’s improvement input''''' to the '''<u>product roadmap</u>'''
	# PO to analyze the competitors, technology trends, market opportunity, strong user demand and '''<u>add or move the item from roadmap to product backlog</u>'''		# PO to analyze the competitors, technology trends, market opportunity, strong user demand and '''<u>add or move the item from roadmap to product backlog</u>'''
Line 11:		Line 10:
	# Stakeholders to discuss and provide recommendation of their priority for the product backlog items		# Stakeholders to discuss and provide recommendation of their priority for the product backlog items
	# Product owner (served by Scrum Master) would reassess, reprioritize and prepare the final list of product backlog items to be considered for the upcoming sprint (Ex: Sprint 2) and create the sprint backlog		# Product owner (served by Scrum Master) would reassess, reprioritize and prepare the final list of product backlog items to be considered for the upcoming sprint (Ex: Sprint 2) and create the sprint backlog


	'''<u>Product Backlog Refinement</u>''':		'''<u>Product Backlog Refinement</u>''':
Line 22:		Line 20:
	# PO to demostrate the prototype with the stakeholders/clients and get it approved		# PO to demostrate the prototype with the stakeholders/clients and get it approved
	# Product owner and scrum master to have refinement session 2 on Day 9 with the agile team and walk them through the revised acceptance criteria and definition of done and mark them as ‘Ready’		# Product owner and scrum master to have refinement session 2 on Day 9 with the agile team and walk them through the revised acceptance criteria and definition of done and mark them as ‘Ready’


	'''<u>Sprint Planning</u>''':		'''<u>Sprint Planning</u>''':
Line 30:		Line 27:
	# Developers to discuss the “How” ''(plan the work necessary to deliver the sprint goal and negotiate on the capacity and efforts)''The “Outcome” of the Sprint Planning is the agreed Sprint Backlog that describes the sprint goal and how the team will start working towards that goal		# Developers to discuss the “How” ''(plan the work necessary to deliver the sprint goal and negotiate on the capacity and efforts)''The “Outcome” of the Sprint Planning is the agreed Sprint Backlog that describes the sprint goal and how the team will start working towards that goal


			[[File:3355 Scrum.png\|alt=3355 Principle\|350px\|right\|thumb\|3355 Principle]]



			'''<u>Gallery</u>''':
	<gallery>		<gallery>
	File:3355 Scrum.png\|3355 Scrum Principle		File:3355 Scrum.png\|3355 Scrum Principle
	File:Agile calendar.png\|Agile Calendar		File:Agile calendar.png\|Agile Calendar
	</gallery>		</gallery>

imported>Anand at 19:08, 10 March 2023

2023-03-10T19:08:47Z

← Older revision		Revision as of 00:38, 11 March 2023
Line 31:		Line 31:

	<gallery>		<gallery>
	File:Scrum.~~jpg~~\|~~Agile Ceremonies~~		File:3355 Scrum.png\|3355 Scrum Principle
	File:Agile calendar.png\|Agile Calendar		File:Agile calendar.png\|Agile Calendar
	</gallery>		</gallery>

imported>Anand at 19:05, 10 March 2023

2023-03-10T19:05:02Z

← Older revision		Revision as of 00:35, 11 March 2023
Line 1:		Line 1:
	Agile ceremonies are recurring events that enable teams to plan, collaborate, and review their work. The most common ceremonies in Agile methodology are Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective. These ceremonies help to ensure alignment, transparency, and continuous improvement throughout the development process.		Agile ceremonies are recurring events that enable teams to plan, collaborate, and review their work. The most common ceremonies in Agile methodology are Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective. These ceremonies help to ensure alignment, transparency, and continuous improvement throughout the development process.

	~~<gallery>~~		[[File:Agile_Ceremonies.jpg\|alt=Agile Calendar\|500px\|center\|thumb\|Agile Calendar]]
	File:~~Scrum~~.jpg\|Agile ~~Ceremonies~~
	~~File:Agile calendar.png~~		[[File:Agile calendar.png\|alt=Agile Calendar\|thumb\|Agile Calendar]]
	~~</gallery>~~[[File:Agile calendar.png\|alt=Agile Calendar\|thumb\|Agile Calendar]]
	'''<u>Product Backlog Alignment</u>''':		'''<u>Product Backlog Alignment</u>''':

Line 30:		Line 29:
	# PO to present the Sprint backlog as “Input” to the ceremony and explain the “What” ''(describes the objective(or goal) of the sprint and what backlog items contribute to that goal. Developers need to understand how they can or cannot deliver that goal)''		# PO to present the Sprint backlog as “Input” to the ceremony and explain the “What” ''(describes the objective(or goal) of the sprint and what backlog items contribute to that goal. Developers need to understand how they can or cannot deliver that goal)''
	# Developers to discuss the “How” ''(plan the work necessary to deliver the sprint goal and negotiate on the capacity and efforts)''The “Outcome” of the Sprint Planning is the agreed Sprint Backlog that describes the sprint goal and how the team will start working towards that goal		# Developers to discuss the “How” ''(plan the work necessary to deliver the sprint goal and negotiate on the capacity and efforts)''The “Outcome” of the Sprint Planning is the agreed Sprint Backlog that describes the sprint goal and how the team will start working towards that goal

			<gallery>
			File:Scrum.jpg\|Agile Ceremonies
			File:Agile calendar.png\|Agile Calendar
			</gallery>

imported>Anand at 17:40, 10 March 2023

2023-03-10T17:40:38Z

← Older revision		Revision as of 23:10, 10 March 2023
Line 1:		Line 1:
	[[File:Agile calendar.png\|alt=Agile Calendar\|thumb\|Agile Calendar]]		Agile ceremonies are recurring events that enable teams to plan, collaborate, and review their work. The most common ceremonies in Agile methodology are Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective. These ceremonies help to ensure alignment, transparency, and continuous improvement throughout the development process.

			<gallery>
			File:Scrum.jpg\|Agile Ceremonies
			File:Agile calendar.png
			</gallery>[[File:Agile calendar.png\|alt=Agile Calendar\|thumb\|Agile Calendar]]
	'''<u>Product Backlog Alignment</u>''':		'''<u>Product Backlog Alignment</u>''':

imported>Anand: Anand moved page Agile Workflow to Agile Ceremonies

2023-03-10T16:22:04Z

Anand moved page Agile Workflow to Agile Ceremonies

← Older revision

Revision as of 21:52, 10 March 2023

imported>Anand at 08:08, 28 November 2022

2022-11-28T08:08:57Z

← Older revision		Revision as of 13:38, 28 November 2022
Line 1:		Line 1:
			[[File:Agile calendar.png\|alt=Agile Calendar\|thumb\|Agile Calendar]]
	'''<u>Product Backlog Alignment</u>''':		'''<u>Product Backlog Alignment</u>''':

imported>Anand at 08:07, 28 November 2022

2022-11-28T08:07:56Z

← Older revision		Revision as of 13:37, 28 November 2022
Line 1:		Line 1:
	'''<u>Product Backlog Alignment</u>''':		'''<u>Product Backlog Alignment</u>''':

	# PO on regular basis to add customer ideas, feature requests, defect incidents, internal team’s input to the product roadmap		# PO on regular basis to add '''''customer ideas''''', '''''feature requests''''', '''''defect incidents''''', '''''internal team’s improvement input''''' to the '''<u>product roadmap</u>'''
	# PO to analyze the competitors, technology trends, market opportunity, strong user demand and add move the item from roadmap to product backlog		# PO to analyze the competitors, technology trends, market opportunity, strong user demand and '''<u>add or move the item from roadmap to product backlog</u>'''
	# PO to collaborate closely with Key Stakeholders: Sponsors, Clients on Day 4 of current sprint (Ex: Sprint 1) and present them with the product backlog items		# PO to collaborate closely with Key Stakeholders: Sponsors, Clients on Day 4 of current sprint (Ex: Sprint 1) and present them with the product backlog items
	# Stakeholders to discuss and provide recommendation of their priority for the product backlog items		# Stakeholders to discuss and provide recommendation of their priority for the product backlog items

imported>Anand at 08:06, 28 November 2022

2022-11-28T08:06:15Z

← Older revision		Revision as of 13:36, 28 November 2022
Line 1:		Line 1:
	'''<u>Product Backlog Alignment</u>''':		'''<u>Product Backlog Alignment</u>''':

	1. PO on regular basis to add customer ideas, feature requests, defect incidents, internal team’s input to the product roadmap		# PO on regular basis to add customer ideas, feature requests, defect incidents, internal team’s input to the product roadmap
			# PO to analyze the competitors, technology trends, market opportunity, strong user demand and add move the item from roadmap to product backlog
	2. PO to analyze the competitors, technology trends, market opportunity, strong user demand and add move the item from roadmap to product backlog		# PO to collaborate closely with Key Stakeholders: Sponsors, Clients on Day 4 of current sprint (Ex: Sprint 1) and present them with the product backlog items
			# Stakeholders to discuss and provide recommendation of their priority for the product backlog items
	3. PO to collaborate closely with Key Stakeholders: Sponsors, Clients on Day 4 of current sprint (Ex: Sprint 1) and present them with the product backlog items		# Product owner (served by Scrum Master) would reassess, reprioritize and prepare the final list of product backlog items to be considered for the upcoming sprint (Ex: Sprint 2) and create the sprint backlog

	4. Stakeholders to discuss and provide recommendation of their priority for the product backlog items

	5. Product owner (served by Scrum Master) would reassess, reprioritize and prepare the final list of product backlog items to be considered for the upcoming sprint (Ex: Sprint 2) and create the sprint backlog


	'''<u>Product Backlog Refinement</u>''':		'''<u>Product Backlog Refinement</u>''':

	1. Product owner to work upon the acceptance criteria for the finalized product backlog items		# Product owner to work upon the acceptance criteria for the finalized product backlog items
			# Scrum master to work upon the Definition of Done
	2. Scrum master to work upon the Definition of Done		# Product owner and scrum master to have refinement session 1 on Day 7 with the agile team and walk them through the acceptance criteria and definition of done
			# PO to remove, split epics into user stories based on changing needs
	3. Product owner and scrum master to have refinement session 1 on Day 7 with the agile team and walk them through the acceptance criteria and definition of done		# PO to initiate a fast-paced Product Design Sprint in Sprint 1 to develope wireframe, prototype for the sprint backlog items planned in the upcoming Sprint 2
			# PO to demostrate the prototype with the stakeholders/clients and get it approved
	4. PO to remove, split epics into user stories based on changing needs		# Product owner and scrum master to have refinement session 2 on Day 9 with the agile team and walk them through the revised acceptance criteria and definition of done and mark them as ‘Ready’

	5. PO to initiate a fast-paced Product Design Sprint in Sprint 1 to develope wireframe, prototype for the sprint backlog items planned in the upcoming Sprint 2

	6. PO to demostrate the prototype with the stakeholders/clients and get it approved

	7. Product owner and scrum master to have refinement session 2 on Day 9 with the agile team and walk them through the revised acceptance criteria and definition of done and mark them as ‘Ready’