http://13.50.150.85/api.php?action=feedcontributions&feedformat=atom&user=HannibalDanielsen 2026-07-16T09:14:55Z User contributions MediaWiki 1.43.3 http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122594 2022-03-27T19:49:54Z

<p>HannibalDanielsen: /* Why use SCRUM */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset. <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint, by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values.<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model. There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner.<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> <br /> The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> The sprint backlog is created by the development team when the sprint planning is taken place. This plan is consisting of goals which explains why it is valuable. Here items from the product backlog is used to define what work should be done to reach an increment. The main focus of the sprint backlog should be transparency a visibility so they are easy to read and understand. There are many different tools which can used and help with the visibility. A tool here can be a Kanban board. A Kanban board can help the team visualize where they are in the process and what actions is the next to come to help them fulfill the increment. When the sprint is taking place and the work is overviewed during the daily SCRUM meetings adjustments can be made.<br /> <br /> == Limitations ==<br /> <br /> As explained SCRUM is a very valuable framework and can be used regarding many different projects but of course have downfalls and cannot always be applicable. In cases where it is not applicable is projects which by their nature is not that complex. In these less complex projects all the iterations and many feedback loops will not necessarily be generate value where a more straight forward approach will be of better use. <br /> <br /> As a general theme through the SCRUM framework it is highly necessary that the team who is doing the project need to have certain prementioned skills such as being self-organized, etc. if these things are not present and the team is not on the same page and understand the framework of SCRUM it will run in to a pitfall.<br /> <br /> Last but not least the biggest issue when it comes to implementing SCRUM in an organization is the cultural change it brings with it. As a company you cannot just pick up SCRUM and simply implement it during a project to managing tool and framework. For many people who have not been working with the framework and the philosophy before it is an entirely new way of thinking. So to probably use the SCRUM framework a slowly and time consuming training and education is needed to fully benefit from it.<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.<br /> <br /> 3. What Is Scrum in Project Management?: https://www.youtube.com/watch?v=M12HSYZkrgQ<br /> <br /> 4. Agile project management with Scrum: https://www.pmi.org/learning/library/agile-project-management-scrum-6269</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122593 2022-03-27T19:49:41Z

<p>HannibalDanielsen: /* History of SCRUM */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset. <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint, by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values.<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> <br /> The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> The sprint backlog is created by the development team when the sprint planning is taken place. This plan is consisting of goals which explains why it is valuable. Here items from the product backlog is used to define what work should be done to reach an increment. The main focus of the sprint backlog should be transparency a visibility so they are easy to read and understand. There are many different tools which can used and help with the visibility. A tool here can be a Kanban board. A Kanban board can help the team visualize where they are in the process and what actions is the next to come to help them fulfill the increment. When the sprint is taking place and the work is overviewed during the daily SCRUM meetings adjustments can be made.<br /> <br /> == Limitations ==<br /> <br /> As explained SCRUM is a very valuable framework and can be used regarding many different projects but of course have downfalls and cannot always be applicable. In cases where it is not applicable is projects which by their nature is not that complex. In these less complex projects all the iterations and many feedback loops will not necessarily be generate value where a more straight forward approach will be of better use. <br /> <br /> As a general theme through the SCRUM framework it is highly necessary that the team who is doing the project need to have certain prementioned skills such as being self-organized, etc. if these things are not present and the team is not on the same page and understand the framework of SCRUM it will run in to a pitfall.<br /> <br /> Last but not least the biggest issue when it comes to implementing SCRUM in an organization is the cultural change it brings with it. As a company you cannot just pick up SCRUM and simply implement it during a project to managing tool and framework. For many people who have not been working with the framework and the philosophy before it is an entirely new way of thinking. So to probably use the SCRUM framework a slowly and time consuming training and education is needed to fully benefit from it.<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.<br /> <br /> 3. What Is Scrum in Project Management?: https://www.youtube.com/watch?v=M12HSYZkrgQ<br /> <br /> 4. Agile project management with Scrum: https://www.pmi.org/learning/library/agile-project-management-scrum-6269</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122592 2022-03-27T19:49:13Z

<p>HannibalDanielsen: /* References */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> <br /> The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> The sprint backlog is created by the development team when the sprint planning is taken place. This plan is consisting of goals which explains why it is valuable. Here items from the product backlog is used to define what work should be done to reach an increment. The main focus of the sprint backlog should be transparency a visibility so they are easy to read and understand. There are many different tools which can used and help with the visibility. A tool here can be a Kanban board. A Kanban board can help the team visualize where they are in the process and what actions is the next to come to help them fulfill the increment. When the sprint is taking place and the work is overviewed during the daily SCRUM meetings adjustments can be made.<br /> <br /> == Limitations ==<br /> <br /> As explained SCRUM is a very valuable framework and can be used regarding many different projects but of course have downfalls and cannot always be applicable. In cases where it is not applicable is projects which by their nature is not that complex. In these less complex projects all the iterations and many feedback loops will not necessarily be generate value where a more straight forward approach will be of better use. <br /> <br /> As a general theme through the SCRUM framework it is highly necessary that the team who is doing the project need to have certain prementioned skills such as being self-organized, etc. if these things are not present and the team is not on the same page and understand the framework of SCRUM it will run in to a pitfall.<br /> <br /> Last but not least the biggest issue when it comes to implementing SCRUM in an organization is the cultural change it brings with it. As a company you cannot just pick up SCRUM and simply implement it during a project to managing tool and framework. For many people who have not been working with the framework and the philosophy before it is an entirely new way of thinking. So to probably use the SCRUM framework a slowly and time consuming training and education is needed to fully benefit from it.<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.<br /> <br /> 3. What Is Scrum in Project Management?: https://www.youtube.com/watch?v=M12HSYZkrgQ<br /> <br /> 4. Agile project management with Scrum: https://www.pmi.org/learning/library/agile-project-management-scrum-6269</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122589 2022-03-27T19:48:03Z

<p>HannibalDanielsen: /* References */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> <br /> The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> The sprint backlog is created by the development team when the sprint planning is taken place. This plan is consisting of goals which explains why it is valuable. Here items from the product backlog is used to define what work should be done to reach an increment. The main focus of the sprint backlog should be transparency a visibility so they are easy to read and understand. There are many different tools which can used and help with the visibility. A tool here can be a Kanban board. A Kanban board can help the team visualize where they are in the process and what actions is the next to come to help them fulfill the increment. When the sprint is taking place and the work is overviewed during the daily SCRUM meetings adjustments can be made.<br /> <br /> == Limitations ==<br /> <br /> As explained SCRUM is a very valuable framework and can be used regarding many different projects but of course have downfalls and cannot always be applicable. In cases where it is not applicable is projects which by their nature is not that complex. In these less complex projects all the iterations and many feedback loops will not necessarily be generate value where a more straight forward approach will be of better use. <br /> <br /> As a general theme through the SCRUM framework it is highly necessary that the team who is doing the project need to have certain prementioned skills such as being self-organized, etc. if these things are not present and the team is not on the same page and understand the framework of SCRUM it will run in to a pitfall.<br /> <br /> Last but not least the biggest issue when it comes to implementing SCRUM in an organization is the cultural change it brings with it. As a company you cannot just pick up SCRUM and simply implement it during a project to managing tool and framework. For many people who have not been working with the framework and the philosophy before it is an entirely new way of thinking. So to probably use the SCRUM framework a slowly and time consuming training and education is needed to fully benefit from it.<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.<br /> <br /> 3. What Is Scrum in Project Management?: https://www.youtube.com/watch?v=M12HSYZkrgQ</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122581 2022-03-27T19:46:37Z

<p>HannibalDanielsen: /* Limitations */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> <br /> The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> The sprint backlog is created by the development team when the sprint planning is taken place. This plan is consisting of goals which explains why it is valuable. Here items from the product backlog is used to define what work should be done to reach an increment. The main focus of the sprint backlog should be transparency a visibility so they are easy to read and understand. There are many different tools which can used and help with the visibility. A tool here can be a Kanban board. A Kanban board can help the team visualize where they are in the process and what actions is the next to come to help them fulfill the increment. When the sprint is taking place and the work is overviewed during the daily SCRUM meetings adjustments can be made.<br /> <br /> == Limitations ==<br /> <br /> As explained SCRUM is a very valuable framework and can be used regarding many different projects but of course have downfalls and cannot always be applicable. In cases where it is not applicable is projects which by their nature is not that complex. In these less complex projects all the iterations and many feedback loops will not necessarily be generate value where a more straight forward approach will be of better use. <br /> <br /> As a general theme through the SCRUM framework it is highly necessary that the team who is doing the project need to have certain prementioned skills such as being self-organized, etc. if these things are not present and the team is not on the same page and understand the framework of SCRUM it will run in to a pitfall.<br /> <br /> Last but not least the biggest issue when it comes to implementing SCRUM in an organization is the cultural change it brings with it. As a company you cannot just pick up SCRUM and simply implement it during a project to managing tool and framework. For many people who have not been working with the framework and the philosophy before it is an entirely new way of thinking. So to probably use the SCRUM framework a slowly and time consuming training and education is needed to fully benefit from it.<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122488 2022-03-27T18:41:04Z

<p>HannibalDanielsen: /* 2. Sprint Backlog */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> <br /> The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> The sprint backlog is created by the development team when the sprint planning is taken place. This plan is consisting of goals which explains why it is valuable. Here items from the product backlog is used to define what work should be done to reach an increment. The main focus of the sprint backlog should be transparency a visibility so they are easy to read and understand. There are many different tools which can used and help with the visibility. A tool here can be a Kanban board. A Kanban board can help the team visualize where they are in the process and what actions is the next to come to help them fulfill the increment. When the sprint is taking place and the work is overviewed during the daily SCRUM meetings adjustments can be made.<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122406 2022-03-27T17:27:04Z

<p>HannibalDanielsen: /* 1. Product Backlog */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> <br /> The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122402 2022-03-27T17:19:32Z

<p>HannibalDanielsen: /* SCRUM Artifacts */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> <br /> The SCRUM artifacts is what indicates value and will in a whole increase transparency. <br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122401 2022-03-27T17:17:51Z

<p>HannibalDanielsen: /* References */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122400 2022-03-27T17:17:24Z

<p>HannibalDanielsen: /* 4. Sprint Retrospective */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> <br /> As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122397 2022-03-27T17:13:30Z

<p>HannibalDanielsen: /* 3. Sprint Review */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product does not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122396 2022-03-27T17:12:49Z

<p>HannibalDanielsen: /* 3. Sprint Review */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> <br /> In the sprint review phase the team demonstrate to the relevant stakeholders what items they have completed according to the backlog items. This is the phase where the product owner has the leading role since this person is the one with direct relations to the different stakeholders. Here the development team also get to showcase prototypes of the product. If the project e.g. is dealing with software the current features or core idea of the function can be shown. If the product do not meet the required goals and the stakeholders are not satisfied with the outcome the product backlog will be adjusted so it will meet the goal.<br /> <br /> ==== 4. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122377 2022-03-27T17:03:59Z

<p>HannibalDanielsen: /* References */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> Insert text<br /> <br /> ==== 4. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> <br /> 2.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122376 2022-03-27T17:03:48Z

<p>HannibalDanielsen: /* References */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> Insert text<br /> <br /> ==== 4. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> <br /> 1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.<br /> 2.</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122362 2022-03-27T16:45:21Z

<p>HannibalDanielsen: /* 2. Daily SCRUM */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> <br /> Regarding the daily SCRUM it is a meeting which is taken place every day at the same time and takes a maximum of 15 minutes. The reasoning for this is that everybody can keep track of progress of the project. Furthermore, these meetings also ensure that everybody in the team have the opportunity to communicate and promote any potential risk and issues which then can be addressed quickly.<br /> <br /> ==== 3. Sprint Review ====<br /> Insert text<br /> <br /> ==== 4. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122358 2022-03-27T16:39:12Z

<p>HannibalDanielsen: </p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 3. Sprint Review ====<br /> Insert text<br /> <br /> ==== 4. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122357 2022-03-27T16:38:57Z

<p>HannibalDanielsen: /* 3. Daily SCRUM */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122356 2022-03-27T16:38:40Z

<p>HannibalDanielsen: /* 2. Sprint Planning */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=122354 2022-03-27T16:37:37Z

<p>HannibalDanielsen: /* 1. Sprints */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> <br /> Sprints in SCRUM are the foundation. They usually take two to four weeks where the ideas made by the development team turns into value so the sprint goal can be achieved. By making sure that these sprints are not any longer ensures that the engagement and focus from the team is still present. The sprint itself consist of all the events described below but will briefly be touch upon. First the sprint will start with a sprint planning which purpose is to define the sprint backlog which are based on the sprint goals. After this work has been done the sprint itself can begin. During the sprint the SCRUM-master will daily host a meeting for the development team so information can be shared. The reasons for having these daily meetings helps out when it comes to transparency, predictability and decrease risk. The final step in the sprint is the sprint retrospective. Here the development team will have time to evaluate the things that went well or bad during the sprint, which they can eventually learn from for future sprints.<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121787 2022-03-24T14:53:06Z

<p>HannibalDanielsen: /* SCRUM Events */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> <br /> The soul core of the SCRUM is the events and is what that makes it agile since it creates a shared flow for the team. As previous mention the SCRUM framework in iterations. When the project owner has been able to define the scope of the project they are working on the first iteration of the sprint can begin. All the events involved in the sprint will be describes in detail further down.<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121786 2022-03-24T14:43:53Z

<p>HannibalDanielsen: </p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121785 2022-03-24T14:40:26Z

<p>HannibalDanielsen: /* SCRUM Values */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Values is what generate something that benefit something. Regarding SCRUM there is referred to five different types of values. These values are focus, respect, openness, commitment and courage. The values are made real through reaching and committing to the goals of the project while working and learning from the SCRUM framework. Since a project never runes into some inconvenient problem or issue these values serves as a important aspect when it comes to teamwork.<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121784 2022-03-24T14:40:10Z

<p>HannibalDanielsen: /* SCRUM Teams */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> <br /> The SCRUM team consist of different persons which will be describe in details below but mention here. These persons are the product owner (PO), the development team (DT) and the SCRUM-master (SM). All these persons are highly skilled in their field, people who can self-organize and are professional. The team will work together during the project and generate value during each sprint towards the finish product. <br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121782 2022-03-24T14:07:05Z

