Agile (Adaptive) model - Revision history

S175382: /* Big Idea */

2022-03-27T17:01:30Z

Big Idea

← Older revision		Revision as of 17:01, 27 March 2022
Line 10:		Line 10:
	==Big Idea==		==Big Idea==

	Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”<ref name="No more"> Rainer Züst, Peter Troxler (2006), NO MORE MUDDLING THROUGH: Mastering Complex Projects in Engineering and Management </ref>.		Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”<ref name="No more"> Rainer Züst, Peter Troxler (2006), NO MORE MUDDLING THROUGH: Mastering Complex Projects in Engineering and Management </ref>

	Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods would be a great match.		Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods would be a great match.

S175382: /* Big Idea */

2022-03-27T17:01:20Z

Big Idea

← Older revision		Revision as of 17:01, 27 March 2022
Line 10:		Line 10:
	==Big Idea==		==Big Idea==

	Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”. (~~Kilde~~)		Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”<ref name="No more"> Rainer Züst, Peter Troxler (2006), NO MORE MUDDLING THROUGH: Mastering Complex Projects in Engineering and Management </ref>.

	Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods would be a great match.		Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods would be a great match.

S175382: /* Big Idea */

2022-03-27T16:58:00Z

Big Idea

← Older revision		Revision as of 16:58, 27 March 2022
Line 12:		Line 12:
	Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”. (Kilde)		Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”. (Kilde)

	Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods ~~are~~ a great match.		Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods would be a great match.

	===The Agile Manifesto===		===The Agile Manifesto===

S175382: /* Big Idea */

2022-03-27T16:57:10Z

Big Idea

← Older revision		Revision as of 16:57, 27 March 2022
Line 11:		Line 11:

	Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”. (Kilde)		Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”. (Kilde)

	Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods are a great match.		Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods are a great match.

S175382: /* Big Idea */

2022-03-27T16:56:56Z

Big Idea

← Older revision		Revision as of 16:56, 27 March 2022
Line 9:		Line 9:

	==Big Idea==		==Big Idea==

			Rainer Züst and Peter Troxler describe the importance of considering time-related changes in planning. As they describe it, systems and their environment change over time. It can influence the product's design and force the development team to make changes. One of R. Züst and P. Troxler’s suggestions to time-related changes is: “Recognise future changes in the system and environment and account for them in the planning process: Analyses of the past, the present and the future have to be integrated in the planning process.”. (Kilde)
			Another suggestion could be to use an agile approach. Instead of analyzing the past, present and the future, and using a lot of time to make plans for it, the team could use a framework that is ready to adapt to changes. For this, agile methods are a great match.

	===The Agile Manifesto===		===The Agile Manifesto===

S175382: /* Daily Stand up */

2022-03-22T21:45:36Z

Daily Stand up

← Older revision		Revision as of 21:45, 22 March 2022
Line 100:		Line 100:

	The overall goal of the Daily Scrum is to discuss the ongoing process and how well the team is doing toward reaching the Sprint Goal. If necessary, the team may adapt and adjust their upcoming work. Last, the developer team has to develop an actionable plan for the next day of work.		The overall goal of the Daily Scrum is to discuss the ongoing process and how well the team is doing toward reaching the Sprint Goal. If necessary, the team may adapt and adjust their upcoming work. Last, the developer team has to develop an actionable plan for the next day of work.
	The scrum guide describes the reason for having Daily Scrum as: “Daily Scrums improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings.“~~(6)~~		The scrum guide describes the reason for having Daily Scrum as: “Daily Scrums improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings.“ <ref name="scrum 2"/>

	======Sprint Review======		======Sprint Review======

S175382: /* The Project Owner */

2022-03-22T21:44:29Z

The Project Owner

← Older revision		Revision as of 21:44, 22 March 2022
Line 141:		Line 141:

	=====The Project Owner=====		=====The Project Owner=====
	In a project, there can only be one person as the Project Owner. The Project Owner (PO) is, in the end, the person who is responsible for the product and responsible for getting the most value out of the job done. The PO has mainly two tasks to be accountable for, the overall project goal and the Product Backlog. The PO’s task is:		In a project, there can only be one person as the Project Owner. The Project Owner (PO) is, in the end, the person who is responsible for the product and responsible for getting the most value out of the job done. The PO has mainly two tasks to be accountable for, the overall project goal and the Product Backlog. The PO’s task is: <ref name="scrum guide"/>

S175382: /* Scrum Master */

2022-03-22T21:44:20Z

Scrum Master

← Older revision		Revision as of 21:44, 22 March 2022
Line 129:		Line 129:
	In each Scrum Team, there should be one Project Owner, one Scrum Master, and several Developers. When using the Scrum framework, it is important to have a small cross functional team. Meaning that the team members together should have all the skills necessary to complete the work in each sprint. The Scrum Team should be able to manage all types of tasks like research, development, maintenance etc. The team should be small enough to manoeuvre quickly and have good communication, but big enough to complete the job in each sprint. A rule of thumb is that the team should not exceed the number of 10 people. If the number exceeds 10 people, it is possible to divide the team into two Scrum Teams working on the same project but sharing Project Owner and Project Backlog to ensure that they are not doing the same work twice.<ref name="scrum guide"/>		In each Scrum Team, there should be one Project Owner, one Scrum Master, and several Developers. When using the Scrum framework, it is important to have a small cross functional team. Meaning that the team members together should have all the skills necessary to complete the work in each sprint. The Scrum Team should be able to manage all types of tasks like research, development, maintenance etc. The team should be small enough to manoeuvre quickly and have good communication, but big enough to complete the job in each sprint. A rule of thumb is that the team should not exceed the number of 10 people. If the number exceeds 10 people, it is possible to divide the team into two Scrum Teams working on the same project but sharing Project Owner and Project Backlog to ensure that they are not doing the same work twice.<ref name="scrum guide"/>
	=====Scrum Master=====		=====Scrum Master=====
	The Scrum Master is one person and is the leader within the team. The Scrum Master is accountable for setting up the Scrum Framework and ensuring that everyone in the team understands the Scrum theory and practice. In addition, the Scrum Master is accountable for:		The Scrum Master is one person and is the leader within the team. The Scrum Master is accountable for setting up the Scrum Framework and ensuring that everyone in the team understands the Scrum theory and practice. In addition, the Scrum Master is accountable for: <ref name="scrum guide"/>

S175382: /* Increment */

2022-03-22T21:44:05Z

Increment

← Older revision		Revision as of 21:44, 22 March 2022
Line 124:		Line 124:
	=====Increment =====		=====Increment =====

	An Increment is a finished task from the Product Backlog. An item from the Product Backlog becomes an Increment when it reaches the Definition of Done. Definition of Done is the quality measurement decided by the organization. First, when the item meets the Definition of Done, it can be presented in the Sprint Review. Otherwise, it will go back into the Product Backlog.		An Increment is a finished task from the Product Backlog. An item from the Product Backlog becomes an Increment when it reaches the Definition of Done. Definition of Done is the quality measurement decided by the organization. First, when the item meets the Definition of Done, it can be presented in the Sprint Review. Otherwise, it will go back into the Product Backlog. <ref name="scrum guide"/>

	====The Scrum Team====		====The Scrum Team====

S175382: /* Sprint Backlog */

2022-03-22T21:43:56Z

Sprint Backlog

← Older revision		Revision as of 21:43, 22 March 2022
Line 120:		Line 120:
	=====Sprint Backlog=====		=====Sprint Backlog=====

	The Sprint Backlog is composed of three things: the Sprint goal (why), selected items from the backlog (what), and a plan for reaching the goal (how).		The Sprint Backlog is composed of three things: the Sprint goal (why), selected items from the backlog (what), and a plan for reaching the goal (how). <ref name="scrum guide"/>

	=====Increment =====		=====Increment =====