Project management
•
0 likes•365 views
This document provides an introduction to agile project management and Scrum. It defines key concepts like the product backlog, sprint backlog, and Scrum roles. It compares the traditional waterfall lifecycle to the iterative nature of agile and Scrum. Key questions are presented around defining tasks as complete and defining project success.
Report
Share
Report
Share
Download to read offline
Recommended
Scrum review (mobile team)
This document summarizes a scrum review meeting for a mobile development team. It discusses three levels of scrum maturity and lists elements that must be included when using scrum for mobile development such as agile methodology, scrum concepts and processes, artifacts, and roles. Issues that the mobile team has experienced with planning, development, reviews and retrospectives are also outlined relating to user stories, estimation, testing, and tracking solutions from previous sprints.
Scrum 101+
This document provides an overview of Scrum, an agile framework for project management. It defines Scrum roles like Product Owner, Scrum Master, and Development Team. It describes Scrum events like Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. It also outlines Scrum artifacts like the Product Backlog, Sprint Backlog, and Product Increment. The goal is to help teams address complex problems and deliver valuable products through short development cycles with transparency, inspection, and adaptation.
What is Scrum?
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
Scrum For Developers
A session on what a developer needs to know when applying to a company where the PM says "we work with Scrum"
Scrum sprint structure workshop by Nermina Durmić
This document outlines the key elements of a Scrum sprint structure:
1. It defines common Scrum terms like user stories, sprints, product owner, and scrum master.
2. It describes the sprint flow as consisting of product backlog, backlog refinement, sprint planning, daily scrums, development, testing, sprint review, and retrospective.
3. It provides information on creating and ordering a product backlog, estimating effort using planning poker, and planning a sprint to select backlog items within the team's estimated sprint capacity.
Scrum Basics
The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.
Beginning SCRUM for Startups
Scrum is an iterative, incremental framework for project management that is often used in agile software development. It involves breaking projects into short cycles called sprints that typically last 1-4 weeks. The main roles in Scrum are the ScrumMaster, Product Owner, and Development Team. Key activities in each sprint include sprint planning meetings, daily standup meetings, development work, testing, and sprint retrospectives. At the end of each sprint, any potentially releasable work is demonstrated in a sprint review.
Scrumban - benefits of both the worlds
#Scrum is very popular these days but #kanban is suitable for better organizational level continuous improvement. We use #scrumban to get the benefits of both the worlds. Its a combination of good practices of scrum with kanban.
Recommended
Scrum review (mobile team)
This document summarizes a scrum review meeting for a mobile development team. It discusses three levels of scrum maturity and lists elements that must be included when using scrum for mobile development such as agile methodology, scrum concepts and processes, artifacts, and roles. Issues that the mobile team has experienced with planning, development, reviews and retrospectives are also outlined relating to user stories, estimation, testing, and tracking solutions from previous sprints.
Scrum 101+
This document provides an overview of Scrum, an agile framework for project management. It defines Scrum roles like Product Owner, Scrum Master, and Development Team. It describes Scrum events like Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. It also outlines Scrum artifacts like the Product Backlog, Sprint Backlog, and Product Increment. The goal is to help teams address complex problems and deliver valuable products through short development cycles with transparency, inspection, and adaptation.
What is Scrum?
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
Scrum For Developers
A session on what a developer needs to know when applying to a company where the PM says "we work with Scrum"
Scrum sprint structure workshop by Nermina Durmić
This document outlines the key elements of a Scrum sprint structure:
1. It defines common Scrum terms like user stories, sprints, product owner, and scrum master.
2. It describes the sprint flow as consisting of product backlog, backlog refinement, sprint planning, daily scrums, development, testing, sprint review, and retrospective.
3. It provides information on creating and ordering a product backlog, estimating effort using planning poker, and planning a sprint to select backlog items within the team's estimated sprint capacity.
Scrum Basics
The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.
Beginning SCRUM for Startups
Scrum is an iterative, incremental framework for project management that is often used in agile software development. It involves breaking projects into short cycles called sprints that typically last 1-4 weeks. The main roles in Scrum are the ScrumMaster, Product Owner, and Development Team. Key activities in each sprint include sprint planning meetings, daily standup meetings, development work, testing, and sprint retrospectives. At the end of each sprint, any potentially releasable work is demonstrated in a sprint review.
Scrumban - benefits of both the worlds
#Scrum is very popular these days but #kanban is suitable for better organizational level continuous improvement. We use #scrumban to get the benefits of both the worlds. Its a combination of good practices of scrum with kanban.
Introduction Professional Scrum Developer for Java
Introduction to the official PSD for Java training from scrum.org. It doesn't cover all topics from the official curriculum, and serves as a intro and teaser to actually follow the official training.
Scrumban
This document discusses Scrum, Kanban, and Scrumban approaches to agile software development. It outlines some common issues with Scrum like changing sprint scope and large team communication. Kanban uses continuous development without sprints and a visualized workflow. Scrumban aims to take the best of Scrum and Kanban by using continuous development within defined sprints and a visualized workflow to reduce idle time and avoid overloading team members. The document recommends starting Scrumban by stopping assigning all stories upfront and continuing with sprints and retrospectives.
ScrumBan : Best of Both Worlds. A Fertile Hybrid
Fusion at its best. The ScrumBan is a combination of best practices from Scrum and Kanban. Scrumban can be used effectively to have on demand agility
Using Scrum to Build a Jet Fighter? Yes!
How can Scrum be used to deliver complex integrated products, like a fighter aircraft?
It's been done, and done successfully.
How do you keep multiple teams aligned on the same delivery using Scrum?
This is a brief Infographic describing a quote from Jeff Sutherland published in HBR, May-June 2018 "Agile at Scale"
Link: https://hbr.org/2018/05/agile-at-scale
Scrum in practice at klarna
How to do SCRUM and how are we doing it in practice at Klarna TLV.
Covering the next topics: sprints, retro + demo, standup, pair programming, code quality, MVP, continuous integration, continuous deployment, and more...
Scrum methodology
Scrum methodology is an Agile management method approach toward software development as it progresses incrementally and repetitively.
Small team scrum and kanban
Can agile frameworks help small development teams? After looking at some agile basics, I examine two projects where a small development team used scrum. Agile can be used by small teams to their advantage with commitment and some work.
From Scrum to Scrumban
This document summarizes John Peltier's experience transitioning from Scrum to Scrumban for product development. Some key points:
- Retrospectives revealed their team was taking on too many stories at once and planning was draining.
- They adopted elements of Kanban like just-in-time planning and work-in-progress limits, while keeping Scrum elements like iterations, standups, and retrospectives.
- This "Scrumban" approach resulted in a 20% increase in productivity and improved morale. It released more control to developers and relieved pressure on product managers serving as product owners.
Big rewrites without big risks
Incremental development is easy when we are talking about functionality. Story splitting has become quite popular as a technique lately.
But what about those cases when you need to do an architectural refactoring? Could incremental development be applied?
(Talk delivered during I T.A.K.E. Unconference 2015)
Kanban Explained Clearly
Kanban is a lean methodology for managing workflow. It uses a visual board to display the actual workflow process and limits work-in-progress to improve flow. Workflow is tracked over time using cumulative flow diagrams to identify opportunities to optimize processes by tweaking work-in-progress limits and seek to minimize lead times. While some view Kanban and Scrum as competing methodologies, others see them as complementary approaches that can be combined for effective results.
Scaling agile
The process of software development for reasonably small team (less that 9 people) is pretty straitforward. Usually it is based on Scrum or Kanban with some variations and simplifications.
For huge team with more then 30 people it is not that obvious. For sure teams have interdependencies both in coding and requirements management that can really slow down development.
For people and teams it looks like constant interruptions caused by other teams and management. The problem is that “classic” Agile doesn’t help.
In this session we will consider methods of scaling Agile in huge teams.
Lightning Talk: An Introduction To Scrum
Scrum is an agile development methodology that focuses on roles, backlogs, and time-boxed meetings. There are three core roles: the Scrum Master enforces practices and removes roadblocks, the Product Owner maintains the backlog and user stories, and the self-organizing Team delivers working software each sprint. Artifacts include the Product Backlog of prioritized user stories and the Sprint Backlog of selected stories. Sprints are 30-day cycles where selected stories are demonstrated as shippable at the end. Meetings include Planning, Daily Scrums, a Sprint Review, and Retrospective.
ScrumBan Evolution - What is you next step?
A challenging presentation about Scrumban as an evolution from Scrum. Rethink your way of working (Iterations?, Estimations? Joy?) and initiate changes to your current working environment.
Introduction to Agile scrum
The sole purpose of this presentation was to introduce Agile Scrum Methodology into our company. We were following sprints and agile methodology, but never planned it properly before this.
A few months back, I recalled my days of working with Limewire and having few scrum masters in DigiMantra Labs. So we gave a little introduction and after that most of our teams are following this method. We now have 2 qualified Scrum Masters and counting.
Kanban development
KANBAN DEVELOPMENT
or get the agilest from agile
Oleh Dovhai, Java developer, ex QA engineer - about Kanban development process and how to use it in your project .
We will learn:
· What Kanban is: origin, principles, practice
· Kanban vs Scrum: compare tools for understanding, not judgment
· There is no ideal tool: experiment, combined and again experiment
Introduction to agile
The document introduces agile methodologies like Scrum and XP, describing key practices such as daily stand up meetings, iterations/sprints with planning and retrospectives, test-driven development, and continuous integration. It discusses choosing an agile approach that fits the context and avoiding anti-patterns as teams work to adopt agile practices. The presentation provides an overview of agile concepts and next steps for organizations looking to implement agile processes.
Scrum for high performance teams
An overview of Scrum methdology. Presentation for the IT students at Kaunas University of Technology in Lithuania
Metrics that bring value
Svetlana Mukhina discusses various metrics that are gathered on agile projects at Luxoft, including capacity, velocity, requirements stability index, burn-down charts, and daily work logs. She explains how each metric is calculated and how they are used to improve planning, track performance, discover issues, and ensure projects are delivered on time. Examples are provided of how metrics have helped Luxoft teams identify bottlenecks and make process improvements.
English redistributable-intro-scrum
This document provides an overview of Agile and Scrum methodologies for software development. It discusses key Agile principles like early delivery, flexibility, and collaboration. Scrum is presented as a framework for Agile development with roles like Product Owner, Scrum Master, and Team. Ceremonies like sprint planning, daily stand-ups, sprint reviews and retrospectives are covered. Artifacts like the product and sprint backlogs are also summarized. Examples of companies using Scrum are provided.
Agile Fundamentals and Best Practices (with Trello)
This document provides an overview of agile fundamentals and best practices. It outlines key concepts of Scrum like the product owner, development team, and sprint process. It also describes agile practices such as sprint planning, getting user feedback, testing, and using Trello for project management. The document is intended to recap agile concepts for the author's team.
Agile Scrum Training Process
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
Introduction to Agile software testing
Introduction to Agile software testing - The 5th seminar in public seminar series from KMS Technology which have been delivering from 2011 in every two months
More Related Content
What's hot
Introduction Professional Scrum Developer for Java
Introduction to the official PSD for Java training from scrum.org. It doesn't cover all topics from the official curriculum, and serves as a intro and teaser to actually follow the official training.
Scrumban
This document discusses Scrum, Kanban, and Scrumban approaches to agile software development. It outlines some common issues with Scrum like changing sprint scope and large team communication. Kanban uses continuous development without sprints and a visualized workflow. Scrumban aims to take the best of Scrum and Kanban by using continuous development within defined sprints and a visualized workflow to reduce idle time and avoid overloading team members. The document recommends starting Scrumban by stopping assigning all stories upfront and continuing with sprints and retrospectives.
ScrumBan : Best of Both Worlds. A Fertile Hybrid
Fusion at its best. The ScrumBan is a combination of best practices from Scrum and Kanban. Scrumban can be used effectively to have on demand agility
Using Scrum to Build a Jet Fighter? Yes!
How can Scrum be used to deliver complex integrated products, like a fighter aircraft?
It's been done, and done successfully.
How do you keep multiple teams aligned on the same delivery using Scrum?
This is a brief Infographic describing a quote from Jeff Sutherland published in HBR, May-June 2018 "Agile at Scale"
Link: https://hbr.org/2018/05/agile-at-scale
Scrum in practice at klarna
How to do SCRUM and how are we doing it in practice at Klarna TLV.
Covering the next topics: sprints, retro + demo, standup, pair programming, code quality, MVP, continuous integration, continuous deployment, and more...
Scrum methodology
Scrum methodology is an Agile management method approach toward software development as it progresses incrementally and repetitively.
Small team scrum and kanban
Can agile frameworks help small development teams? After looking at some agile basics, I examine two projects where a small development team used scrum. Agile can be used by small teams to their advantage with commitment and some work.
From Scrum to Scrumban
This document summarizes John Peltier's experience transitioning from Scrum to Scrumban for product development. Some key points:
- Retrospectives revealed their team was taking on too many stories at once and planning was draining.
- They adopted elements of Kanban like just-in-time planning and work-in-progress limits, while keeping Scrum elements like iterations, standups, and retrospectives.
- This "Scrumban" approach resulted in a 20% increase in productivity and improved morale. It released more control to developers and relieved pressure on product managers serving as product owners.
Big rewrites without big risks
Incremental development is easy when we are talking about functionality. Story splitting has become quite popular as a technique lately.
But what about those cases when you need to do an architectural refactoring? Could incremental development be applied?
(Talk delivered during I T.A.K.E. Unconference 2015)
Kanban Explained Clearly
Kanban is a lean methodology for managing workflow. It uses a visual board to display the actual workflow process and limits work-in-progress to improve flow. Workflow is tracked over time using cumulative flow diagrams to identify opportunities to optimize processes by tweaking work-in-progress limits and seek to minimize lead times. While some view Kanban and Scrum as competing methodologies, others see them as complementary approaches that can be combined for effective results.
Scaling agile
The process of software development for reasonably small team (less that 9 people) is pretty straitforward. Usually it is based on Scrum or Kanban with some variations and simplifications.
For huge team with more then 30 people it is not that obvious. For sure teams have interdependencies both in coding and requirements management that can really slow down development.
For people and teams it looks like constant interruptions caused by other teams and management. The problem is that “classic” Agile doesn’t help.
In this session we will consider methods of scaling Agile in huge teams.
Lightning Talk: An Introduction To Scrum
Scrum is an agile development methodology that focuses on roles, backlogs, and time-boxed meetings. There are three core roles: the Scrum Master enforces practices and removes roadblocks, the Product Owner maintains the backlog and user stories, and the self-organizing Team delivers working software each sprint. Artifacts include the Product Backlog of prioritized user stories and the Sprint Backlog of selected stories. Sprints are 30-day cycles where selected stories are demonstrated as shippable at the end. Meetings include Planning, Daily Scrums, a Sprint Review, and Retrospective.
ScrumBan Evolution - What is you next step?
A challenging presentation about Scrumban as an evolution from Scrum. Rethink your way of working (Iterations?, Estimations? Joy?) and initiate changes to your current working environment.
Introduction to Agile scrum
The sole purpose of this presentation was to introduce Agile Scrum Methodology into our company. We were following sprints and agile methodology, but never planned it properly before this.
A few months back, I recalled my days of working with Limewire and having few scrum masters in DigiMantra Labs. So we gave a little introduction and after that most of our teams are following this method. We now have 2 qualified Scrum Masters and counting.
Kanban development
KANBAN DEVELOPMENT
or get the agilest from agile
Oleh Dovhai, Java developer, ex QA engineer - about Kanban development process and how to use it in your project .
We will learn:
· What Kanban is: origin, principles, practice
· Kanban vs Scrum: compare tools for understanding, not judgment
· There is no ideal tool: experiment, combined and again experiment
Introduction to agile
The document introduces agile methodologies like Scrum and XP, describing key practices such as daily stand up meetings, iterations/sprints with planning and retrospectives, test-driven development, and continuous integration. It discusses choosing an agile approach that fits the context and avoiding anti-patterns as teams work to adopt agile practices. The presentation provides an overview of agile concepts and next steps for organizations looking to implement agile processes.
Scrum for high performance teams
An overview of Scrum methdology. Presentation for the IT students at Kaunas University of Technology in Lithuania
Metrics that bring value
Svetlana Mukhina discusses various metrics that are gathered on agile projects at Luxoft, including capacity, velocity, requirements stability index, burn-down charts, and daily work logs. She explains how each metric is calculated and how they are used to improve planning, track performance, discover issues, and ensure projects are delivered on time. Examples are provided of how metrics have helped Luxoft teams identify bottlenecks and make process improvements.
English redistributable-intro-scrum
This document provides an overview of Agile and Scrum methodologies for software development. It discusses key Agile principles like early delivery, flexibility, and collaboration. Scrum is presented as a framework for Agile development with roles like Product Owner, Scrum Master, and Team. Ceremonies like sprint planning, daily stand-ups, sprint reviews and retrospectives are covered. Artifacts like the product and sprint backlogs are also summarized. Examples of companies using Scrum are provided.
Agile Fundamentals and Best Practices (with Trello)
This document provides an overview of agile fundamentals and best practices. It outlines key concepts of Scrum like the product owner, development team, and sprint process. It also describes agile practices such as sprint planning, getting user feedback, testing, and using Trello for project management. The document is intended to recap agile concepts for the author's team.
What's hot (20)
Introduction Professional Scrum Developer for Java
Introduction Professional Scrum Developer for Java
Agile Fundamentals and Best Practices (with Trello)
Agile Fundamentals and Best Practices (with Trello)
Similar to Project management
Agile Scrum Training Process
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
Introduction to Agile software testing
Introduction to Agile software testing - The 5th seminar in public seminar series from KMS Technology which have been delivering from 2011 in every two months
Scrum training
Agile and Scrum, Business Problem, Scrum Process, Scrum Team, Artifacts, Product Backlog, Sprint Backlog
Scrum Training
This document provides an overview of Scrum and its key concepts. It introduces Scrum as an Agile methodology used to manage product development. The document outlines the Scrum process including sprints, daily stand-ups, sprint planning and reviews. It describes Scrum roles like Product Owner and Scrum Master and artifacts like the product and sprint backlogs. Charts are presented to track work like burndowns and velocity. The document aims to explain how Scrum can help teams adapt to change and deliver working software frequently.
Scrum workshop - September 7, 2012
Scrum Workshop presentation done by Alex Rosales on Septembe 7, 2012 - Quang Trung Software City, HCMC, Vietnam
Scrum wall images by tobias mayer
Scrum is a framework for developing new products that allows teams to create their own lightweight process. It emphasizes empiricism, self-organization, collaboration, prioritization, and rhythm. Scrum works best for complex problems like new product development and knowledge work. Teams of 3-7 people work in short cycles called sprints to deliver working software. They plan, execute, and reflect at the end of each sprint to continuously improve.
Introduction to scrum
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also discusses the product and sprint backlogs and how teams work in sprints to deliver working software increments every 2-4 weeks using the Scrum framework.
Scrum methodology
Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
Introduction to Scrum - Agile Methods
Scrum is an agile framework for managing product development that emphasizes self-organizing cross-functional teams, sprints, daily stand-ups, and adaptive planning. It consists of roles like the product owner and Scrum master, artifacts like the product backlog and sprint backlog, and ceremonies like sprint planning and reviews. Scrum originated in the 1990s and aims to rapidly deliver working software through short development cycles and continuous improvement.
Agile Project Management using Scrum
This document provides an overview of the basics of Scrum, an agile project management framework. It defines key Scrum concepts like roles, activities, artifacts and processes. The document outlines that Scrum is a simple, flexible approach to managing complex projects that focuses on clarity, inspection and adaptation through short iterations and daily stand-ups. It emphasizes delivering working software frequently in sprints and adapting the backlog based on feedback.
Manage your project differently
The document discusses managing projects using an Agile framework called Scrum. It explains that Scrum is iterative and incremental, focusing on delivering working software frequently in short cycles called sprints. It outlines Scrum roles like Product Owner, Scrum Master, and self-organizing cross-functional teams. Key Scrum artifacts include the Product Backlog, Sprint Backlog, and Burn Down Chart. Meetings like the Daily Scrum and Sprint Review are used to track progress and get feedback.
Getting Agile with Srum
Scrum is one of the leading agile software development processes. Over 12,000 project managers have become certified to run Scrum projects . Since its origin on Japanese new product development projects in the 1980s, Scrum has become recognized as one of the best project management frameworks for handling rapidly changing or evolving projects. Especially useful on projects with lots of technology or requirements uncertainty, Scrum is a proven, scalable agile process for managing software projects.
Through lecture, discussion and exercises, this fast-paced tutorial covers the basics of what you need to know to get started with Scrum. You will learn about all key aspects of Scrum including product and sprint backlog, the sprint planning meeting, the sprint review, conducting a sprint retrospective, activities that occur during sprints, measuring and monitoring progress, and scaling Scrum to work with large and distributed teams. Also covered are the roles and responsibilities of the ScrumMaster, the product owner, and the Scrum team.
This session will be equally suited for managers, programmers, testers, product managers and anyone else interested in improving product delivery.
Customized Scrum
This document discusses customizing the Scrum process for a startup company. It describes the author's experience being assigned the Product Owner and Scrum Master roles without previous Scrum experience. The author learned Scrum and implemented it in their own way for their company. The document then provides an overview of key Scrum concepts like sprints, product backlogs, daily standups, sprint reviews, and retrospectives. It also discusses tools that can be used to support the Scrum process.
Scrum agile process
Scrum and Kanban are popular agile methodologies used with Team Foundation Server (TFS). TFS supports agile practices through features like version control, work item tracking, build automation, and reporting. It allows teams to manage their backlogs, track work items like user stories and bugs, and gain visibility into project progress and metrics.
Scrum Framework in Agile
This document provides an overview of Scrum and its key concepts. It defines the waterfall and agile models of software development. Scrum is described as an agile method that uses cross-functional teams, product backlogs, sprints, daily stand-ups, and sprint reviews. Key Scrum roles like the Product Owner and Scrum Master are explained. The document also discusses estimating techniques, burndown charts, and how Scrum compares to other agile frameworks.
Scrum - but... Agile Game Development in Small Teams
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like the Product Owner, Development Team, and Scrum Master. The Scrum process involves sprints, daily stand-ups, sprint planning and reviews. It also introduces an example game development team called Astro City working with Scrum.
Getting Agile with Srum
This document provides an overview of Scrum, an agile framework for project management. It discusses key Scrum concepts like sprints, daily stand-ups, product backlogs, and roles. Scrum aims to be more flexible than traditional "relay race" development by having cross-functional teams work on tasks simultaneously in sprints of 1-4 weeks to iteratively develop working software.
Avantica presentacion scrum
This document provides an overview of SCRUM, an agile framework for managing software projects. It describes common software development problems like missed deadlines and falling quality that SCRUM aims to address. Key aspects of SCRUM covered include the agile manifesto, origins of SCRUM, roles like product owner and scrum master, activities like daily scrums and sprints, artifacts like product and sprint backlogs, and metrics for tracking progress. The document concludes that SCRUM is not a silver bullet but aims to manage what is manageable through transparency, inspection, and adaptation of the process.
Getting agile-with-scrum-ndc-2104
This document provides an overview of Scrum, an agile framework for project management. It discusses key Scrum concepts like self-organizing cross-functional teams, sprints, ceremonies, and artifacts. Some key points include: Scrum uses short sprints (1-4 weeks) to incrementally develop work, teams are self-organizing and do a little of everything each sprint, ceremonies provide transparency and include daily stand-ups, sprint reviews, and retrospectives, and the product backlog and sprint backlog help track and manage work in progress.
Spiritof SCRUM
The spirit of SCRUM presentation will allow you to understand teh realtion between PMBOK, Agile, Waterfall and TPS.
Similar to Project management (20)
Scrum - but... Agile Game Development in Small Teams
Scrum - but... Agile Game Development in Small Teams
More from SSA KPI
Germany presentation
This document discusses student organizations and the university system in Germany. It provides an overview of the different types of higher education institutions in Germany, including universities, universities of applied sciences, and arts universities. It describes the degree system including bachelor's, master's, and Ph.D. programs. It also outlines the systems of student participation at universities, using the examples of Leipzig and Hanover. Student councils, departments, and faculty student organizations are discussed.
Grand challenges in energy
The document discusses grand challenges in energy and perspectives on moving towards more sustainable systems. It notes that while global energy demand and CO2 emissions rebounded in 2010 after the economic downturn, urgent changes are still needed. It explores perspectives on changing direction, including overcoming barriers like technologies, economies, management, and mindsets. The document advocates a systems approach and backcasting from desirable futures to identify pathways for transitioning between states.
Engineering role in sustainability
Engineering can play an important role in sustainable development by focusing on meeting human needs over wants and prioritizing projects that serve the most vulnerable populations. Engineers should consider how their work impacts sustainability, affordability, and accessibility. A socially sustainable product is manufactured sustainably and also improves people's lives. Engineers are not neutral and should strive to serve societal needs rather than just generate profits. They can help redefine commerce and an engineering culture focused on meeting needs sustainably through services rather than creating unnecessary products and infrastructure.
Consensus and interaction on a long term strategy for sustainable development
The document discusses the need for a long-term vision for sustainable development to address major challenges like climate change, resource depletion, and inequity. A long-term perspective is required because these problems will take consistent action over many years to solve. However, short-term solutions may counteract long-term goals if not guided by an overall strategic vision. Developing a widely accepted long-term sustainable development vision requires input from many stakeholders to find balanced solutions and avoid dead ends. Strategic decisions with long-lasting technological and social consequences need a vision that can adapt to changing conditions over time.
Competences in sustainability in engineering education
The document discusses competencies in sustainability for engineering education. It defines competencies and lists taxonomies that classify competencies into categories like knowledge, skills, attitudes, and ethics. Engineering graduates are expected to have competencies like critical thinking, systemic thinking, and interdisciplinarity. Analysis of competency frameworks from different universities found that competencies are introduced at varying levels, from basic knowledge to complex problem solving and valuing sustainability challenges. The document also outlines the University of Polytechnic Catalonia's framework for its generic sustainability competency.
Introducatio SD for enginers
The document discusses concepts related to sustainability including carrying capacity, ecological footprint, and the IPAT equation. It provides data on historical and projected world population growth. Examples are given showing the ecological footprint of different countries and how it is calculated based on factors like energy use, agriculture, transportation, housing, goods and services. The human development index is also introduced as a broader measure than GDP for assessing well-being. Graphs illustrate the relationship between increasing HDI, ecological footprint, and the goal of transitioning to sustainable development.
Talking with money
AACIMP 2011 Summer School. Science of Global Challenges Stream. Lecture by Roman Zinchenko.
'Green' startup investment
AACIMP 2011 Summer School. Science of Global Challenges Stream. Lecture by Roman Zinchenko.
From Huygens odd sympathy to the energy Huygens' extraction from the sea waves
Huygens observed that two pendulum clocks suspended near each other would synchronize their swings to be 180 degrees out of phase. He conducted experiments that showed the synchronization was caused by small movements transmitted through their common frame. While this discovery did not help solve the longitude problem as intended, it sparked further investigations into coupled oscillators and synchronization phenomena.
Dynamics of dice games
1) The document discusses whether dice rolls and other mechanical randomizers can truly produce random outcomes from a dynamics perspective.
2) It analyzes the equations of motion for different dice shapes and coin tossing, showing that outcomes are theoretically predictable if initial conditions can be reproduced precisely.
3) However, in reality small uncertainties in initial conditions mean mechanical randomizers can approximate random processes, even if they are deterministic based on their underlying dynamics.
Energy Security Costs
This document discusses the concept of energy security costs. It defines energy security costs as externalities associated with short-term macroeconomic adjustments to changes in energy prices and long-term impacts of monopoly or monopsony power in energy markets. The document provides references on calculating health and environmental impacts of electricity generation and assessing costs and benefits of oil imports. It also outlines a proposed 4-hour course on basic concepts, examples, and a case study analyzing energy security costs for Ukraine based on impacts of increasing natural gas import prices.
Naturally Occurring Radioactivity (NOR) in natural and anthropic environments
This document provides an overview of naturally occurring radioactivity (NOR) and naturally occurring radioactive materials (NORM) with a focus on their relevance to the oil and gas industry. It discusses the main radionuclides of interest, including radium-226, radium-228, uranium, radon-222, and lead-210. It also summarizes the origins of NORM in the oil and gas industry and the types of radiation emitted by NORM.
Advanced energy technology for sustainable development. Part 5
All energy technologies involve risks that must be carefully evaluated and minimized to ensure sustainable development. No technology is perfectly safe, so ongoing analysis of benefits, risks and impacts is needed. Public understanding and acceptance of risks is also important.
Advanced energy technology for sustainable development. Part 4
The document discusses the impacts and benefits of energy technology research, using fusion research as a case study. It outlines four pathways through which energy research can impact economies and societies: 1) direct economic effects, 2) impacts on local communities, 3) impacts on industrial technology capabilities, and 4) long-term impacts on energy markets and technologies. It then analyzes the direct and indirect economic impacts of fusion research investments and the technical spin-offs that fusion research has produced. Finally, it evaluates the potential future role of fusion electricity in global energy markets under environmental constraints.
Advanced energy technology for sustainable development. Part 3
This document discusses using fusion energy for sustainable development through biomass conversion. It proposes a system where fusion energy is used to provide heat for gasifying biomass into synthetic fuels like methane and diesel. Experiments show biomass can be over 95% converted to hydrogen, carbon monoxide and methane gases using nickel catalysts at temperatures of 600-1000 degrees Celsius. A conceptual biomass reactor is presented that could process 6 million tons of biomass per year, consisting of 70% cellulose and 30% lignin, into synthetic fuels to serve as carbon-neutral transportation fuels. Fusion energy could provide the high heat needed for the gasification and synthesis processes.
Advanced energy technology for sustainable development. Part 2
The document summarizes fusion energy technology and its potential for sustainable development. Fusion occurs at extremely high temperatures and is the process that powers the Sun and stars. Researchers are working to develop fusion energy on Earth using hydrogen isotopes as fuel. Key challenges include confining the hot plasma long enough at high density for fusion reactions to produce net energy gain. Progress is being made towards achieving the conditions needed for a sustainable fusion reaction as defined by Lawson's criteria.
Advanced energy technology for sustainable development. Part 1
1. The document discusses the concept of sustainability and sustainable systems. It provides an example of a closed ecosystem with algae, water fleas, and fish, where energy and material balances must be maintained for long-term stability.
2. Key requirements for a sustainable system include energy balance between inputs and outputs, recycling of materials or wastes, and mechanisms to control population relationships and prevent overconsumption of resources.
3. Historically, the environment was seen as external and unchanging, but it is now recognized that the environment co-evolves interactively with the living creatures within it.
Fluorescent proteins in current biology
This document discusses the use of fluorescent proteins in current biological research. It begins with an overview of the development of optical microscopy and fluorescence techniques. It then focuses on the green fluorescent protein (GFP) and how it has been used as a molecular tag to study protein expression and interactions in living cells through techniques like gene delivery, transfection, viral infection, FRET, and optogenetics. The document concludes that fluorescent proteins have revolutionized cell biology by enabling the real-time visualization and control of molecular pathways and signaling processes in living systems.
Neurotransmitter systems of the brain and their functions
1. Neurotransmitters are chemical substances released at synapses that transmit signals between neurons. The main neurotransmitters in the brain are acetylcholine, serotonin, dopamine, norepinephrine, glutamate, GABA, and endorphins.
2. Each neurotransmitter system is involved in regulating key brain functions and behaviors such as movement, mood, sleep, cognition, and pain perception.
3. Neurotransmitters act via membrane receptors on target neurons, including ionotropic receptors that are ligand-gated ion channels and metabotropic G-protein coupled receptors.
More from SSA KPI (20)
Consensus and interaction on a long term strategy for sustainable development
Consensus and interaction on a long term strategy for sustainable development
Competences in sustainability in engineering education
Competences in sustainability in engineering education
From Huygens odd sympathy to the energy Huygens' extraction from the sea waves
From Huygens odd sympathy to the energy Huygens' extraction from the sea waves
Naturally Occurring Radioactivity (NOR) in natural and anthropic environments
Naturally Occurring Radioactivity (NOR) in natural and anthropic environments
Advanced energy technology for sustainable development. Part 5
Advanced energy technology for sustainable development. Part 5
Advanced energy technology for sustainable development. Part 4
Advanced energy technology for sustainable development. Part 4
Advanced energy technology for sustainable development. Part 3
Advanced energy technology for sustainable development. Part 3
Advanced energy technology for sustainable development. Part 2
Advanced energy technology for sustainable development. Part 2
Advanced energy technology for sustainable development. Part 1
Advanced energy technology for sustainable development. Part 1
Neurotransmitter systems of the brain and their functions
Neurotransmitter systems of the brain and their functions
Recently uploaded
How to Fix the Import Error in the Odoo 17
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
How to Setup Warehouse & Location in Odoo 17 Inventory
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
South African Journal of Science: Writing with integrity workshop (2024)
South African Journal of Science: Writing with integrity workshop (2024)Academy of Science of South Africa
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.Chapter wise All Notes of First year Basic Civil Engineering.pptx
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
Walmart Business+ and Spark Good for Nonprofits.pdf
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
How to deliver Powerpoint Presentations.pptx
"How to make and deliver dynamic presentations by making it more interactive to captivate your audience attention"
What is Digital Literacy? A guest blog from Andy McLaughlin, University of Ab...
What is Digital Literacy? A guest blog from Andy McLaughlin, University of Aberdeen
PCOS corelations and management through Ayurveda.
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
How to Create a More Engaging and Human Online Learning Experience
How to Create a More Engaging and Human Online Learning Experience Wahiba Chair Training & Consulting
Wahiba Chair's Talk at the 2024 Learning Ideas Conference. BBR 2024 Summer Sessions Interview Training
Qualitative research interview training by Professor Katrina Pritchard and Dr Helen Williams
Main Java[All of the Base Concepts}.docx
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
BÀI TẬP DẠY THÊM TIẾNG ANH LỚP 7 CẢ NĂM FRIENDS PLUS SÁCH CHÂN TRỜI SÁNG TẠO ...
BÀI TẬP DẠY THÊM TIẾNG ANH LỚP 7 CẢ NĂM FRIENDS PLUS SÁCH CHÂN TRỜI SÁNG TẠO ...Nguyen Thanh Tu Collection
https://app.box.com/s/qhtvq32h4ybf9t49ku85x0n3xl4jhr15Hindi varnamala | hindi alphabet PPT.pdf
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
Recently uploaded (20)
How to Setup Warehouse & Location in Odoo 17 Inventory
How to Setup Warehouse & Location in Odoo 17 Inventory
South African Journal of Science: Writing with integrity workshop (2024)
South African Journal of Science: Writing with integrity workshop (2024)
Chapter wise All Notes of First year Basic Civil Engineering.pptx
Chapter wise All Notes of First year Basic Civil Engineering.pptx
Walmart Business+ and Spark Good for Nonprofits.pdf
Walmart Business+ and Spark Good for Nonprofits.pdf
What is Digital Literacy? A guest blog from Andy McLaughlin, University of Ab...
What is Digital Literacy? A guest blog from Andy McLaughlin, University of Ab...
NEWSPAPERS - QUESTION 1 - REVISION POWERPOINT.pptx
NEWSPAPERS - QUESTION 1 - REVISION POWERPOINT.pptx
How to Create a More Engaging and Human Online Learning Experience
How to Create a More Engaging and Human Online Learning Experience
BÀI TẬP DẠY THÊM TIẾNG ANH LỚP 7 CẢ NĂM FRIENDS PLUS SÁCH CHÂN TRỜI SÁNG TẠO ...
BÀI TẬP DẠY THÊM TIẾNG ANH LỚP 7 CẢ NĂM FRIENDS PLUS SÁCH CHÂN TRỜI SÁNG TẠO ...
Film vocab for eal 3 students: Australia the movie
Film vocab for eal 3 students: Australia the movie
Project management
- 1. Introduction to Agile Project Management Vasilij Savin AACIMP 2011
- 2. What is a project?
- 7. Scrum
- 9. Scrum Roles Scrum Master Product Owner
- 10. Scrum Roles Scrum Team Scrum Master Product Owner
- 11. Questions for discussion When is a task When a project is complete? considered to be a (Definition of Done) failure? (Definition of Success)
- 12. Scrum
- 13. ≠
- 14. Agile (XP) Rules ● Have sustainable pace (no overtime) ● Have people work on different modules to learn ● Pair Programming ● Coding standards ● Integration ● Create automated test suite ● Write a test to replicate the bug
- 15. QUESTIONS?
- 16. Extra Slides
- 17. Waterfall pros ● Produces what is specified ● Supports large teams ● High resource efficiency ● Clear division of labour
- 18. Waterfall cons ● Results delivered by the end of project cycle ● Requires a lot of documentation ● Everyone has very narrow view of the project ● Scope is very inflexible ● Gives an illusion of control
- 19. Scrum ● Alternative project management technique ● 3 main roles – Team (7+-2) – Scrum Master, facilitator, team support – Product Owner, customer representative
- 20. Scrum concepts ● Product Backlog ● Sprint Backlog ● Scrum board / Burndown chart
- 21. Scrum activities ● Sprint planning/planning poker ● Sprint / Daily Scrum ● Demonstration / Retrospective
- 22. Task break down ● User stories ● Story estimate by team ● Story broken down into tasks
- 23. Resources ● http://www.extremeprogramming.org/rules.html ● http://www.implementingscrum.com/
- 24. Laws ● “adding manpower to a late software project makes it later” Brook's law