<p>HannibalDanielsen: /* 3. The SCRUM-Master */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> Insert text<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> The SCRUM-master differs from the product owner which task is to define why the project itself is necessary and the team which task is to define what is needed to be done in order to reach the desired value of the project. The master’s role is to define how they will reach the desired product, but most importantly the SCRUM-master are not to be managing the team in anyway. They are merely to be helping the team in any way that seems fit so the other people can be successful at their job.<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121781 2022-03-24T13:57:50Z

<p>HannibalDanielsen: /* 2. The Team */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> Insert text<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> <br /> The team which is also referred to as the development team can consist of a range of people up till nine, this of course depends on the project. These team members need to have certain necessary skills and expertise e.g. designers, analysts, developers, etc. so the finish product will be as desired. Furthermore, it is preferred that these team members can be working cross-functional and can organize themselves since this generate ownership of the project. The last but not least the team members need to be able to adapt and change during the project process if certain events might happen.<br /> <br /> ==== 3. The SCRUM-Master ====<br /> Insert text<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121778 2022-03-24T13:46:09Z

<p>HannibalDanielsen: /* 1. The Product Owner */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> Insert text<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> When trying to identify the product owner this person should have the ability to understand and interpretative the stakeholders needs and requirements in the Production Backlog. A product owner also needs to have certain trades as being communicative, good at prioritizing and have a strong personality since they will be the one leading. If these things are not done correctly the value of the outcome will be affected.<br /> <br /> ==== 2. The Team ====<br /> Insert text<br /> <br /> ==== 3. The SCRUM-Master ====<br /> Insert text<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121776 2022-03-24T13:34:07Z

<p>HannibalDanielsen: /* The Framework in a whole */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> <br /> Since every project every vary from one another the SCRUM framework needs to be modified so it fits the specific project. All the following steps will describe the basic required steps which needs to be performed to successful implement SCRUM framework into a project.<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> Insert text<br /> <br /> ==== 1. The Product Owner ====<br /> Insert text<br /> <br /> ==== 2. The Team ====<br /> Insert text<br /> <br /> ==== 3. The SCRUM-Master ====<br /> Insert text<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=121774 2022-03-24T13:28:24Z

<p>HannibalDanielsen: </p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.<br /> <br /> == The Framework in a whole ==<br /> Insert text<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> Insert text<br /> <br /> ==== 1. The Product Owner ====<br /> Insert text<br /> <br /> ==== 2. The Team ====<br /> Insert text<br /> <br /> ==== 3. The SCRUM-Master ====<br /> Insert text<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=110231 2022-02-20T22:08:27Z

<p>HannibalDanielsen: </p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> == The Framework in a whole ==<br /> Insert text<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> Insert text<br /> <br /> ==== 1. The Product Owner ====<br /> Insert text<br /> <br /> ==== 2. The Team ====<br /> Insert text<br /> <br /> ==== 3. The SCRUM-Master ====<br /> Insert text<br /> <br /> ==== 4. The Development Team ====<br /> Insert text<br /> <br /> === SCRUM Events ===<br /> Insert text<br /> <br /> ==== 1. Sprints ====<br /> Insert text<br /> <br /> ==== 2. Sprint Planning ====<br /> Insert text<br /> <br /> ==== 3. Daily SCRUM ====<br /> Insert text<br /> <br /> ==== 4. Sprint Review ====<br /> Insert text<br /> <br /> ==== 5. Sprint Retrospective ====<br /> Insert text<br /> <br /> === SCRUM Artifacts ===<br /> Insert text<br /> <br /> ==== 1. Product Backlog ====<br /> Insert text<br /> <br /> ==== 2. Sprint Backlog ====<br /> Insert text<br /> <br /> == Limitations ==<br /> Insert text<br /> <br /> == References ==<br /> Insert text</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=110226 2022-02-20T22:07:25Z

<p>HannibalDanielsen: /* SCRUM Values */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> Insert text<br /> <br /> === SCRUM Teams ===<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> ==== 2. The Team ====<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> ==== 4. The Development Team ====<br /> <br /> === SCRUM Events ===<br /> <br /> ==== 1. Sprints ====<br /> <br /> ==== 2. Sprint Planning ====<br /> <br /> ==== 3. Daily SCRUM ====<br /> <br /> ==== 4. Sprint Review ====<br /> <br /> ==== 5. Sprint Retrospective ====<br /> <br /> === SCRUM Artifacts ===<br /> <br /> ==== 1. Product Backlog ====<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109865 2022-02-20T20:30:23Z

<p>HannibalDanielsen: /* Why use SCRUM */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.<br /> <br /> == Application and Implementation ==<br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> ==== 2. The Team ====<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> ==== 4. The Development Team ====<br /> <br /> === SCRUM Events ===<br /> <br /> ==== 1. Sprints ====<br /> <br /> ==== 2. Sprint Planning ====<br /> <br /> ==== 3. Daily SCRUM ====<br /> <br /> ==== 4. Sprint Review ====<br /> <br /> ==== 5. Sprint Retrospective ====<br /> <br /> === SCRUM Artifacts ===<br /> <br /> ==== 1. Product Backlog ====<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109858 2022-02-20T20:27:27Z

<p>HannibalDanielsen: /* Why use SCRUM */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current marked which is a forever state of change.<br /> <br /> == Application and Implementation ==<br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> ==== 2. The Team ====<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> ==== 4. The Development Team ====<br /> <br /> === SCRUM Events ===<br /> <br /> ==== 1. Sprints ====<br /> <br /> ==== 2. Sprint Planning ====<br /> <br /> ==== 3. Daily SCRUM ====<br /> <br /> ==== 4. Sprint Review ====<br /> <br /> ==== 5. Sprint Retrospective ====<br /> <br /> === SCRUM Artifacts ===<br /> <br /> ==== 1. Product Backlog ====<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109649 2022-02-20T18:59:50Z

<p>HannibalDanielsen: /* Application and Implementation */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> == Application and Implementation ==<br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> ==== 2. The Team ====<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> ==== 4. The Development Team ====<br /> <br /> === SCRUM Events ===<br /> <br /> ==== 1. Sprints ====<br /> <br /> ==== 2. Sprint Planning ====<br /> <br /> ==== 3. Daily SCRUM ====<br /> <br /> ==== 4. Sprint Review ====<br /> <br /> ==== 5. Sprint Retrospective ====<br /> <br /> === SCRUM Artifacts ===<br /> <br /> ==== 1. Product Backlog ====<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109632 2022-02-20T18:47:15Z

<p>HannibalDanielsen: /* SCRUM Artifacts */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> == Application and Implementation == <br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> ==== 2. The Team ====<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> ==== 4. The Development Team ====<br /> <br /> === SCRUM Events ===<br /> <br /> ==== 1. Sprints ====<br /> <br /> ==== 2. Sprint Planning ====<br /> <br /> ==== 3. Daily SCRUM ====<br /> <br /> ==== 4. Sprint Review ====<br /> <br /> ==== 5. Sprint Retrospective ====<br /> <br /> === SCRUM Artifacts ===<br /> <br /> ==== 1. Product Backlog ====<br /> <br /> ==== 2. Sprint Backlog ====<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109627 2022-02-20T18:45:50Z

<p>HannibalDanielsen: /* SCRUM Events */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> == Application and Implementation == <br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> ==== 2. The Team ====<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> ==== 4. The Development Team ====<br /> <br /> === SCRUM Events ===<br /> <br /> ==== 1. Sprints ====<br /> <br /> ==== 2. Sprint Planning ====<br /> <br /> ==== 3. Daily SCRUM ====<br /> <br /> ==== 4. Sprint Review ====<br /> <br /> ==== 5. Sprint Retrospective ====<br /> <br /> === SCRUM Artifacts ===<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109624 2022-02-20T18:43:13Z

<p>HannibalDanielsen: /* SCRUM Teams */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> == Application and Implementation == <br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> ==== 1. The Product Owner ====<br /> <br /> ==== 2. The Team ====<br /> <br /> ==== 3. The SCRUM-Master ====<br /> <br /> ==== 4. The Development Team ====<br /> <br /> === SCRUM Events ===<br /> <br /> === SCRUM Artifacts ===<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109618 2022-02-20T18:40:36Z

<p>HannibalDanielsen: /* Why use SCRUM */</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> == Application and Implementation == <br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> === SCRUM Events ===<br /> <br /> === SCRUM Artifacts ===<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109614 2022-02-20T18:39:36Z

<p>HannibalDanielsen: </p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).<br /> <br /> <br /> <br /> == Application and Implementation == <br /> <br /> == The Framework in a whole ==<br /> <br /> === SCRUM Values ===<br /> <br /> === SCRUM Teams ===<br /> <br /> === SCRUM Events ===<br /> <br /> === SCRUM Artifacts ===<br /> <br /> == Limitations ==<br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109605 2022-02-20T18:35:43Z

<p>HannibalDanielsen: </p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset ([[insert reference]]). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values ([[insert reference]]).<br /> <br /> == Why use SCRUM ==<br /> So why do we really want to use the SCRUM model instead of the classic Waterfall model ([[Insert reference]]). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals.<br /> For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner ([[Insert reference]]).</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Managing_SCRUM&diff=109582 2022-02-20T18:24:01Z

<p>HannibalDanielsen: Created page with &quot;= Managing SCRUM = This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framewor...&quot;</p> <hr /> <div>= Managing SCRUM =<br /> <br /> This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master.<br /> Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.<br /> <br /> == History of SCRUM ==<br /> Back in the 1990’s the SCRUM framework was developed by Ken Schwaber &amp; Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset (insert reference). <br /> Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values (insert reference).<br /> <br /> == Why use SCRUM ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Articles_Spring_Term_2022&diff=109580 2022-02-20T18:22:02Z

<p>HannibalDanielsen: /* Overview of 2022 Wiki Collections */</p> <hr /> <div>=Overview of 2022 Wiki Collections=<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |+Spring Term 2022 Wiki Collections<br /> |Group 32<br /> |Nikoleta<br /> |Tsolaki<br /> |s212602<br /> |[[The Kaizen Method in Project Management]]<br /> |-<br /> |-<br /> |TAs Example<br /> |Thomas<br /> |Giannoulopoulos<br /> |s192419<br /> |[[APPM Example 2021]]<br /> |-<br /> |-<br /> |TAs Example<br /> |Daniel Rohrer<br /> |Hansen<br /> |s173922<br /> |[[Managing “emails”]]<br /> |-<br /> |-<br /> |Group 9<br /> |Andrea<br /> |Sánchez Díez<br /> |s202957<br /> |[[Urgent vs important. The Eisenhower matrix]]<br /> |-<br /> |-<br /> |Group 22<br /> |Edgars<br /> |Treimanis<br /> |s213590<br /> |[[Sustainable Project management]]<br /> |-<br /> |-<br /> |Group 31<br /> |William Taul<br /> |Madsen<br /> |s184956<br /> |[[Risk Treatment in project management]]<br /> |-<br /> |-<br /> |Group 12<br /> |Pablo Leandro<br /> |Capellari<br /> |s213666<br /> |[[Internal Rate of Return (IRR)]]<br /> |-<br /> |-<br /> |Group 15<br /> |Tolga<br /> |Azgun<br /> |s220502<br /> |[[Pooled, Sequential &amp; Reciprocal Interdependence]]<br /> |-<br /> |-<br /> |Group 15<br /> |Mathilde <br /> |Dahl <br /> |s176213 <br /> |[[Development Arena in Project Management]]<br /> |-<br /> |-<br /> |Group 19<br /> |Matias<br /> |Earthy-Find<br /> |s184350<br /> |[[Stress Management]]<br /> |-<br /> |-<br /> |Group 3<br /> |Stephen Akabekire<br /> |Azongo<br /> |s213057<br /> |[[The magic triangle as a project management tool in cost estimation and budgeting]]<br /> |-<br /> |-<br /> |Group 19<br /> |Wout<br /> |Jennissen<br /> |s216914<br /> |[[Porter's Five Forces Framework]]<br /> |-<br /> |-<br /> |Group 4<br /> |Sissel Albrecht<br /> |Kahr<br /> |s173964<br /> |[[Work Break Down Structure (WBS)]]<br /> |-<br /> |-<br /> |Group 15<br /> |Teis<br /> |Johannesen<br /> |s213561<br /> |[[Reflective practice]]<br /> |-<br /> |-<br /> |<br /> |Berta<br /> |Viñas<br /> |s202256<br /> |[[Agile model]]<br /> |-<br /> |-<br /> |Group 15<br /> |Christina<br /> |Qwist Frank<br /> |s173409<br /> |[[Staging negotiation spaces in project management]]<br /> |-<br /> |-<br /> |Group 15<br /> |Sara <br /> |Kristine Holmskov Eberle<br /> |s211691<br /> |[[Wheel of change]]<br /> |-<br /> |-<br /> |Group Name: TBD<br /> |Saaransh<br /> |PD Kattula<br /> |s210240<br /> |[[7 principles of Stephen covey for project mangers to tackle risks]]<br /> |-<br /> |-<br /> |Group Name: 47<br /> |Jakob Weber<br /> |Vestermark<br /> |s175072<br /> |[[Kanban method]]<br /> |-<br /> |-<br /> |Group Name: TBD<br /> |Jakob<br /> |Kehler<br /> |s212691<br /> |[[Post-Implementation Review (PIR)]]<br /> |-<br /> |-<br /> |Group Name: 47<br /> |Fie<br /> |Fredshavn Nielsen<br /> |s170396<br /> |[[Project dashboard]]<br /> |-<br /> |-<br /> |Group Name: 33<br /> |Alvaro<br /> |Martin Sanchez<br /> |s220145<br /> |[[Agile project management - SCRUM]]<br /> |-<br /> |-<br /> |Group Name: TBD<br /> |Mathias<br /> |Christensen<br /> |s175382<br /> |[[Agile (Adaptive) model]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Emilie<br /> |Haahr<br /> |s175383<br /> |[[Leadship vs Management Qualities]]<br /> |-<br /> |-<br /> |Group 22<br /> |Linda<br /> |Zviedre<br /> |s213817<br /> |[[Matrix Organizations]]<br /> |-<br /> |-<br /> |Group Name: 4<br /> |Casper<br /> |Stenbæk<br /> |s183504<br /> |[[Causes and effects of stress in project management]]<br /> |-<br /> |-<br /> |Group name<br /> |Sarah<br /> |Naegele<br /> |S220025<br /> |[[Communication models based on Schulz von Thun]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Sofie<br /> |Wallin<br /> |s173884<br /> |[[Sources of conflict]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Elias<br /> |Bobrowski<br /> |s216056<br /> |[[Management vs. Leadership Skills]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Luisa<br /> |Buchta<br /> |s216284<br /> |[[MTA (Milestone trend analysis)]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Frederik<br /> |Østergaard Schytte<br /> |s175075<br /> |[[Prioritizing in Projects with Eisenhower Decision Matrix]]<br /> |-<br /> |-<br /> |Group 40<br /> |Xenofon<br /> |Apostolou<br /> |s202908<br /> |[[Continuous Improvement (CI)]]<br /> |-<br /> |-<br /> |Group Name: 08<br /> |Periklis<br /> |Aprilis<br /> |s212866<br /> |[[FMEA as tool in Project Management]]<br /> |-<br /> |-<br /> |Group Name: <br /> |Nils<br /> |Lehmann<br /> |s220153<br /> |[[Effects of Social Loafing on Team Performance (due to low motivation)]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Olivia<br /> |Mark<br /> |s175096<br /> |[[Self-awareness in management]]<br /> |-<br /> |-<br /> |Group Name: <br /> |Paul<br /> |Schatt<br /> |s210736<br /> |[[Perception filters]]<br /> |-<br /> |-<br /> |Group name<br /> |Lorenzo<br /> |Incarnato<br /> |s220426<br /> |[[Internal rate of return (IRR)]]<br /> |-<br /> |-<br /> |Group Name: 40<br /> |Sasa<br /> |Javorac<br /> |s210770<br /> |[[Agile way of working]]<br /> |-<br /> |-<br /> |Group Name: 12<br /> |Elia<br /> |Simon<br /> |s212700<br /> |[[Extrinsic motivation]]<br /> |-<br /> |-<br /> |Group Name: <br /> |Swann<br /> |Roussillon<br /> |s212830<br /> |[[Robust Decision Making (RDM)]]<br /> |-<br /> |-<br /> |Group 09<br /> |Deepthi<br /> |Parana Liyanage Don<br /> |s203116<br /> |[[Net Present Value (NPV)]]<br /> |-<br /> |-<br /> |Group Name: 10<br /> |Felix<br /> |Piepenstock<br /> |s201828<br /> |[[Successive Cost Estimation]]<br /> |-<br /> |-<br /> |Group Name: 10<br /> |Julian<br /> |Schmidt<br /> |s213004<br /> |[[Social loafing]]<br /> |-<br /> |-<br /> |Group number: 22<br /> |Gustav<br /> |Gregersen<br /> |s153930<br /> |[[DMAIC Projects]]<br /> |-<br /> |-<br /> |Group 42<br /> |Simon<br /> |Widmer<br /> |s210449<br /> |[[Scaled Agile Framework (SAFe)]]<br /> |-<br /> |-<br /> |Group 17<br /> |Cosmina<br /> |Oltean<br /> |s212409<br /> |[[Team Cohesiveness]]<br /> |-<br /> |-<br /> |Group 12<br /> |Jasmine Riis<br /> |Douglas<br /> |s123367<br /> |[[How stress management improves the effectiveness of the employees]]<br /> |-<br /> |-<br /> |Group <br /> |Preetham <br /> |Obla Sampathkumar<br /> |s213604<br /> |[[Root cause analysis (RCA)]]<br /> |-<br /> |-<br /> |Group 4<br /> |Patrick <br /> |Laybourn<br /> |s144993<br /> |[[Robust decision making]]<br /> |-<br /> |-<br /> |Group 6<br /> |Gudrun<br /> |Gudnadottir<br /> |s212950<br /> |[[Risk-based Learning]]<br /> |-<br /> |-<br /> |Group 17<br /> |Andreea Bianca<br /> |Ladaru<br /> |s202438<br /> |[[Lean principles in the construction industry]]<br /> |-<br /> |-<br /> |Group 15<br /> |Lærke Viuff <br /> |Petersen<br /> |s163830<br /> |[[Social Loafing in Teams]]<br /> |-<br /> |-<br /> |Group 15<br /> |Stine Pagaard <br /> |Haahr<br /> |s152100<br /> |[[Conflict Management using the Thomas-Kilmann Conflict Mode Instrument (TKI)]]<br /> |-<br /> |-<br /> |Group 42<br /> |Nachanan<br /> |Wongsupakpun<br /> |s210284<br /> |[[Organizational context]]<br /> |-<br /> |-<br /> |Group 33<br /> |Guillermo<br /> |Roig Pitarch<br /> |s212754<br /> |[[Kanban: a project management framework]]<br /> |-<br /> |-<br /> |Group 29<br /> |Magnus<br /> |Leick<br /> |s213818<br /> |[[VUCA]]<br /> |-<br /> |-<br /> |Group 4<br /> |Freja Ejdrup<br /> |Andersen<br /> |s183631<br /> |[[The paradox of project planning from an uncertainty perspective]]<br /> |-<br /> |-<br /> |Group 9<br /> |Nongnapat<br /> |Suksusiang<br /> |s213572<br /> |[[New Product Introduction (NPI)]]<br /> |-<br /> |-<br /> |Group 31<br /> |Eigil<br /> |Vølund<br /> |s183887<br /> |[[Risk Treatment]]<br /> |-<br /> |-<br /> |Group 11<br /> |Ann Sofie<br /> |Grube Kjeldsen<br /> |s184535<br /> |[[Milestone trend analysis]]<br /> |-<br /> |-<br /> |Group 19<br /> |Qiushi <br /> |Lyu<br /> |s212543<br /> |[[Porter's 5 Forces - A strategic planning model]]<br /> |-<br /> |-<br /> |Group 9<br /> |Qifan <br /> |Wang<br /> |s212500<br /> |[[The Big Five(OCEAN) Personality Traits]]<br /> |-<br /> |-<br /> |Group 12<br /> |Hai <br /> |Hu<br /> |s212360<br /> |[[Kano Model: Introduction and Application]]<br /> |-<br /> |-<br /> |Group 32<br /> |Tobias<br /> |Nielsen<br /> |s220719<br /> |[[The paradox of project planning]]<br /> |-<br /> |-<br /> |Group 11<br /> |Hannah<br /> |Nissen<br /> |s184497<br /> |[[Effective teams with Belbin]]<br /> |-<br /> |-<br /> |Group 11 <br /> |Emil Engstrøm<br /> |Bruun<br /> |S180902<br /> |[[Adizes management styles]]<br /> |-<br /> |-<br /> |Group 33<br /> |Raquel <br /> |Galocha<br /> |S212745<br /> |[[Project interdependency mapping]]<br /> |-<br /> |-<br /> |Group 11 <br /> |Emilie <br /> |Rasmussen<br /> |S184532<br /> |[[WBS, Work Breakdown Structure]]<br /> |-<br /> |-<br /> |Group 6 <br /> |Telma Sigrún <br /> |Torfadóttir<br /> |S212566<br /> |[[Stress]]<br /> |-<br /> |-<br /> |-<br /> |-<br /> |Group 4 <br /> |Erlend Thabiso Rømyhr <br /> |Sehube<br /> |S212426<br /> |[[Risk treatment for renewable energy developers]]<br /> |-<br /> |-<br /> |Group 11 <br /> |Peter<br /> |Birkholm<br /> |S184514<br /> |[[Gantt Chart In Construction]]<br /> |-<br /> |-<br /> |Group 18 <br /> |Giacomo<br /> |Branchini<br /> |S212987<br /> |[[Sources of Conflict: Guidelines for a Healthy Organizational Environment]]<br /> |-<br /> |-<br /> |Group 33 <br /> |Paula<br /> |González<br /> |S213398<br /> |[[The Big Five (Ocean)]]<br /> |-<br /> |-<br /> |Group 33 <br /> |Fernando<br /> |Ramiro Gonzalez<br /> |S214134<br /> |[[MCDA methods in decision making]]<br /> |-<br /> |-<br /> |Group 20 <br /> |Magnus Stjernborg<br /> |Koch<br /> |S175189<br /> |[[Project Success and Project Management Success]]<br /> |-<br /> |-<br /> |Group 26<br /> |Katarzyna<br /> |Kukulowicz<br /> |S213042<br /> |[[Extrinsic and intrinsic motivation. What does the will to act depend on?]]<br /> |-<br /> |-<br /> |Group 6 <br /> |Hildur Lara <br /> |Jonsdottir<br /> |S212410<br /> |[[The Significance of Cohesiveness in Projects]]<br /> |-<br /> |-<br /> |Group 20<br /> |Ziwei<br /> |Chen<br /> |S212635<br /> |[[Stakeholder Identification and Categorization]]<br /> |-<br /> |-<br /> |Group 18<br /> |Raül<br /> |Ciscar<br /> |S217122<br /> |[[Developing a project with the Tuckman's model]]<br /> |-<br /> |-<br /> |Group 18<br /> |Giorgio<br /> |Galasso<br /> |S212985<br /> |[[Risk Assessment: framework for combining CBA and MCDA]]<br /> |-<br /> |-<br /> |Group 33<br /> |Maria Elena<br /> |Igarzabal Saborida<br /> |S213206<br /> |[[Intrinsic and Extrinsic motivation]]<br /> |-<br /> |-<br /> |Group 32<br /> |Aikaterini<br /> |Deli<br /> |s212459<br /> |[[The Technique of Value Engineering (VE) in Architecture]]<br /> |-<br /> |-<br /> |Group 08<br /> |Jiajing<br /> |Zhang<br /> |s212412<br /> |[[The Rolling-wave Planning]]<br /> |-<br /> |-<br /> |Group<br /> |Isera Sarah<br /> |Hajaj<br /> |s153540<br /> |[[Standard Operating Procedures (SOPs)]]<br /> |-<br /> |Group 50<br /> |Ibrahim<br /> |Nassrallah<br /> |s211254<br /> |[[Brain Storming Technique]]-<br /> |-<br /> |-<br /> |Group 29<br /> |Panagiotis<br /> |Bakas<br /> |s216860<br /> |[[Drexler/Sibbet Model for Team development and project management]]<br /> |-<br /> |-<br /> |Group 20<br /> |Dionysios<br /> |Maroulis<br /> |s212885<br /> |[[Adapting-Resilient Management]]<br /> |-<br /> |-<br /> |Group 32<br /> |Gabriela Miti<br /> |Tsuge Costa<br /> |s220075<br /> |[[Project loafing in Projects]]<br /> |-<br /> |-<br /> |Group 32<br /> |Helená Evin<br /> |Cinar<br /> |s164741<br /> |[[The use of SWOT analysis]]<br /> |-<br /> |-<br /> |Group 3<br /> |Pietro<br /> |Boschetto<br /> |s213928<br /> |[[Enterprise Risk Management]]<br /> |-<br /> |-<br /> |Group 3<br /> |Virginia<br /> |Stinchi<br /> |s213230<br /> |[[The Blake and Mouton's Managerial (Leadership) Grid]]<br /> |-<br /> |-<br /> |Group 32<br /> |César<br /> |Delafargue<br /> |s212834<br /> |[[Design validation]]<br /> |-<br /> |-<br /> |Group 11<br /> |Rune<br /> |Andersen<br /> |s180642<br /> |[[Creating effective teams by means of mathematical modelling]]<br /> |-<br /> |-<br /> |Group Name: 47<br /> |Hannibal<br /> |Danielsen<br /> |s154283<br /> |[[Managing SCRUM]]<br /> |-<br /> |Group 20<br /> |Kunyi<br /> |Yang<br /> |s220027<br /> |[[Wideband Delphi]]</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Manage_SCRUM&diff=108998 2022-02-20T14:41:06Z

