The Scrum framework

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
  
[[Category: Project Management]] [[Category: Agile]]
+
[[Category: Project Management]] [[Category: Agile]] [[Category: Purpose]] [[Category: Complexity]]
 
   
 
   
  

Revision as of 09:10, 14 February 2021


Contents

Abstract

In the complex technology and business world we live in today, there is a need for project management practices that can be considered flexible. When looking at for example product development, timing plays a huge role. Companies face growing pressure in delivering their products quickly to the market. This pressure can result in many uncertainties and increases the rates of failures. These uncertainties can be linked to traditional project management methods being applied, where deterministic practices are being used. This can lead to companies not being able to evolve quickly or inexpensively enough when nearing the end of the development lifecycle. With the product development example in mind the ultimate goal is to deliver great customer value, Agile practices do that by constantly seeking involvement in the product development e.g. from the customer. Getting validation, and evaluating if what is being made is meeting business goals. This approach mitigates risk and reduces uncertainty in fast evolving projects (reference 1)

Scrum is an Agile project Management framework, where projects are managed in short sprints or iterations. The control or project management is moved from the traditional central scheduling to the teams itself. Where individuals closer to the actual work take charge of the decision making. With this frameworks the feedback loop between customers and developers is much shorter, the progress is visible, inspections are done constantly and adaptations done when needed. This is especially important in complex projects where companies have to be able to adjust to changes in scope or specifications. Scrum framework can be considered the opposite to deterministic project management approaches where detailed plans are being used, e.g. work schedules and Gantt charts. (reference 2)

Background

Application

Scrum roles

Scrum has three roles: The ScrumMaster, Product Owner and the Team.

o ScrumMaster o Product Owner o Team


Application

Benefits

Limitation

Conclusion

Annotated bibliography

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox