Agile project management - Revision history

Tkokotas at 15:17, 16 November 2018

2018-11-16T15:17:41Z

← Older revision		Revision as of 15:17, 16 November 2018
Line 1:		Line 1:
			''Developed by Hoda Vazirinasab''


	==Abstract==		==Abstract==
	'''''” Agility means the ability to balance between flexibility and stability.'''''		'''''” Agility means the ability to balance between flexibility and stability.'''''

Hoda.vn: /* SCRUM */

2018-02-28T18:03:45Z

SCRUM

← Older revision		Revision as of 18:03, 28 February 2018
Line 98:		Line 98:
	*'''''Sprint Demo''''': A meeting that team share what they've shipped in that sprint.		*'''''Sprint Demo''''': A meeting that team share what they've shipped in that sprint.
	*'''''Daily Stand up''''': Also named stand-up is a definition for 15-minute mini-meeting for the software team to sync.		*'''''Daily Stand up''''': Also named stand-up is a definition for 15-minute mini-meeting for the software team to sync.
	*'''''Retrospective''''': A revising of what did and didn't go well with actions to help make the next sprint better).<ref name="multiple">CLAIRE DRUMOND. Agile Project Management. [ONLINE] Available at: "https://www.atlassian.com/agile/project-management"</ref>.		*'''''Retrospective''''': A revising of what did and didn't go well with actions to help make the next sprint better.<ref name="multiple">CLAIRE DRUMOND. Agile Project Management. [ONLINE] Available at: "https://www.atlassian.com/agile/project-management"</ref>.



	====Kanban====		====Kanban====

Hoda.vn: /* XP */

2018-02-28T17:57:55Z

← Older revision		Revision as of 17:57, 28 February 2018
Line 122:		Line 122:
	====XP====		====XP====
	[[File:XP1.png\|200px\|thumb\|Extreme Programming (XP) at a Glance] Available at <ref>[''Extreme Programming (XP) at a Glance (Visual) BY JD Meier,June 6, 2014 ''] [ONLINE] Available at''https://blogs.msdn.microsoft.com/jmeier/2014/06/06/extreme-programming-xp-at-a-glance-visual/'' </ref> ]]		[[File:XP1.png\|200px\|thumb\|Extreme Programming (XP) at a Glance] Available at <ref>[''Extreme Programming (XP) at a Glance (Visual) BY JD Meier,June 6, 2014 ''] [ONLINE] Available at''https://blogs.msdn.microsoft.com/jmeier/2014/06/06/extreme-programming-xp-at-a-glance-visual/'' </ref> ]]
	'''''XP''''' is initial for '''''Extreme Programming''''' which is an '''''agile software development method''''' and its main goal is to produce higher quality software, and superior quality of life for the development team. '''''XP''''' is the most particular of the agile frameworks regarding suitable engineering practices for software development. As '''''Extreme Programming''''' concentrate on customer satisfaction its mention as a successful method.[ONLINE] Available at: "http://www.extremeprogramming.org/"</ref>.		'''''XP''''' is initial for '''''Extreme Programming''''' which is an '''''agile software development method''''' and its main goal is to produce higher quality software, and superior quality of life for the development team. '''''XP''''' is the most particular of the agile frameworks regarding suitable engineering practices for software development. As '''''Extreme Programming''''' concentrate on customer satisfaction its mention as a successful method.<ref>Don Wells. All Rights reserved.
			Last modified October 8, 2013. Extreme Programming:
			A gentle introduction. [ONLINE] Available at: "http://www.extremeprogramming.org/"</ref>.

	==Limitation==		==Limitation==

Hoda.vn: /* XP */

2018-02-28T17:56:38Z

← Older revision		Revision as of 17:56, 28 February 2018
Line 122:		Line 122:
	====XP====		====XP====
	[[File:XP1.png\|200px\|thumb\|Extreme Programming (XP) at a Glance] Available at <ref>[''Extreme Programming (XP) at a Glance (Visual) BY JD Meier,June 6, 2014 ''] [ONLINE] Available at''https://blogs.msdn.microsoft.com/jmeier/2014/06/06/extreme-programming-xp-at-a-glance-visual/'' </ref> ]]		[[File:XP1.png\|200px\|thumb\|Extreme Programming (XP) at a Glance] Available at <ref>[''Extreme Programming (XP) at a Glance (Visual) BY JD Meier,June 6, 2014 ''] [ONLINE] Available at''https://blogs.msdn.microsoft.com/jmeier/2014/06/06/extreme-programming-xp-at-a-glance-visual/'' </ref> ]]
	'''''XP''''' is initial for '''''Extreme Programming''''' which is an '''''agile software development method''''' and its main goal is to produce higher quality software, and superior quality of life for the development team. '''''XP''''' is the most particular of the agile frameworks regarding suitable engineering practices for software development. As '''''Extreme Programming''''' concentrate on customer satisfaction its mention as a successful method~~. Instead of delivering everything you could possibly want on some date far in the future this process delivers the software as you need it.~~		'''''XP''''' is initial for '''''Extreme Programming''''' which is an '''''agile software development method''''' and its main goal is to produce higher quality software, and superior quality of life for the development team. '''''XP''''' is the most particular of the agile frameworks regarding suitable engineering practices for software development. As '''''Extreme Programming''''' concentrate on customer satisfaction its mention as a successful method.[ONLINE] Available at: "http://www.extremeprogramming.org/"</ref>.
	'''''Teamwork''''' is one of the most emphasizing part of '''''Extreme Programming'''''. Managers, customers, and developers are all equal components in a cooperative team. Extreme Programming implements a simple, yet effective environment enabling teams to become highly productive. The team self-organizes around the problem to solve it as efficiently as possible.<ref>Don Wells. All Rights reserved.
	~~Last modified October 8, 2013. Extreme Programming:~~
	~~A gentle introduction~~. [ONLINE] Available at: "http://www.extremeprogramming.org/"</ref>.

	==Limitation==		==Limitation==

Hoda.vn: /* Big idea */

2018-02-28T17:51:48Z

Big idea

← Older revision		Revision as of 17:51, 28 February 2018
Line 17:		Line 17:
	The commonest way for the technical and management staff is to start a conversation with the business people, to ask them questions about what they have in mind, the needs and something like that. We keep doing that until we have a complete understanding of their expectations and when we are sure that we know their expectations, then we consider a product that can meet those expectations. Now we have the product and we create a plan that can help us create that product. Then we start the project and throughout the project, our goal is to follow the plan. Because that is probably, the best way we can realize that product.		The commonest way for the technical and management staff is to start a conversation with the business people, to ask them questions about what they have in mind, the needs and something like that. We keep doing that until we have a complete understanding of their expectations and when we are sure that we know their expectations, then we consider a product that can meet those expectations. Now we have the product and we create a plan that can help us create that product. Then we start the project and throughout the project, our goal is to follow the plan. Because that is probably, the best way we can realize that product.
	You usually have some deviations that it is completely normal and is ok. you have to have a monitoring and controlling system to understand the deviations and remove them and get back on track.		You usually have some deviations that it is completely normal and is ok. you have to have a monitoring and controlling system to understand the deviations and remove them and get back on track.
	After a while you get to the end and create a product as it was planned and designed upfront. You will show it to the business people. in certain cases, in some projects, when you do that, you realize the expectations for something else that you could not understand the expectations before		After a while you get to the end and create a product as it was planned and designed upfront. You will show it to the business people. in certain cases, in some projects, when you do that, you realize the expectations for something else that you could not understand the expectations before.

	It does not happen in every project. When you want to construct a building or when you want to build a bridge, you can understand the expectation from the beginning and then plan everything and create the product and everyone will be happy. But in some projects, such as IT development, it does not usually happen. Cases are different. As it is very common, how can we prevent it from happening? how can we solve this problem?.		It does not happen in every project. When you want to construct a building or when you want to build a bridge, you can understand the expectation from the beginning and then plan everything and create the product and everyone will be happy. But in some projects, such as IT development, it does not usually happen. Cases are different. As it is very common, how can we prevent it from happening? how can we solve this problem?.

Hoda.vn: /* DSDM */

2018-02-28T17:47:07Z

DSDM

← Older revision		Revision as of 17:47, 28 February 2018
Line 118:		Line 118:

	'''''The DSDM Consortium''''' published the first version of '''''DSDM''''' in 1994; around the same time as XP and Scrum.		'''''The DSDM Consortium''''' published the first version of '''''DSDM''''' in 1994; around the same time as XP and Scrum.
	'''''DSDM''''' has been designed to be compatible with generic project management methods, especially PRINCE2®. That makes '''''DSDM''''' different from lightweight frameworks like Scrum.<ref>Wikipedia. Dynamic systems development method. [ONLINE] Available at: "https://en.wikipedia.org/wiki/Dynamic_systems_development_method#References"</ref>.		'''''DSDM''''' has been designed to be compatible with generic project management methods, especially PRINCE2®. That makes '''''DSDM''''' different from lightweight frameworks like Scrum. '''''DSDM''''' is an agile method that encompass all the activities being done during the project life cycle. It is based on repetitive approach that principles of agile development make the important part of it. It include the everyday users and customer involvement.<ref>Wikipedia. Dynamic systems development method. [ONLINE] Available at: "https://en.wikipedia.org/wiki/Dynamic_systems_development_method#References"</ref>.

	====XP====		====XP====

Hoda.vn: /* Agile Planning */

2018-02-28T17:38:01Z

Agile Planning

← Older revision		Revision as of 17:38, 28 February 2018
Line 71:		Line 71:
	-In stage 7, '''''the sprint retrospective''''' need to be held by the '''''scrum team''''' at the end of each sprint. In this stage, the scrum team discusses about their processes and environment during the sprint . It can help them to improve their process for the next sprint.		-In stage 7, '''''the sprint retrospective''''' need to be held by the '''''scrum team''''' at the end of each sprint. In this stage, the scrum team discusses about their processes and environment during the sprint . It can help them to improve their process for the next sprint.

	'''''The Roadmap To Value''''' can be repeated ~~with~~ in each stage which contains planning activities.<ref name=agile> Mark C. Layton and		'''''The Roadmap To Value''''' can be repeated in each stage which contains planning activities.<ref name=agile> Mark C. Layton and
	Steven J Ostermiller \| 2017 \| "Agile Project Management For Dummies®, 2nd Edition" </ref><ref>Emerson Taymor. Agile Handbook. [ONLINE] Available at: "http://agilehandbook.com/agile-handbook.pdf"</ref>.		Steven J Ostermiller \| 2017 \| "Agile Project Management For Dummies®, 2nd Edition" </ref><ref>Emerson Taymor. Agile Handbook. [ONLINE] Available at: "http://agilehandbook.com/agile-handbook.pdf"</ref>.

Hoda.vn: /* Agile Planning */

2018-02-28T17:32:04Z

Agile Planning

← Older revision		Revision as of 17:32, 28 February 2018
Line 49:		Line 49:
	'''''The Roadmap To Value''''' is a great approach to look at the '''''planning tasks''''' in '''''Agile Projects''''', which occurs at a number of points.		'''''The Roadmap To Value''''' is a great approach to look at the '''''planning tasks''''' in '''''Agile Projects''''', which occurs at a number of points.

	[[File:The Road map to value.png\|frame\|center\|1000*1000px\|Stages of agile planning and execution with the Roadmap to Value.. Adapted from <ref ~~name=~~"~~agile~~"/>]]		[[File:The Road map to value.png\|frame\|center\|1000*1000px\|Stages of agile planning and execution with the Roadmap to Value.. Adapted from <ref > Mark C. Layton and
			Steven J Ostermiller \| 2017 \| "Agile Project Management For Dummies®, 2nd Edition" page 118 </ref>]]


Line 71:		Line 72:

	'''''The Roadmap To Value''''' can be repeated with in each stage which contains planning activities.<ref name=agile> Mark C. Layton and		'''''The Roadmap To Value''''' can be repeated with in each stage which contains planning activities.<ref name=agile> Mark C. Layton and
	Steven J Ostermiller \| 2017 \| "Agile Project Management For Dummies®, 2nd Edition" </ref>,<ref>Emerson Taymor. Agile Handbook. [ONLINE] Available at: "http://agilehandbook.com/agile-handbook.pdf"</ref>.		Steven J Ostermiller \| 2017 \| "Agile Project Management For Dummies®, 2nd Edition" </ref><ref>Emerson Taymor. Agile Handbook. [ONLINE] Available at: "http://agilehandbook.com/agile-handbook.pdf"</ref>.

	===Control schedule in agile approach===		===Control schedule in agile approach===

Hoda.vn: /* Application */

2018-02-28T17:25:03Z

Application

← Older revision		Revision as of 17:25, 28 February 2018
Line 41:		Line 41:
	In '''''Agile projects''''', whole project should be divided in smaller segment called '''''iterations''''' to accommodate frequent inspection and immediate adjustments.		In '''''Agile projects''''', whole project should be divided in smaller segment called '''''iterations''''' to accommodate frequent inspection and immediate adjustments.
	This approach, involves the same type of work as in a '''''traditional waterfall project''''' : creating requirements and designs, improving the product, documenting it and if necessary, integrating the product with other products. After that, testing the product, solving any problems, and deploying it for use.		This approach, involves the same type of work as in a '''''traditional waterfall project''''' : creating requirements and designs, improving the product, documenting it and if necessary, integrating the product with other products. After that, testing the product, solving any problems, and deploying it for use.
	But in '''''Agile approach'''''project manager need to break these steps for all product features in the project into iterations, also called '''''sprints''''',		But in '''''Agile approach''''' project manager need to break these steps for all product features in the project into iterations, also called '''''sprints''''',
	instead of completing these at once, as in a waterfall project.		instead of completing these at once, as in a waterfall project.
	Since the creators of the '''''Agile Manifesto''''' worked in the IT industry, they originally focused on software development.		Since the creators of the '''''Agile Manifesto''''' worked in the IT industry, they originally focused on software development.

Hoda.vn: /* Application */

2018-02-28T17:24:32Z

Application

← Older revision		Revision as of 17:24, 28 February 2018
Line 40:		Line 40:
	Decision making in '''''Agile approaches''''', are based on an '''''empirical control method''''' and the real observation during the project. This method can affect project to improve and upgrade projects. In this method, project manager, by using frequent and inspection of the project to date, can make immediate adjustments, if necessary.		Decision making in '''''Agile approaches''''', are based on an '''''empirical control method''''' and the real observation during the project. This method can affect project to improve and upgrade projects. In this method, project manager, by using frequent and inspection of the project to date, can make immediate adjustments, if necessary.
	In '''''Agile projects''''', whole project should be divided in smaller segment called '''''iterations''''' to accommodate frequent inspection and immediate adjustments.		In '''''Agile projects''''', whole project should be divided in smaller segment called '''''iterations''''' to accommodate frequent inspection and immediate adjustments.
	This approach, involves the same type of work as in a '''''traditional waterfall project''''': creating requirements and designs, improving the product, documenting it and if necessary, integrating the product with other products. After that, testing the product, solving any problems, and deploying it for use.		This approach, involves the same type of work as in a '''''traditional waterfall project''''' : creating requirements and designs, improving the product, documenting it and if necessary, integrating the product with other products. After that, testing the product, solving any problems, and deploying it for use.
	But in '''''Agile approach'''''project manager need to break these steps for all product features in the project into iterations, also called '''''sprints''''',		But in '''''Agile approach'''''project manager need to break these steps for all product features in the project into iterations, also called '''''sprints''''',
	instead of completing these at once, as in a waterfall project.		instead of completing these at once, as in a waterfall project.