<p>HannibalDanielsen: /* Summary of article */</p> <hr /> <div><br /> == Summary of article ==<br /> <br /> == Concept of the tool ==<br /> <br /> <br /> == Application of tool ==<br /> <br /> <br /> == Limitations of tool ==<br /> <br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Manage_SCRUM&diff=108971 2022-02-20T14:33:30Z

<p>HannibalDanielsen: Created page with &quot; == Summary of article == == Concept of the tool == == Application of tool == == Limitations of tool == == References ==&quot;</p> <hr /> <div><br /> == Summary of article ==<br /> <br /> <br /> <br /> <br /> == Concept of the tool ==<br /> <br /> <br /> == Application of tool ==<br /> <br /> <br /> == Limitations of tool ==<br /> <br /> <br /> == References ==</div>

HannibalDanielsen http://13.50.150.85/index.php?title=Articles_Spring_Term_2022&diff=108948 2022-02-20T14:22:24Z

<p>HannibalDanielsen: /* Overview of 2022 Wiki Collections */</p> <hr /> <div>=Overview of 2022 Wiki Collections=<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |+Spring Term 2022 Wiki Collections<br /> |Group 32<br /> |Nikoleta<br /> |Tsolaki<br /> |s212602<br /> |[[The Kaizen Method in Project Management]]<br /> |-<br /> |-<br /> |TAs Example<br /> |Thomas<br /> |Giannoulopoulos<br /> |s192419<br /> |[[APPM Example 2021]]<br /> |-<br /> |-<br /> |TAs Example<br /> |Daniel Rohrer<br /> |Hansen<br /> |s173922<br /> |[[Managing “emails”]]<br /> |-<br /> |-<br /> |Group 9<br /> |Andrea<br /> |Sánchez Díez<br /> |s202957<br /> |[[Urgent vs important. The Eisenhower matrix]]<br /> |-<br /> |-<br /> |Group 22<br /> |Edgars<br /> |Treimanis<br /> |s213590<br /> |[[Sustainable Project management]]<br /> |-<br /> |-<br /> |Group 31<br /> |William Taul<br /> |Madsen<br /> |s184956<br /> |[[Risk Treatment in project management]]<br /> |-<br /> |-<br /> |Group 15<br /> |Tolga<br /> |Azgun<br /> |s220502<br /> |[[Pooled, Sequential &amp; Reciprocal Interdependence]]<br /> |-<br /> |-<br /> |Group 15<br /> |Mathilde <br /> |Dahl <br /> |s176213 <br /> |[[Development Arena in Project Management]]<br /> |-<br /> |-<br /> |Group 19<br /> |Matias<br /> |Earthy-Find<br /> |s184350<br /> |[[Stress Management]]<br /> |-<br /> |-<br /> |Group 3<br /> |Stephen Akabekire<br /> |Azongo<br /> |s213057<br /> |[[The magic triangle as a project management tool in cost estimation and budgeting]]<br /> |-<br /> |-<br /> |Group 19<br /> |Wout<br /> |Jennissen<br /> |s216914<br /> |[[Porter's Five Forces Framework]]<br /> |-<br /> |-<br /> |Group 4<br /> |Sissel Albrecht<br /> |Kahr<br /> |s173964<br /> |[[Work Break Down Structure (WBS)]]<br /> |-<br /> |-<br /> |Group 15<br /> |Teis<br /> |Johannesen<br /> |s213561<br /> |[[Reflective practice]]<br /> |-<br /> |-<br /> |<br /> |Berta<br /> |Viñas<br /> |s202256<br /> |[[Agile model]]<br /> |-<br /> |-<br /> |Group 15<br /> |Christina<br /> |Qwist Frank<br /> |s173409<br /> |[[Staging negotiation spaces in project management]]<br /> |-<br /> |-<br /> |Group 15<br /> |Sara <br /> |Kristine Holmskov Eberle<br /> |s211691<br /> |[[Wheel of change]]<br /> |-<br /> |-<br /> |Group Name: TBD<br /> |Saaransh<br /> |PD Kattula<br /> |s210240<br /> |[[7 principles of Stephen covey for project mangers to tackle risks]]<br /> |-<br /> |-<br /> |Group Name: 47<br /> |Jakob Weber<br /> |Vestermark<br /> |s175072<br /> |[[Kanban method]]<br /> |-<br /> |-<br /> |Group Name: TBD<br /> |Jakob<br /> |Kehler<br /> |s212691<br /> |[[Post-Implementation Review (PIR)]]<br /> |-<br /> |-<br /> |Group Name: 47<br /> |Fie<br /> |Fredshavn Nielsen<br /> |s170396<br /> |[[Project dashboard]]<br /> |-<br /> |-<br /> |Group Name: 33<br /> |Alvaro<br /> |Martin Sanchez<br /> |s220145<br /> |[[Agile project management - SCRUM]]<br /> |-<br /> |-<br /> |Group Name: TBD<br /> |Mathias<br /> |Christensen<br /> |s175382<br /> |[[Agile (Adaptive) model]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Emilie<br /> |Haahr<br /> |s175383<br /> |[[Leadship vs Management Qualities]]<br /> |-<br /> |-<br /> |Group 22<br /> |Linda<br /> |Zviedre<br /> |s213817<br /> |[[Matrix Organizations]]<br /> |-<br /> |-<br /> |Group Name: 4<br /> |Casper<br /> |Stenbæk<br /> |s183504<br /> |[[Causes and effects of stress in project management]]<br /> |-<br /> |-<br /> |Group name<br /> |Sarah<br /> |Naegele<br /> |S220025<br /> |[[Communication models based on Schulz von Thun]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Sofie<br /> |Wallin<br /> |s173884<br /> |[[Sources of conflict]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Elias<br /> |Bobrowski<br /> |s216056<br /> |[[Management vs. Leadership Skills]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Luisa<br /> |Buchta<br /> |s216284<br /> |[[MTA (Milestone trend analysis)]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Frederik<br /> |Østergaard Schytte<br /> |s175075<br /> |[[Prioritizing in Projects with Eisenhower Decision Matrix]]<br /> |-<br /> |-<br /> |Group 40<br /> |Xenofon<br /> |Apostolou<br /> |s202908<br /> |[[Continuous Improvement (CI)]]<br /> |-<br /> |-<br /> |Group Name: 08<br /> |Periklis<br /> |Aprilis<br /> |s212866<br /> |[[FMEA as tool in Project Management]]<br /> |-<br /> |-<br /> |Group Name: <br /> |Nils<br /> |Lehmann<br /> |s220153<br /> |[[Effects of Social Loafing on Team Performance (due to low motivation)]]<br /> |-<br /> |-<br /> |Group Name:<br /> |Olivia<br /> |Mark<br /> |s175096<br /> |[[Self-awareness in management]]<br /> |-<br /> |-<br /> |Group Name: <br /> |Paul<br /> |Schatt<br /> |s210736<br /> |[[Perception filters]]<br /> |-<br /> |-<br /> |Group name<br /> |Lorenzo<br /> |Incarnato<br /> |s220426<br /> |[[Internal rate of return (IRR)]]<br /> |-<br /> |-<br /> |Group Name: 40<br /> |Sasa<br /> |Javorac<br /> |s210770<br /> |[[Agile way of working]]<br /> |-<br /> |-<br /> |Group Name: 12<br /> |Elia<br /> |Simon<br /> |s212700<br /> |[[Extrinsic motivation]]<br /> |-<br /> |-<br /> |Group Name: <br /> |Swann<br /> |Roussillon<br /> |s212830<br /> |[[Robust Decision Making (RDM)]]<br /> |-<br /> |-<br /> |Group 09<br /> |Deepthi<br /> |Parana Liyanage Don<br /> |s203116<br /> |[[Net Present Value (NPV)]]<br /> |-<br /> |-<br /> |Group Name: <br /> |Felix<br /> |Piepenstock<br /> |s201828<br /> |[[Successive Cost Estimation]]<br /> |-<br /> |-<br /> |Group Name: 10<br /> |Julian<br /> |Schmidt<br /> |s213004<br /> |[[Social loafing]]<br /> |-<br /> |-<br /> |Group number: 22<br /> |Gustav<br /> |Gregersen<br /> |s153930<br /> |[[DMAIC Projects]]<br /> |-<br /> |-<br /> |Group 42<br /> |Simon<br /> |Widmer<br /> |s210449<br /> |[[Scaled Agile Framework (SAFe)]]<br /> |-<br /> |-<br /> |Group 17<br /> |Cosmina<br /> |Oltean<br /> |s212409<br /> |[[Team Cohesiveness]]<br /> |-<br /> |-<br /> |Group 12<br /> |Jasmine Riis<br /> |Douglas<br /> |s123367<br /> |[[How stress management improves the effectiveness of the employees]]<br /> |-<br /> |-<br /> |Group <br /> |Preetham <br /> |Obla Sampathkumar<br /> |s213604<br /> |[[Root cause analysis (RCA)]]<br /> |-<br /> |-<br /> |Group 4<br /> |Patrick <br /> |Laybourn<br /> |s144993<br /> |[[Robust decision making]]<br /> |-<br /> |-<br /> |Group 6<br /> |Gudrun<br /> |Gudnadottir<br /> |s212950<br /> |[[Risk-based Learning]]<br /> |-<br /> |-<br /> |Group 17<br /> |Andreea Bianca<br /> |Ladaru<br /> |s202438<br /> |[[Lean principles in the construction industry]]<br /> |-<br /> |-<br /> |Group 15<br /> |Lærke Viuff <br /> |Petersen<br /> |s163830<br /> |[[Social Loafing in Teams]]<br /> |-<br /> |-<br /> |Group 15<br /> |Stine Pagaard <br /> |Haahr<br /> |s152100<br /> |[[Conflict Management using the Thomas-Kilmann Conflict Mode Instrument (TKI)]]<br /> |-<br /> |-<br /> |Group 42<br /> |Nachanan<br /> |Wongsupakpun<br /> |s210284<br /> |[[Organizational context]]<br /> |-<br /> |-<br /> |Group 33<br /> |Guillermo<br /> |Roig Pitarch<br /> |s212754<br /> |[[Kanban: a project management framework]]<br /> |-<br /> |-<br /> |Group 29<br /> |Magnus<br /> |Leick<br /> |s213818<br /> |[[VUCA]]<br /> |-<br /> |-<br /> |Group 4<br /> |Freja Ejdrup<br /> |Andersen<br /> |s183631<br /> |[[The paradox of project planning from an uncertainty perspective]]<br /> |-<br /> |-<br /> |Group 9<br /> |Nongnapat<br /> |Suksusiang<br /> |s213572<br /> |[[New Product Introduction (NPI)]]<br /> |-<br /> |-<br /> |Group 31<br /> |Eigil<br /> |Vølund<br /> |s183887<br /> |[[Risk Treatment]]<br /> |-<br /> |-<br /> |Group 11<br /> |Ann Sofie<br /> |Grube Kjeldsen<br /> |s184535<br /> |[[Milestone trend analysis]]<br /> |-<br /> |-<br /> |Group 19<br /> |Qiushi <br /> |Lyu<br /> |s212543<br /> |[[Porter's 5 Forces - A strategic planning model]]<br /> |-<br /> |-<br /> |Group 9<br /> |Qifan <br /> |Wang<br /> |s212500<br /> |[[The Big Five(OCEAN) Personality Traits]]<br /> |-<br /> |-<br /> |Group 12<br /> |Hai <br /> |Hu<br /> |s212360<br /> |[[Kano Model: Introduction and Application]]<br /> |-<br /> |-<br /> |Group 32<br /> |Tobias<br /> |Nielsen<br /> |s220719<br /> |[[The paradox of project planning]]<br /> |-<br /> |-<br /> |Group 11<br /> |Hannah<br /> |Nissen<br /> |s184497<br /> |[[Effective teams with Belbin]]<br /> |-<br /> |-<br /> |Group 11 <br /> |Emil Engstrøm<br /> |Bruun<br /> |S180902<br /> |[[Adizes management styles]]<br /> |-<br /> |-<br /> |Group 33<br /> |Raquel <br /> |Galocha<br /> |S212745<br /> |[[Project interdependency mapping]]<br /> |-<br /> |-<br /> |Group 11 <br /> |Emilie <br /> |Rasmussen<br /> |S184532<br /> |[[WBS, Work Breakdown Structure]]<br /> |-<br /> |-<br /> |Group 6 <br /> |Telma Sigrún <br /> |Torfadóttir<br /> |S212566<br /> |[[Stress]]<br /> |-<br /> |-<br /> |-<br /> |-<br /> |Group 4 <br /> |Erlend Thabiso Rømyhr <br /> |Sehube<br /> |S212426<br /> |[[Risk treatment for renewable energy developers]]<br /> |-<br /> |-<br /> |Group 11 <br /> |Peter<br /> |Birkholm<br /> |S184514<br /> |[[Gantt Chart In Construction]]<br /> |-<br /> |-<br /> |Group 18 <br /> |Giacomo<br /> |Branchini<br /> |S212987<br /> |[[Sources of Conflict: Guidelines for a Healthy Organizational Environment]]<br /> |-<br /> |-<br /> |Group 33 <br /> |Paula<br /> |González<br /> |S213398<br /> |[[The Big Five (Ocean)]]<br /> |-<br /> |-<br /> |Group 33 <br /> |Fernando<br /> |Ramiro Gonzalez<br /> |S214134<br /> |[[MCDA methods in decision making]]<br /> |-<br /> |-<br /> |Group 20 <br /> |Magnus Stjernborg<br /> |Koch<br /> |S175189<br /> |[[Project Success and Project Management Success]]<br /> |-<br /> |-<br /> |Group 26<br /> |Katarzyna<br /> |Kukulowicz<br /> |S213042<br /> |[[Extrinsic and intrinsic motivation. What does the will to act depend on?]]<br /> |-<br /> |-<br /> |Group 6 <br /> |Hildur Lara <br /> |Jonsdottir<br /> |S212410<br /> |[[The Significance of Cohesiveness in Projects]]<br /> |-<br /> |-<br /> |Group 20<br /> |Ziwei<br /> |Chen<br /> |S212635<br /> |[[Stakeholder Identification and Categorization]]<br /> |-<br /> |-<br /> |Group 18<br /> |Raül<br /> |Ciscar<br /> |S217122<br /> |[[Developing a project with the Tuckman's model]]<br /> |-<br /> |-<br /> |Group 18<br /> |Giorgio<br /> |Galasso<br /> |S212985<br /> |[[Risk Assessment: framework for combining CBA and MCDA]]<br /> |-<br /> |-<br /> |Group 33<br /> |Maria Elena<br /> |Igarzabal Saborida<br /> |S213206<br /> |[[Intrinsic and Extrinsic motivation]]<br /> |-<br /> |-<br /> |Group 32<br /> |Aikaterini<br /> |Deli<br /> |s212459<br /> |[[The Technique of Value Engineering (VE) in Architecture]]<br /> |-<br /> |-<br /> |Group 08<br /> |Jiajing<br /> |Zhang<br /> |s212412<br /> |[[The Rolling-wave Planning]]<br /> |-<br /> |-<br /> |Group<br /> |Isera Sarah<br /> |Hajaj<br /> |s153540<br /> |[[Standard Operating Procedures (SOPs)]]<br /> |-<br /> |Group 50<br /> |Ibrahim<br /> |Nassrallah<br /> |s211254<br /> |[[Brain Storming Technique]]-<br /> |-<br /> |-<br /> |Group 29<br /> |Panagiotis<br /> |Bakas<br /> |s216860<br /> |[[Drexler/Sibbet Model for Team development and project management]]<br /> |-<br /> |-<br /> |Group 20<br /> |Dionysios<br /> |Maroulis<br /> |s212885<br /> |[[Adapting-Resilient Management]]<br /> |-<br /> |-<br /> |Group 32<br /> |Gabriela Miti<br /> |Tsuge Costa<br /> |s220075<br /> |[[Project loafing in Projects]]<br /> |-<br /> |-<br /> |Group 32<br /> |Helená Evin<br /> |Cinar<br /> |s164741<br /> |[[The use of SWOT analysis]]<br /> |-<br /> |-<br /> |Group 3<br /> |Pietro<br /> |Boschetto<br /> |s213928<br /> |[[Enterprise Risk Management]]<br /> |-<br /> |-<br /> |Group 3<br /> |Virginia<br /> |Stinchi<br /> |s213230<br /> |[[The Blake and Mouton's Managerial (Leadership) Grid]]<br /> |-<br /> |-<br /> |Group 32<br /> |César<br /> |Delafargue<br /> |s212834<br /> |[[Design validation]]<br /> |-<br /> |-<br /> |Group 11<br /> |Rune<br /> |Andersen<br /> |s180642<br /> |[[Creating effective teams by means of mathematical modelling]]<br /> |-<br /> |-<br /> |Group Name: 47<br /> |Hannibal<br /> |Danielsen<br /> |s154283<br /> |[[Manage SCRUM]]</div>

HannibalDanielsen