Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.
Scrum is an agile framework for managing product development. It defines three roles - Scrum Master, Product Owner, and Development Team - and three artifacts - Product Backlog, Sprint Backlog, and Product Increment. It also includes five ceremonies - Product Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Scrum was first defined in 1986 and evolved through the 1990s, with Ken Schwaber and Jeff Sutherland formalizing the method in 2001 in their book Agile Software Development with Scrum.
This document provides an overview of Agile and Scrum methodologies. It describes the iterative incremental model and compares it to the waterfall model. The key aspects of Agile include iterative development, early delivery of working software, collaboration between business and developers, self-organizing teams, and face-to-face communication. Scrum is then introduced as a framework for implementing Agile. The core Scrum roles, events, artifacts, user stories, estimation techniques, and burn down charts are defined and explained at a high level.
The document provides an overview of the Scrum agile framework for software development. It defines Scrum, outlines its history and components, and describes key aspects like roles, artifacts, and the sprint process. Scrum uses short development iterations called sprints to incrementally develop working software, with daily stand-ups and sprint planning and review meetings. Roles include the product owner, scrum master, and self-organizing cross-functional team. Artifacts include the product and sprint backlogs and burn down charts. The document also discusses scaling Scrum for large projects.
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
Scrum is an agile process for managing software development projects using empirical process control with inspection and adaptation cycles. The scrum process consists of monthly sprints resulting in potentially shippable increments and daily scrum meetings. A product backlog is prioritized and items are selected for each sprint backlog. The scrum team works during sprints to complete items and demonstrate progress at sprint reviews.
Scrum is a framework for project management developed by Ken Schwaber and Jeff Sutherland. It is lightweight, simple, and difficult to master. Scrum uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like product backlogs and sprint backlogs. The goals are transparency, inspection, and adaptation. Scrum aims to deliver working software frequently through short development cycles and continuous improvement.
Scrum is a framework for managing complex product development that uses self-organizing cross-functional teams, short development iterations called sprints, and regular inspection and adaptation. Key roles include the Product Owner who manages the product backlog, the Scrum Master who facilitates the process, and the Scrum Team who does the work. Sprints involve planning, daily stand-ups, reviews, and retrospectives to continuously improve. The product backlog, sprint backlog, and burn down charts are used to track progress.
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
Scrum is an agile framework for managing product development. It involves self-organizing cross-functional teams who break their work into actions that can be completed within timeboxed iterations, called sprints, no longer than one month to build usable software. Key roles include the Product Owner who manages priorities from stakeholders, the Scrum Master who ensures Scrum is followed, and the Development Team. Artifacts include the Product Backlog of features, Sprint Backlog of tasks, and increments of functionality delivered each sprint. The process consists of sprints, daily stand-ups, sprint planning and review meetings, and retrospectives for continuous improvement.
This document provides a summary of key concepts from Chapter 4 of the book "Essential Scrum". It describes the Scrum framework, roles, artifacts, and events. The Scrum roles include the Product Owner, Scrum Master, and Development Team. Key artifacts are the Product Backlog and Sprint Backlog. Main events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal is to help teams self-organize to deliver working software in short cycles through transparency, inspection, and adaptation.
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile concepts like iterations called sprints and artifacts like product backlog, sprint backlog, and product increment. It describes Scrum roles of product owner, Scrum master, and team. It outlines Scrum activities like sprint planning, daily scrum, sprint review, and retrospective. Finally, it discusses tools like task boards and burn down charts used to provide transparency and track progress.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
Agile Methodology in Software DevelopmentRaghav Seth
The document discusses various agile methodologies and frameworks, with a focus on Scrum. It defines Scrum as an agile process that allows teams to focus on delivering the highest business value in the shortest time through rapid inspection of working software every 2-4 weeks. Key Scrum roles include the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and self-organizing Development Teams. Sprints involve planning, daily stand-ups, demos, and retrospectives to continuously improve.
This document provides an introduction to Agile Scrum methodology. It defines Agile and Scrum, outlines the history and principles of Scrum, and describes the core components and processes in Scrum including roles, ceremonies, artifacts, and sprints. The document explains that Scrum is an iterative Agile framework used for managing complex projects, with self-organizing cross-functional teams working in short sprints to deliver working software increments based on prioritized backlogs.
Scrum is an agile software development methodology where self-organizing teams work in short development cycles called sprints to build software incrementally. It focuses on collaboration, flexibility, and delivering working software frequently. Key components of Scrum include roles like the product owner and scrum master, a product backlog to track requirements, sprints for incremental development, and daily stand-up meetings. Scrum aims to be flexible and adaptive to changing requirements while maximizing productivity through its empirical process control methods.
- Scrum is an agile framework for managing complex projects using short development cycles ("sprints"), regular inspection of progress, and adaptation to change. It emphasizes communication, collaboration, and incremental delivery of work.
- Key Scrum roles include the Product Owner who prioritizes features, the Development Team who implements them, and the Scrum Master who facilitates the process.
- Core Scrum activities are Sprint Planning meetings, Daily Scrums, Sprint Reviews, and Sprint Retrospectives, which focus the team and enable inspection and adaptation.
- The Product Backlog contains prioritized features and the Sprint Backlog contains work for the current Sprint. A Burn Down Chart tracks progress. Scrum
The document provides an overview of Agile development and Scrum methodology. It discusses key Agile concepts like the Agile Manifesto, Scrum roles and artifacts, timeboxing, and metrics like velocity and burndowns. It also addresses adopting Agile, working with requirements and QA, and challenges of offshore development in an Agile model.
The document discusses Agile SCRUM project development methodology. It provides an overview of SCRUM principles and processes including short iterative development cycles called sprints, daily stand-up meetings, sprint planning, tracking sprint backlogs and burn downs, sprint reviews and retrospectives. The roles of product owners, scrum masters and self-organizing cross-functional teams are also summarized.
Polymer & the web components revolution 6:25:14mattsmcnulty
Polymer & the Web Components Revolution from Google I/O on 6/25/14 by Matthew McNulty. An overview of Web Components, Polymer, and the ecosystem and tools being created surrounding them.
The document discusses agile development methods like Scrum and Extreme Programming (XP). It covers topics like iterative planning, continuous integration, pair programming, and refactoring code. The goal of agile methods is to provide visibility, adaptability, and business value through a flexible iterative process compared to traditional waterfall development.
Downtown & Infill Tax Increment Districts: Strategies for SuccessVierbicher
This document outlines seven strategies for successful downtown and infill tax increment financing (TIF) districts. It discusses the need for longer timeframes and greater resources for these types of TIDs. It emphasizes staying up-to-date on TID status and being prepared to adapt. It also stresses the importance of matching public improvements to private development timelines and leveraging other funding sources. The document provides case studies of specific cities that have effectively implemented these strategies.
Appraisal and Performance Management in Schools - A practical approachMark S. Steed
This presentation discusses the rationale and methodology that lies behind the Berkhamsted Schools Group appraisal structure. The approach is loosely based on an industry model that considers ‘Attitudes and Behaviours’ as well as ‘Performance outcomes’. The senior team have developed a structure using a suite of appraisal grids for each of the key roles within the organisation: teacher, teaching assistant, Head of Department and Senior Leaders. The teacher appraisal structure applies from Early Years through to Sixth Form.
The presentation was given by Mark S. Steed, Principal of Berkhamsted Schools Group at TLAB15 on Saturday 21st March, 2015 hosted at Berkhamsted School.
This document summarizes research on the economic impacts of green building certification. The research analyzes data on over 28,000 office buildings, including 3,000 with Energy Star or LEED certification. The key findings are:
1) Green-certified buildings have 2-6% higher rents, 6-8% higher effective rents, and 11-13% higher sale prices compared to similar conventional buildings.
2) The rental and value premiums are directly related to characteristics measured by LEED and Energy Star like energy efficiency. Higher LEED certification scores and greater energy cost savings correspond to larger premiums.
3) During the 2007-2009 economic downturn, green-certified buildings experienced smaller declines
The Etsy Shard Architecture: Starts With S and Ends With Hardjgoulah
The document describes Etsy's shard architecture for scaling their MySQL database. Some key points:
- Data is partitioned ("sharded") across multiple MySQL servers to improve performance and scalability.
- Unique IDs like user IDs are used to determine the target shard by taking the modulus of the ID and the number of shards.
- Index shards store metadata like which data shard a given object resides in.
- An ORM handles shard selection and routing queries/writes to the correct shards.
- Migrations can move data from overloaded to underloaded shards to rebalance data distribution.
This letter informs the recipient of changes to their employment terms including an increment to their salary effective April 1, 2014. It congratulates the employee for their contributions and expresses confidence they will continue to perform well and grow with the organization. The letter also notes that all other employment terms remain unchanged and compensation details should be kept confidential between the employee and HR.
How to successfully utilize Tax Increment Financing (TIF) on downtown and infill real estate development projects. Presentation made by Ben Zellers to the American Planning Association Wisconsin conference in June 2014.
Increment Strategy ppt 2012-13 : Play this in slide show modeVipul Saxena
The Indian economy grew at 6.28% in FY 2011-12 but slowed to an estimated growth rate of 5% in FY 2012-13, below the budgeted rate of 7.6%. Inflation increased over this period from 8.4% to 10.44% while industrial production and FDI declined. The mining and metals sector saw negative growth of 2.01% and 2.33% respectively over the two fiscal years. Salary increases across sectors averaged 12% in FY 2012-13, with manufacturing seeing the highest at 15% and financial services the lowest at 10%, as the economy faced challenges of inflation and slowing global growth.
The document discusses increment and decrement operators in C/C++. The increment operator (++) adds 1 to its operand while the decrement operator (--) subtracts 1. Both are unary operators that can be used in prefix or postfix form, affecting whether the operation is performed before or after the expression. The increment and decrement operators have the same precedence and bind from right to left. Examples are provided to demonstrate the behavior of prefix and postfix forms.
The document discusses string operations in C programming. It defines strings as arrays of characters terminated by a null character. It provides examples of declaring and initializing string variables. Functions like strlen, strcpy, strcmp, strcat and reverse are discussed which perform operations on strings like finding length, copying, comparing, concatenating and reversing strings. The document also provides algorithms and functions to check if a string is a palindrome, find a substring and convert a string to uppercase.
1. The document outlines the compensation and benefits provided to three categories of employees - board level executives, below board level executives, and workmen. It details the pay structures, allowances, and perks for each category.
2. Employees receive various allowances including Dearness Allowance, House Rent Allowance, conveyance advances, and reimbursements. The document also describes perks such as furniture schemes, medical benefits, leave travel concessions, and holiday home facilities.
3. Guidelines on compensation and benefits are issued by the Department of Public Enterprises (DPE) for all central public sector enterprises. The document provides information on the guidelines issued by DPE on pay revisions for executives and negotiations with
The incremental model divides a project into a series of increments. Each increment follows the waterfall model by going through planning, modeling, design, construction, testing, and deployment phases to deliver working functionality. As increments are completed, the working system is expanded until the full system is implemented. This allows software to be delivered in early increments while maintaining flexibility to change scope over the course of the project. However, problems can arise if not all requirements are identified upfront.
Tommy Norman gave a presentation on introducing agile software development using Scrum. He began with an overview of agile principles compared to traditional waterfall development. The key aspects of Scrum were then outlined, including sprint planning, daily standups, product backlog refinement, and sprint reviews and retrospectives. The benefits of agile such as visibility, adaptability, and risk reduction were highlighted. Challenges to adopting agile like management buy-in and organizational change were also discussed. The presentation concluded with next steps around research, training, involvement, and coaching.
Normal forest – growing stock and incrementiqbalforestry
This document discusses the concept of a normal forest, which is defined as an ideally constituted forest that can sustain yields indefinitely through balanced age distributions, growing stock, and annual increment removal. A normal forest is characterized by: [1] a normal series of age classes distributed appropriately across the forest; [2] a maximum normal increment given the forest type and site conditions; and [3] a normal growing stock volume indicated by yield tables. The concept of a normal forest provides an ideal standard for comparison to evaluate the condition of an existing forest and ensure maximum sustained benefits from management.
Explanation of the fundamentals of Redux with additional tips and good practices. Presented in the Munich React Native Meetup, so the sample code is using React Native. Additional code: https://github.com/nacmartin/ReduxIntro
An overview of techniques for detecting software variability concepts in sour...Angela Lozano
The document discusses techniques for detecting software variability in source code. It describes key concepts related to variability including features, feature diagrams, mandatory vs optional features, and feature dependencies. It also discusses how mining source code can help identify variable features, variants selected by triggers, and feature dependencies. The document provides examples of how pre-processor directives in code specify selection of variants and notes triggers do not necessarily store the selection of a variant.
The document provides an overview of Agile and Scrum methodologies. It describes key concepts like the Agile manifesto, Scrum roles, ceremonies like daily stand-ups and retrospectives, and practices like user stories, estimation, and burn-down charts. The objective is to familiarize people with the basic principles and processes in Agile and Scrum development.
This document discusses using Scrum for agile software development. It covers planning a project with a product backlog of prioritized user stories, planning sprints by committing to stories and tasks, running sprints with daily standups and a demo at the end, and reporting on burndowns, tests, bugs, and story progress. Visual Studio tools like work items and queries can help manage artifacts for Scrum projects. Iterative development with Scrum focuses on early delivery of valuable features.
Scrum in One Day is a presentation about Scrum and agile principles. It introduces key Scrum concepts like artifacts, roles, and events. The presentation defines Scrum, its pillars of transparency, inspection, and adaptation. It explains Scrum artifacts like product backlog, sprint backlog, burnup and burndown charts. It also covers agile user stories and inception decks. The presentation provides an overview of agile and Scrum to help attendees understand this framework for iterative software development.
The document provides an overview of Scrum, including its values, principles, roles, meetings, artifacts, and processes. The four values of the Agile Manifesto are listed, followed by the twelve principles. Scrum roles include the Product Owner, Scrum Master, and Development Team. Key Scrum events include the Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective meetings. Main artifacts are the Product Backlog, Sprint Backlog, and Sprint Burn Down Chart.
The document discusses backlog grooming, which is the practice of refining high-level requirements in the product backlog to provide more detail and make them ready for development. Key points:
- Backlog grooming helps reduce rework, improves productivity and visibility of progress.
- The process involves prioritizing, sizing, labeling, estimating and preparing requirements/user stories for sprints. Coarse-grained requirements are broken into fine-grained user stories.
- Best practices include ongoing grooming by the product owner with input from customers and developers, prioritizing based on factors like business value and feedback urgency.
Agile & SCRUM - Deep Dive for General Assemblytheresajaustin
A swift look at the relationship between Agile & SCRUM, then a deep dive into the practicalities and basics of SCRUM. Presented at General Assembly NYC in July 2014 to the Product Management class.
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
What is your role as a BA on a Scrum team? How do you fit in? This presentation was given to the IIBA conference in NZ in 2010 by Stephen Reed. Stephen had worked extensively as a BA and moved into using Scrum with multiple teams at a large Insurance company. This experience led to a lot of questions around what the BA should be doing on a Scrum team. This presentation goes some way to listing what worked in the teams Stephen was involved in. The BA role does not change and all the skills of a great BA are necessary still on a great Software Development team, just more focused on being a team member and utilising those skills for the Scrum process of getting working software to the customer with more focus and clarity for the user.
The document discusses various concepts related to agile software development methodology including Scrum, Kanban, sprints, product and sprint backlogs, daily standups, planning and retrospective meetings. It provides details on Scrum roles like Product Owner and Scrum Master and their responsibilities. Various agile terms are defined like velocity, story boards, spikes, impediments and user stories. The advantages of the agile methodology are highlighted.
The document discusses the Agile Manifesto and Scrum framework. It outlines the core values of the Agile Manifesto which emphasize individuals and interactions, working software, customer collaboration, and responding to change over processes, tools, documentation, contracts, and plans. It then provides details on how Scrum is implemented including roles of the Product Owner, Development Team, and Scrum Master. Key Scrum practices like Sprints, Daily Stand-ups, Sprint Planning, Reviews and Retrospectives are defined.
Agile is a software development methodology in which the development is carried out iteratively and the requirements evolve through continuous inspection and adaptation. Some of the most commonly used agile software development methods/frameworks are: Adaptive Software Development (ASD), Extreme Programming (XP), Scrum and Kanban.
Agile and UX, July 8 - Scrum Club, Los Angeles, CAPatrick Neeman
This document discusses how to integrate user experience design into the Scrum agile development process. Some key points:
- Scrum is an agile process that focuses on iterative development through short sprints, daily stand-ups, and retrospectives to improve. UX design fits well by focusing on user research, wireframes, and testing each sprint.
- Roles include the Product Owner who defines features and priorities, the Scrum Master who removes barriers for the team, and a cross-functional team that includes UX designers, developers, and QA.
- Each sprint the team commits to completing user stories or features in a "Definition of Done" state, with demos for the Product Owner.
Scrum is an agile software methodology for managing product development. Above presentation states how joining the scrum activities ( Roles, artifacts and events ), we form a complete scrum cycle, which helps in developing a flexible and holistic Product.
Agile processes like Scrum are needed because software development is complex and requirements often change. Scrum is an agile framework that uses short cycles ("sprints") to incrementally develop products. Key Scrum roles include the Product Owner, Scrum Master, and Team. The Product Owner manages product requirements and priorities. The Scrum Master facilitates the process. The Team does the work. Main Scrum artifacts are the Product Backlog, Sprint Backlog, and Product Increment. The Scrum process involves Sprint Planning, Daily Stand-ups, Sprint Review, and Retrospectives to continuously improve.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
This document provides an overview and summary of Steve Forte's half-day Agile seminar presented by SSW. The seminar covers topics including an introduction to Agile and Scrum, Agile estimation, Agile and offshore teams, and Agile tools. Attendees can ask questions throughout the interactive seminar.
The document discusses key concepts in Agile and Scrum project management frameworks. It outlines some common misconceptions about Agile, describes Scrum roles and ceremonies like sprint planning and review meetings, and emphasizes that adopting Scrum requires changes to team dynamics, skills, and work habits.
Big agile - It's not just for small projects anymoreJesse Fewell
1) Big Agile is applicable to large programs and portfolios, not just small projects. Effective techniques include forming agile teams, aligning iteration cycles across teams, and establishing a "Scrum of Scrums" process to coordinate dependencies.
2) Challenges in big agile include prioritizing work, dependencies between teams, and ensuring strategic alignment. Product and program teams help overcome these challenges and provide value-driven governance.
3) A three-tier framework structures work at the epic, feature, and user story levels. Work is progressively elaborated as it moves closer to delivery. This supports long-term planning while maintaining flexibility.
This is an introductory overview of the Scrum Framework based on the Scrum Guide.
These charts are also the basis for the corresponding presentation available at the Enduring Agile channel on youtube, accessible using the link provided below:
https://youtu.be/eAZyChHY4Jo
The Agile Process - Taming Your Process To Work For YouNowell Strite
The document discusses the Agile process and how it aims to address problems with traditional waterfall approaches. It summarizes the key aspects of Agile including:
- Focusing on iterative delivery of working software over comprehensive documentation.
- Emphasizing collaboration and responsiveness to change over strict contracts and plans.
- Using sprints, daily stand-ups, and retrospectives to keep projects on track and continuously improve.
It then provides more details on how Scrum, one flavor of Agile, structures teams, roles, and the sprint life cycle to help deliver working software in a transparent and adaptive manner.
Understanding Bias: Its Impact on the Workplace and Individualssanjay singh
In the presentation, I delve into what bias is, the different types of biases that commonly occur, and the profound negative impacts they have on both workplace dynamics and individual well-being. Understanding these aspects is the first step towards creating a more equitable and supportive work culture.
CAPACITY BUILDING:HOW TO GROW YOUR INFLUENCE, INCOME & IMPACTTochi22
Don't wish for less problems but for more capacity.
In this slideshare, you will discover the importance of capacity and different critical areas you must build to achieve your dream life.
To get the recording of this seminar, join our community on Clubhouse @ High Impact Makers
Unlocking The Human Element in IT And Service ManagementDario Diament
The book "Unlocking the Human Element in IT" provides a comprehensive guide to understanding and leveraging the human aspects of information technology. Drawing on extensive research and real-world case studies, the book delves into the critical role that people, culture, and organizational dynamics play in the success or failure of IT initiatives.
The Importance of the Human Element in IT
The book begins by highlighting the often-overlooked human dimension of IT, emphasizing that technology alone is not enough to drive meaningful change and innovation. It argues that the true power of IT lies in its ability to empower and engage people, fostering a collaborative and adaptive organizational culture.
Key Themes and Insights
People-Centric Approach: The book underscores the need to shift from a technology-centric mindset to a people-centric approach in IT management. It explores strategies for aligning IT goals with the needs and aspirations of employees, customers, and stakeholders.
Organizational Culture: The authors examine the profound impact of organizational culture on IT initiatives, addressing topics such as change management, leadership, and team dynamics. They provide practical frameworks for cultivating a culture that embraces innovation, collaboration, and continuous learning.
Soft Skills and Talent Management: The book delves into the importance of developing soft skills, such as communication, empathy, and problem-solving, among IT professionals. It also explores effective talent management strategies to attract, retain, and develop high-performing IT teams.
Agile and Adaptive IT: The book highlights the rise of agile and adaptive IT methodologies, emphasizing the need for IT organizations to be nimble, responsive, and customer-centric. It offers guidance on implementing agile practices and fostering a mindset of continuous improvement.
Bridging the IT-Business Divide: The authors address the longstanding challenge of aligning IT with business objectives, providing strategies for enhancing collaboration, communication, and mutual understanding between IT and other organizational functions.
Practical Applications and Case Studies
Throughout the book, the authors present real-world case studies that illustrate the impact of the human element in IT. These case studies cover a range of industries and organizational contexts, offering valuable insights and lessons learned for readers to apply in their own environments.
Conclusion
"Unlocking the Human Element in IT" is a must-read for IT leaders, managers, and professionals who recognize the importance of people, culture, and organizational dynamics in driving successful IT initiatives. By embracing the human element, organizations can unlock the full potential of their technology investments and achieve sustainable, transformative change.
People mentioned:
- Matt Beran
- Deborah Monroe
- NJ Robinson
- Megan Engels
- Gregg Gregory
- Rocky McGuire
Learn more at invgate.com
Certified Administrative Officer CAO.pdfGAFM ACADEMY
The Certified Administrative Officer (CAO) is a gold-standard certification awarded exclusively by the Global Academy of Finance and Management ®. Earning this designation demonstrates that you have skills and experience in office administration which includes events coordination, time management, resource management, Microsoft Office applications, and business communication.
REQUIREMENTS
The Certified Administrative Officer designation requires a diploma or a bachelor's degree in business and administration, or related field.
Two years experience in office administration
Final year graduates with industrial attachment will be considered.
In addition to educational requirements, candidates must have knowledge in Microsoft Office applications, and business communication skills.
To apply: https://gafm.com.my/digital-certification/application-for-certification/
11. Individuals and Interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
12. BE AGILE
-Team and collaboration
- Incremental
- Iterative
-Value driven
- Frequent delivery
- Product quality
- Inspect and adapt
- Self-organisation
35. - Prioritised set of estimated items
- Constantly in change as the situation changes
- Contains stories, bugs, refactorings, …
- Detailed appropriately
- Source of work for the Development team
PRODUCT BACKLOG
37. TASK
Each user story can be separated
into (technical) tasks.
As a plan to accomplish the work.
AS A …
I WANTTO …
SOTHAT …
Set up the database
Create API call
…
46. Be adaptive! Iterate!
Sprint
Fixed timebox in which the Scrum team
delivers a product increment
according to the Definition of Done.
between 1 and 4 weeks
47. SPRINT
Project progresses in sprints
Sprint commitment by Development team
No new requirements during the spint
Scrum team delivers a product increment
48. How do we plan?
Sprint Planning
Timeboxed meeting for the Scrum Team,
to pull work into the Sprint Backlog
max 2 hours per week of sprint
51. RELATIVE ESTIMATES
- Story points are more then just time
- Compare to reference item
- Faster, more accurate planning
- Independent of developer skills
Fibonacci: 1 2 3 5 8 13 ..
52. PLANNING POKER
1 - Product Owner explains item
2 - Developer compares with a reference item
3 - All cards are shown together
4 - Highest and lowest explained
5 -Team gets to a consensus, possible other round
53. Track progress during the sprint?
Daily Scrum
Timeboxed meeting for the Development team
to make sure the sprint goal is reached.
max 15 minutes
54. What did you do yesterday?
What will you be doing today?
Are there any blocking issues?
Everyone. Short.Turn by turn.
And take necessary steps after the Daily Scrum
56. What did we do good in last sprint?
What did we do less in the last sprint?
Are there any questions or uncertainties?
Are there any open items from last retrospective?
Everyone.Write down.
Group the items and discuss. Plan and take action.
58. Updated backlog!
Product Backlog Refinement
Scrum team keeps the product backlog up to date,
to have a shared understanding of what needs to be done
ongoing activity