High Bandwidth Communication
•
2 likes•706 views
What we say isn't always as important as how we say it. Great teams need fast, high fidelity feedback so they can rapidly inspect, improve and adapt. In this talk we'll dive into a favourite agile approach and learn about the what, how and why - with some fun and games.
Report
Share
Report
Share
Recommended
The Daily Scrum (The Scrum Events)
This is my presentation from the 17th Agile Greece meetup. The event was a series of lightning talks about the events of Scrum.
My presentations has a collection of bad and good practices when implementing a Daily Scrum or Daily standup at Scrum.
http://www.meetup.com/Agile-Greece/
EIA 2015 How to Survive a Hackathon
This document provides advice on how to survive and win at a hackathon. It outlines an agenda for the event and introduces the mentors. It emphasizes creating a minimum viable product through prioritizing features and using shortcuts like cloud platforms and drag-and-drop tools. A daily schedule is proposed, with checkpoints to track progress. Teams are advised to dream small, not pivot their idea, help each other, and choose technologies they are familiar with. The overall goal is to build a working product.
Lean and Continuous delivery
The document discusses lean software development principles for achieving continuous delivery, including eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole process. It provides examples of how following these principles can reduce wait times, unnecessary processes, and bugs by making decisions quickly with the whole team and delivering changes more rapidly based on feedback. The overall message is that lean principles can help teams optimize their processes for continuous delivery.
Scrum - Standup meeting
This document discusses the daily scrum meeting in Scrum. The daily scrum has the following objectives: to understand progress made, know the plan for the next 24 hours, and know any impediments. It is attended by committed team members and the Scrum Master. The meeting is held daily at the same time and place, and lasts no more than 15 minutes. Participants take turns answering three questions: what they did yesterday, their plan for today, and any impediments. The benefits are improved transparency, self-commitment, shared understanding, equal treatment of members, early impediment removal, and improved team cohesion.
Daily standup
The slides that I used to help team understand the importance and the structure for the daily standup
Learning Scrum through games
This document outlines a game to teach Scrum concepts like sprints, product backlogs, daily scrums, and sprint planning. Players familiarize themselves with a product backlog and commit to user stories they can complete in 10 minutes during sprint planning. They then have daily scrums and complete a sprint review and retrospective before planning their next sprint. The goal is for players to learn Scrum fundamentals in an engaging game format.
Adopting agile via continuous improvement with workshop
The document discusses adopting an agile framework called Scrum for project management. It provides an overview of agile principles and Scrum methodology. Scrum uses self-organizing cross-functional teams, sprint planning meetings, daily stand-ups, sprint reviews and retrospectives. Key Scrum roles include the Product Owner who prioritizes backlog items, the Scrum Master who facilitates the process, and the Scrum Team. The document reviews Scrum artifacts, meetings, roles and provides guidance on implementation through workshops and examples.
Superfast Development
Presentation on tips and tricks I've learned over the years to develop applications fast. First presented at @frontendparty in New Orleans
Recommended
The Daily Scrum (The Scrum Events)
This is my presentation from the 17th Agile Greece meetup. The event was a series of lightning talks about the events of Scrum.
My presentations has a collection of bad and good practices when implementing a Daily Scrum or Daily standup at Scrum.
http://www.meetup.com/Agile-Greece/
EIA 2015 How to Survive a Hackathon
This document provides advice on how to survive and win at a hackathon. It outlines an agenda for the event and introduces the mentors. It emphasizes creating a minimum viable product through prioritizing features and using shortcuts like cloud platforms and drag-and-drop tools. A daily schedule is proposed, with checkpoints to track progress. Teams are advised to dream small, not pivot their idea, help each other, and choose technologies they are familiar with. The overall goal is to build a working product.
Lean and Continuous delivery
The document discusses lean software development principles for achieving continuous delivery, including eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole process. It provides examples of how following these principles can reduce wait times, unnecessary processes, and bugs by making decisions quickly with the whole team and delivering changes more rapidly based on feedback. The overall message is that lean principles can help teams optimize their processes for continuous delivery.
Scrum - Standup meeting
This document discusses the daily scrum meeting in Scrum. The daily scrum has the following objectives: to understand progress made, know the plan for the next 24 hours, and know any impediments. It is attended by committed team members and the Scrum Master. The meeting is held daily at the same time and place, and lasts no more than 15 minutes. Participants take turns answering three questions: what they did yesterday, their plan for today, and any impediments. The benefits are improved transparency, self-commitment, shared understanding, equal treatment of members, early impediment removal, and improved team cohesion.
Daily standup
The slides that I used to help team understand the importance and the structure for the daily standup
Learning Scrum through games
This document outlines a game to teach Scrum concepts like sprints, product backlogs, daily scrums, and sprint planning. Players familiarize themselves with a product backlog and commit to user stories they can complete in 10 minutes during sprint planning. They then have daily scrums and complete a sprint review and retrospective before planning their next sprint. The goal is for players to learn Scrum fundamentals in an engaging game format.
Adopting agile via continuous improvement with workshop
The document discusses adopting an agile framework called Scrum for project management. It provides an overview of agile principles and Scrum methodology. Scrum uses self-organizing cross-functional teams, sprint planning meetings, daily stand-ups, sprint reviews and retrospectives. Key Scrum roles include the Product Owner who prioritizes backlog items, the Scrum Master who facilitates the process, and the Scrum Team. The document reviews Scrum artifacts, meetings, roles and provides guidance on implementation through workshops and examples.
Superfast Development
Presentation on tips and tricks I've learned over the years to develop applications fast. First presented at @frontendparty in New Orleans
TestMob - Design Thinking in Agile Testing
Design Thinking has gained momentum widely due to its inherent fit to agile and lean product development. Stanford’s D.School Design Thinking crash course and Google Ventures’ Design Sprint further extends it by providing a framework for designing products and services in the context of teams. Can this apply to testing?
Through TestMob, we’ve applied the same process to software testing within agile and non-agile contexts. TestMob incorporates agile and context-driven testing principles and practices of fast feedback, collaboration, exploratory risk-based testing, and team ownership of quality. This hands-on workshop will equip you with the principles, practices, and goals behind TestMob and how you can apply them to your agile teams ASAP. You will learn about the ADAPT model (Analyze, Design, Agree, Plan, Test) patterned after Google's Design Sprint, and run hands-on simulation of most practices.
How to Host a Successful Agile Stand-up Meeting.
The stand-up meeting is considered an important agile practice but why is it so important and how to you get started with this unusual meeting format? When you watch experienced teams run a stand-up, it seems so easy but what are the secret ingredients to hosting a great stand-up meeting? How do you move from the usual 1-hour snore fest status meeting to a short, sharp, engaged, active and valuable ritual? I use the Host Leadership metaphor to help to think about all the aspects needed to run a successful standup meeting.
Beginners Guide to Scrum
Scrum is an iterative method that belongs in the agile camp of how to manage and run projects. It can be used to manage almost any type of project, software, websites, hardware, marketing, event planning, etc. This presentations covers:
Roles in Scrum, Key Points of Scrum, and Actions Done in Scrum such as: Planning Meeting, Completing Work, Daily Scrum Meeting, Sprint Review Meeting, & Retrospective Meeting.
The Way of The Software Craftsman # Part One: The Beginning
“Hold, Break, Leave”
- First, follow all the practices.
- Then, realize and change them.
- Finally, you don't need to think about the rules anymore.
Daily scrum foster team work with just in time planning
How many times have you heard the Development team recite the 3 questions every morning and still fail to finish the sprint? Daily Scrum is an avenue for the team to synchronise and not give a status update. And when a team understands the value of the Daily Scrum, it can help drive the sprint’s success. During this session, we will introduce participants to some tools to achieve this.
Introduction to Agile Development with Scrum
Introduction to Agile Development with Scrum Medill School of Journalism, Northwestern University Thursday, April 2nd
SCRUM, an introduction
Scrum is an agile framework for managing work. It is iterative, incremental and focuses on collaboration and adaptation. Key aspects of Scrum include short iterations called sprints where work is completed and reviewed, daily stand-up meetings to track progress, and roles like Product Owner, Scrum Master and Development Team. Scrum aims to increase transparency, drive progress through commitment to sprints, and provide signals on project status through its meetings and reviews.
Beyond Agile Software
How to move your agile software development process from boring to purposeful and productive. Benefits of agile processes, problems with agile processes and how to give teams autonomy.
Are you engineers stuck in a rut? Maybe what was a good thing has become a drag. Learn strategies for advanced software development processes.
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...
How to run an effective (and fun) standup
The document provides tips for running an effective daily standup meeting that avoids becoming dull or pointless. Some key recommendations include asking questions of individuals rather than the group, varying the speaking order each day, having developers discuss their work with each other, and ending crisply with defined actions. The document also discusses problems like long-winded status reports or discussions instead of updates, and provides solutions such as using a parking lot for topics needing further discussion outside the standup.
Effective Daily Standups
The document discusses effective daily standups in Agile development. It defines standups as 15 minute meetings for teams developing product backlog items. The goals are to assess progress, plan next steps, and identify impediments. Key aspects covered include having standups at the same time and place each day, using a structured format to discuss work completed, upcoming work, and obstacles. The benefits are improved communication, coordination, and quick decision making.
Working with agile development
This document discusses Agile development principles and practices. It compares Scrum and Kanban methodologies. Scrum uses fixed-time sprints while Kanban uses a continuous flow approach. Both aim to deliver working software frequently and respond quickly to changes. Estimation techniques like story points and velocity help plan work. Daily stand-ups, retrospectives and product reviews provide transparency and feedback. While roles may differ, Agile requires collaboration between teams, products owners and managers to deliver value.
Scrum days
Is it possible to introduce Scrum by doing it wrongly? 2 stories about introducing Scrum in Skapiec.pl Many companies are starting the agile transformation with important trainings and exercises. In Skapiec.pl we checked how people can respond with a change at influence of not comfortable set of rules. 2 stories which may give you a lot of thinking.
You can find explanation in polish here: http://czapeczka.com/czy-mozna-wprowadzic-scrum-robiac-zle/
If you would like to have it in english - just ask
Scrum and-xp-from-the-trenches 02 sprint planning
This document outlines an agenda for a Scrum session on preparing for and conducting sprint planning meetings. It discusses best practices for ensuring the product backlog is well-defined before planning begins. During planning, the product owner and team collaborate to determine the sprint goal, select stories for the sprint based on estimates, and make adjustments as needed based on discussions. Estimates can be done using gut feel for simple stories or calculating velocity based on past performance. Maintaining quality is not negotiable, and exceptions require clear justification.
Only Test the Features You Want to Keep
This document discusses the benefits of automated testing and provides an introduction to Behat, an automated testing framework for PHP. It notes that automated tests can catch bugs before they hit production, improve team morale, and allow for faster code iterations. The document then demonstrates how to install and run Behat tests on a Drupal site using Gherkin syntax and scenarios. Resources for learning more about Behat, Mink, and test-driven development are also provided.
Fine-tuning your Creative Production Workflow -- Creative Operations Essentials
When you're managing high volumes of visual assets through a Work-in-Progress (WIP) flow, it's important to diagram, document & analyze your creative production workflow so you can identify bottlenecks and begin to improve.
In this presentation you will learn:
- Assessing the workflow you have
- Finding points for improvement
- Tools to help you along the way (from point solutions to B2C software and enterprise DAM software)
Guest speaker: Brian R. Stuckey, Senior Product Manager @ globaledit.
Watch the full webinar here: http://bit.ly/1T53fo1
This slideshow is part of a "Creative Operations Essentials" webinar series brought to you by Globaledit, the online SaaS platform that empowers creative professionals to manage visual production at scale. You can CAPTURE, REVIEW, APPROVE, MARKUP, SHARE, ARCHIVE your digital files all within Globaledit.
More information about globaledit: www.globaledit.com
142 - Why Agile Falls Apart
This document discusses Agile project management techniques. It outlines the five Scrum rituals: storytime, sprint planning, daily standup, sprint review, and retrospective. It provides tips for daily standups, including sticking to a script, standing, meeting at the same time daily, and having separate Scrum of Scrums meetings for multiple teams. It also covers user story format and acceptance criteria format, noting acceptance criteria should test functionality and include error states. Finally, it asks if the reader has experienced Agile implementations and what has worked well and been hardest to incorporate.
Agile Programming Live - AgilePrague2012
1) The document discusses principles of agile programming such as pair programming, test-driven development, and refactoring.
2) It describes a demonstration of test-driven development using a minesweeper game, highlighting how tests are written first and then code is produced to pass those tests.
3) The document emphasizes that practicing these agile techniques through deliberate practice of coding katas can help programmers improve their skills and "think better" above just the code level. Regular practice is encouraged at meetups like the Prague Coding Dojo.
Sprint Zero in Scrum
This document discusses Sprint Zero, which is the preparation period before real sprints begin for a new Scrum team. Sprint Zero is needed because the product owner and team need time to get acquainted, set up the development environment, establish processes like the definition of done, and clarify roles. The document provides a checklist of activities for Sprint Zero, including ensuring team training, setting up tools and infrastructure, defining the technical architecture and coding standards, and agreeing on the sprint agenda and planning process. It also lists signs of good and bad Scrum practices.
Adopting agile via continuous improvement with workshop by Priyank Shah
The document discusses adopting an agile framework called Scrum for project management. It provides an overview of agile principles and Scrum methodology. Scrum uses self-organizing cross-functional teams, sprint planning meetings, daily stand-ups, sprint reviews and retrospectives. Key Scrum roles include the Product Owner who prioritizes backlog items, the Scrum Master who facilitates the process, and the Scrum Team. The document reviews Scrum artifacts, meetings, roles and provides guidance on implementation through workshops and examples.
Skillswap - Back To Basics
First talk for Back To Basics evening. What is a website? Why should we make one? Perhaps it's best not to make one sometimes.
Scrum
- Scrum is a development process commonly used in game development and other disciplines that uses short iterations called sprints to develop and iterate on features.
- Key roles in Scrum include the Product Owner who defines requirements, the Scrum Master who helps remove blockers, and the Scrum Team who does the development work.
- The document then describes the sprint planning, daily standup, and retrospective meetings that are part of the Scrum process and help ensure teams stay on track and continuously improve.
More Related Content
What's hot
TestMob - Design Thinking in Agile Testing
Design Thinking has gained momentum widely due to its inherent fit to agile and lean product development. Stanford’s D.School Design Thinking crash course and Google Ventures’ Design Sprint further extends it by providing a framework for designing products and services in the context of teams. Can this apply to testing?
Through TestMob, we’ve applied the same process to software testing within agile and non-agile contexts. TestMob incorporates agile and context-driven testing principles and practices of fast feedback, collaboration, exploratory risk-based testing, and team ownership of quality. This hands-on workshop will equip you with the principles, practices, and goals behind TestMob and how you can apply them to your agile teams ASAP. You will learn about the ADAPT model (Analyze, Design, Agree, Plan, Test) patterned after Google's Design Sprint, and run hands-on simulation of most practices.
How to Host a Successful Agile Stand-up Meeting.
The stand-up meeting is considered an important agile practice but why is it so important and how to you get started with this unusual meeting format? When you watch experienced teams run a stand-up, it seems so easy but what are the secret ingredients to hosting a great stand-up meeting? How do you move from the usual 1-hour snore fest status meeting to a short, sharp, engaged, active and valuable ritual? I use the Host Leadership metaphor to help to think about all the aspects needed to run a successful standup meeting.
Beginners Guide to Scrum
Scrum is an iterative method that belongs in the agile camp of how to manage and run projects. It can be used to manage almost any type of project, software, websites, hardware, marketing, event planning, etc. This presentations covers:
Roles in Scrum, Key Points of Scrum, and Actions Done in Scrum such as: Planning Meeting, Completing Work, Daily Scrum Meeting, Sprint Review Meeting, & Retrospective Meeting.
The Way of The Software Craftsman # Part One: The Beginning
“Hold, Break, Leave”
- First, follow all the practices.
- Then, realize and change them.
- Finally, you don't need to think about the rules anymore.
Daily scrum foster team work with just in time planning
How many times have you heard the Development team recite the 3 questions every morning and still fail to finish the sprint? Daily Scrum is an avenue for the team to synchronise and not give a status update. And when a team understands the value of the Daily Scrum, it can help drive the sprint’s success. During this session, we will introduce participants to some tools to achieve this.
Introduction to Agile Development with Scrum
Introduction to Agile Development with Scrum Medill School of Journalism, Northwestern University Thursday, April 2nd
SCRUM, an introduction
Scrum is an agile framework for managing work. It is iterative, incremental and focuses on collaboration and adaptation. Key aspects of Scrum include short iterations called sprints where work is completed and reviewed, daily stand-up meetings to track progress, and roles like Product Owner, Scrum Master and Development Team. Scrum aims to increase transparency, drive progress through commitment to sprints, and provide signals on project status through its meetings and reviews.
Beyond Agile Software
How to move your agile software development process from boring to purposeful and productive. Benefits of agile processes, problems with agile processes and how to give teams autonomy.
Are you engineers stuck in a rut? Maybe what was a good thing has become a drag. Learn strategies for advanced software development processes.
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...
How to run an effective (and fun) standup
The document provides tips for running an effective daily standup meeting that avoids becoming dull or pointless. Some key recommendations include asking questions of individuals rather than the group, varying the speaking order each day, having developers discuss their work with each other, and ending crisply with defined actions. The document also discusses problems like long-winded status reports or discussions instead of updates, and provides solutions such as using a parking lot for topics needing further discussion outside the standup.
Effective Daily Standups
The document discusses effective daily standups in Agile development. It defines standups as 15 minute meetings for teams developing product backlog items. The goals are to assess progress, plan next steps, and identify impediments. Key aspects covered include having standups at the same time and place each day, using a structured format to discuss work completed, upcoming work, and obstacles. The benefits are improved communication, coordination, and quick decision making.
Working with agile development
This document discusses Agile development principles and practices. It compares Scrum and Kanban methodologies. Scrum uses fixed-time sprints while Kanban uses a continuous flow approach. Both aim to deliver working software frequently and respond quickly to changes. Estimation techniques like story points and velocity help plan work. Daily stand-ups, retrospectives and product reviews provide transparency and feedback. While roles may differ, Agile requires collaboration between teams, products owners and managers to deliver value.
Scrum days
Is it possible to introduce Scrum by doing it wrongly? 2 stories about introducing Scrum in Skapiec.pl Many companies are starting the agile transformation with important trainings and exercises. In Skapiec.pl we checked how people can respond with a change at influence of not comfortable set of rules. 2 stories which may give you a lot of thinking.
You can find explanation in polish here: http://czapeczka.com/czy-mozna-wprowadzic-scrum-robiac-zle/
If you would like to have it in english - just ask
Scrum and-xp-from-the-trenches 02 sprint planning
This document outlines an agenda for a Scrum session on preparing for and conducting sprint planning meetings. It discusses best practices for ensuring the product backlog is well-defined before planning begins. During planning, the product owner and team collaborate to determine the sprint goal, select stories for the sprint based on estimates, and make adjustments as needed based on discussions. Estimates can be done using gut feel for simple stories or calculating velocity based on past performance. Maintaining quality is not negotiable, and exceptions require clear justification.
Only Test the Features You Want to Keep
This document discusses the benefits of automated testing and provides an introduction to Behat, an automated testing framework for PHP. It notes that automated tests can catch bugs before they hit production, improve team morale, and allow for faster code iterations. The document then demonstrates how to install and run Behat tests on a Drupal site using Gherkin syntax and scenarios. Resources for learning more about Behat, Mink, and test-driven development are also provided.
Fine-tuning your Creative Production Workflow -- Creative Operations Essentials
When you're managing high volumes of visual assets through a Work-in-Progress (WIP) flow, it's important to diagram, document & analyze your creative production workflow so you can identify bottlenecks and begin to improve.
In this presentation you will learn:
- Assessing the workflow you have
- Finding points for improvement
- Tools to help you along the way (from point solutions to B2C software and enterprise DAM software)
Guest speaker: Brian R. Stuckey, Senior Product Manager @ globaledit.
Watch the full webinar here: http://bit.ly/1T53fo1
This slideshow is part of a "Creative Operations Essentials" webinar series brought to you by Globaledit, the online SaaS platform that empowers creative professionals to manage visual production at scale. You can CAPTURE, REVIEW, APPROVE, MARKUP, SHARE, ARCHIVE your digital files all within Globaledit.
More information about globaledit: www.globaledit.com
142 - Why Agile Falls Apart
This document discusses Agile project management techniques. It outlines the five Scrum rituals: storytime, sprint planning, daily standup, sprint review, and retrospective. It provides tips for daily standups, including sticking to a script, standing, meeting at the same time daily, and having separate Scrum of Scrums meetings for multiple teams. It also covers user story format and acceptance criteria format, noting acceptance criteria should test functionality and include error states. Finally, it asks if the reader has experienced Agile implementations and what has worked well and been hardest to incorporate.
Agile Programming Live - AgilePrague2012
1) The document discusses principles of agile programming such as pair programming, test-driven development, and refactoring.
2) It describes a demonstration of test-driven development using a minesweeper game, highlighting how tests are written first and then code is produced to pass those tests.
3) The document emphasizes that practicing these agile techniques through deliberate practice of coding katas can help programmers improve their skills and "think better" above just the code level. Regular practice is encouraged at meetups like the Prague Coding Dojo.
What's hot (18)
The Way of The Software Craftsman # Part One: The Beginning
The Way of The Software Craftsman # Part One: The Beginning
Daily scrum foster team work with just in time planning
Daily scrum foster team work with just in time planning
Fine-tuning your Creative Production Workflow -- Creative Operations Essentials
Fine-tuning your Creative Production Workflow -- Creative Operations Essentials
Similar to High Bandwidth Communication
Sprint Zero in Scrum
This document discusses Sprint Zero, which is the preparation period before real sprints begin for a new Scrum team. Sprint Zero is needed because the product owner and team need time to get acquainted, set up the development environment, establish processes like the definition of done, and clarify roles. The document provides a checklist of activities for Sprint Zero, including ensuring team training, setting up tools and infrastructure, defining the technical architecture and coding standards, and agreeing on the sprint agenda and planning process. It also lists signs of good and bad Scrum practices.
Adopting agile via continuous improvement with workshop by Priyank Shah
The document discusses adopting an agile framework called Scrum for project management. It provides an overview of agile principles and Scrum methodology. Scrum uses self-organizing cross-functional teams, sprint planning meetings, daily stand-ups, sprint reviews and retrospectives. Key Scrum roles include the Product Owner who prioritizes backlog items, the Scrum Master who facilitates the process, and the Scrum Team. The document reviews Scrum artifacts, meetings, roles and provides guidance on implementation through workshops and examples.
Skillswap - Back To Basics
First talk for Back To Basics evening. What is a website? Why should we make one? Perhaps it's best not to make one sometimes.
Scrum
- Scrum is a development process commonly used in game development and other disciplines that uses short iterations called sprints to develop and iterate on features.
- Key roles in Scrum include the Product Owner who defines requirements, the Scrum Master who helps remove blockers, and the Scrum Team who does the development work.
- The document then describes the sprint planning, daily standup, and retrospective meetings that are part of the Scrum process and help ensure teams stay on track and continuously improve.
Techhub Riga - tm 27.07
This document summarizes Toms Bauģis' experience developing open source software and working at Parse.ly. It discusses his work on the Hamster time tracking project from 2012, contributions to GNOME, and lessons learned. It also outlines his role as employee #4 at Parse.ly, focusing on communication, version control, work organization, and observations about leading an open source project.
Scrum소개
The document introduces Scrum and its roles, artifacts, and activities. It discusses the Scrum process including sprint planning, daily standups, sprint demos, and retrospectives. It emphasizes that teams should strictly follow Scrum practices like having a product backlog, sprint backlog, and definition of done to achieve the benefits of an agile framework. Failing to properly implement Scrum can undermine its effectiveness.
Scrum
The document discusses the key aspects of implementing Scrum at Paylogic. It describes why Scrum works through better control, incremental delivery of business value, and empowering self-managed teams. It outlines the Scrum process, including artifacts like the product and sprint backlogs, daily standups, sprints, and retrospectives. It defines the roles of product owner and Scrum master. Sprints are proposed to last 1 week to provide fine-grained control and ensure quality through frequent deliveries. The first sprints would focus on core features and getting initial feedback to adjust subsequent sprints.
Scrum
The document provides an overview of the Scrum process for agile software development. It describes Scrum as using short cycles of inspection and adaptation rather than defined phases. The main Scrum cycles are sprints, which last a month, and daily Scrums. A cross-functional Scrum team consisting of a product owner, Scrum master, and developers work in sprints to implement prioritized backlog items. Daily Scrums are 15-minute stand-up meetings to track progress. At the end of each sprint, there is a sprint review demonstration and inspection where feedback is collected to improve the process.
Scrum shuhari
This document discusses the concept of "Scrum Shu Ha Ri" which refers to the three stages of learning an agile framework like Scrum: follow (Shu), detach/break limits (Ha), and create/innovate (Ri). It encourages moving from strictly following Scrum processes to adapting and strengthening Scrum with techniques like acceptance test-driven development, visual management, and integrating ideas from Kanban and lean startup. The ultimate goal is to understand Scrum's teachings and invent your own unique approach to agility.
Scrum Anti Patterns
Anti-patterns are a commonly used process, structure, or pattern of action that despite initially appearing to be an appropriate and effective response to a problem, has more bad consequences than good ones. Another solution exists that is documented, repeatable, and proven to be effective.(Wikipedia)
The most of the issues we are facing in every Scrum implementation are common and well known, There are anti-patterns that lead to this issues and there are effective known patterns to overcome these issues.
We are going to talk about the common issues, its causes and how to avoid it like long and ineffective meetings, Unorganized backlog, Amount of details in stories, messy code base, huge technical debt, estimation, Unfinished work at end of sprint ...etc.
Bogdan Onyshchenko: Scrum AND. How to make your Scrum implementation even bet...
Bogdan Onyshchenko: Scrum AND. How to make your Scrum implementation even better? (UA)
Ukraine Online PMDay 2023 Winter
Website - www.pmday.org/online
Youtube - https://www.youtube.com/startuplviv
FB - https://www.facebook.com/pmdayconference
Extreme Programming
Introduction to the fundamentals of eXtreme programming (XP). XP is a software development approach which stresses on improving software quality and respond according to changing business requirements.
Agile writer
This document provides an overview of Agile development methods and the Scrum framework. It describes the basics of Agile, including iterative development and prioritizing flexibility over following a strict plan. The Scrum framework is then explained, outlining the roles of Product Owner, Scrum Master, and team. Key Scrum ceremonies like sprint planning, daily standups, sprint reviews, and retrospectives are also summarized.
22-AnOverviewOfScrum.pptx
Scrum is an agile process that focuses on delivering the highest priority features in short iterations called sprints. During a sprint, a self-organizing team works on user stories from the product backlog and meets daily to track progress. At the end of a sprint, working software is demoed to stakeholders. Scrum uses roles like product owner, ScrumMaster, and team as well as artifacts like product backlog, sprint backlog, and burn down charts to help deliver value quickly.
AGILE! Who cares - Tell me what to do @ADC2014
"AGILE! Who cares - Tell Me What To Do. " I presented this at Agile Day Conference 2014 in Pune, India http://www.agiledayconference.com/conference-in-pune
I bet you have encountered this title in your role (e.g. Agile Coach or Mentor) when helping teams in transitioning to Agile. So I did encounter this too and in one such discussion, Chris (Principal Architect) asked me to share my thoughts on handling a Scrum team who simply wanted to be “told what to do”. On the surface, this doesn't seem like such a bad thing. In fact, I’ll bet these folks are bright, capable and work very hard. So if there is an issue with this in agile teams, what is it? And why would it be a problem? Hence this session is about "Transitioning to Agile".
Scrum
Scrum is a framework for managing complex work that emphasizes iterative development, daily self-organization, and accountability. It consists of roles like the Product Owner, Scrum Master, and team. The team works in short cycles called sprints that involve sprint planning, daily standups, a review, and retrospective. The goal is to deliver value continuously through working software and transparency using artifacts like the product and sprint backlogs.
KNOLX - SCRUM ANTI-PATTERNS_SEP 02, 2022_PPT.pptx.pdf
The document discusses Scrum anti-patterns. It begins by defining anti-patterns as ineffective solutions to recurring problems that can be counterproductive. It then provides examples of anti-patterns for the Product Owner, Scrum Master, development team, stakeholders, and Scrum events like the daily scrum, sprint planning and review meetings. Specific anti-patterns mentioned include a poorly managed product backlog, a Scrum Master taking a command and control approach, and stakeholders trying to label all requirements as bugs. The document emphasizes that understanding anti-patterns is important to recognize when the wrong path has been taken and find a better solution.
Black Ops Testing Workshop from Agile Testing Days 2014
The document summarizes notes from a testing workshop on the Redmine project management application. Participants tested various aspects of Redmine and identified 15 bugs, including issues with PDF exports not containing all data, character encoding problems in CSVs, ability to delete the only admin account, and other data validation and synchronization bugs. Workshop leaders provided hints and interrupts to prompt deeper investigation and testing of areas like HTTP traffic, DOM manipulation, and breaking file exports.
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
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.
Similar to High Bandwidth Communication (20)
Adopting agile via continuous improvement with workshop by Priyank Shah
Adopting agile via continuous improvement with workshop by Priyank Shah
Bogdan Onyshchenko: Scrum AND. How to make your Scrum implementation even bet...
Bogdan Onyshchenko: Scrum AND. How to make your Scrum implementation even bet...
KNOLX - SCRUM ANTI-PATTERNS_SEP 02, 2022_PPT.pptx.pdf
KNOLX - SCRUM ANTI-PATTERNS_SEP 02, 2022_PPT.pptx.pdf
Black Ops Testing Workshop from Agile Testing Days 2014
Black Ops Testing Workshop from Agile Testing Days 2014
Recently uploaded
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd test bank.docx
https://qidiantiku.com/test-bank-for-small-business-management-an-entrepreneurs-guidebook-8th-edition-by-mary-jane-byrd.shtml
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
In the ever-evolving world of logistics, staying ahead of the curve is crucial. Industry expert Neal Elbaum highlights the top five trends shaping the logistics industry in 2024, offering valuable insights into the future of supply chain management.
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
The Ready-Made Garments (RMG) industry in Bangladesh is a cornerstone of the economy, but increasing costs and stagnant productivity pose significant challenges to profitability. This study explores the implementation of Lean Management in the Sampling Section of RMG factories to enhance productivity. Drawing from a comprehensive literature review, theoretical framework, and action research methodology, the study identifies key areas for improvement and proposes solutions.
Through the DMAIC approach (Define, Measure, Analyze, Improve, Control), the research identifies low productivity as the primary problem in the Sampling Section, with a PPH (Productivity per head) of only 4.0. Using Lean Management techniques such as 5S, Standardized work, PDCA/Kaizen, KANBAN, and Quick Changeover, the study addresses issues such as pre and post Quick Changeover (QCO) time, improper line balancing, and sudden plan changes.
The research employs regression analysis to test hypotheses, revealing a significant correlation between reducing QCO time and increasing productivity. With a regression equation of Y = -0.000501X + 6.72 and an R-squared value of 0.98, the study demonstrates a strong relationship between the independent variables (QCO downtime and improper line balancing downtime) and the dependent variable (productivity per head).
The findings suggest that by implementing Lean Management practices and addressing key productivity inhibitors, RMG factories can achieve substantial improvements in efficiency and profitability. The study provides valuable insights for practitioners, policymakers, and researchers seeking to enhance productivity in the RMG industry and similar manufacturing sectors.
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
M249 Saw marksman PMIThe Squad Automatic Weapon (SAW), or 5.56mm M249 is an individually portable, gas operated, magazine or disintegrating metallic link-belt fed, light machine gun with fixed headspace and quick change barrel feature. The M249 engages point targets out to 800 meters, firing the improved NATO standard 5.56mm cartridge. The SAW forms the basis of firepower for the fire team. The gunner has the option of using 30-round M16 magazines or linked ammunition from pre-loaded 200-round plastic magazines. The gunner's basic load is 600 rounds of linked ammunition. The SAW was developed through an initially Army-led research and development effort and eventually a Joint NDO program in the late 1970s/early 1980s to restore sustained and accurate automatic weapons fire to the fire team and squad. When actually fielded in the mid-1980s, the SAW was issued as a one-for-one replacement for the designated "automatic rifle" (M16A1) in the Fire Team. In this regard, the SAW filled the void created by the retirement of the Browning Automatic Rifle (BAR) during the 1950s because interim automatic weapons (e.g. M-14E2/M16A1) had failed as viable "base of fire" weapons.
Early in the SAW's fielding, the Army identified the need for a Product Improvement Program (PIP) to enhance the weapon. This effort resulted in a "PIP kit" which modifies the barrel, handguard, stock, pistol grip, buffer, and sights.
The M249 machine gun is an ideal complementary weapon system for the infantry squad platoon. It is light enough to be carried and operated by one man, and can be fired from the hip in an assault, even when loaded with a 200-round ammunition box. The barrel change facility ensures that it can continue to fire for long periods. The US Army has conducted strenuous trials on the M249 MG, showing that this weapon has a reliability factor that is well above that of most other small arms weapon systems. Today, the US Army and Marine Corps utilize the license-produced M249 SAW.
9 Ways Managers Kill Morale (and What to Do Instead)
This presentation, "The Morale Killers: 9 Ways Managers Unintentionally Demotivate Employees (and How to Fix It)," is a deep dive into the critical factors that can negatively impact employee morale and engagement. Based on extensive research and real-world experiences, this presentation reveals the nine most common mistakes managers make, often without even realizing it.
The presentation begins by highlighting the alarming statistic that 70% of employees report feeling disengaged at work, underscoring the urgency of addressing this issue. It then delves into each of the nine "morale killers," providing clear explanations and illustrative examples.
1. Ignoring Achievements: The presentation emphasizes the importance of recognizing and rewarding employees' efforts, tailored to their individual preferences.
2. Bad Hiring/Promotions & Broken Promises: It reveals the detrimental effects of poor hiring and promotion decisions, along with the erosion of trust that results from broken promises.
3. Treating Everyone Equally & Tolerating Poor Performance: This section stresses the need for fair treatment while acknowledging that employees have different needs. It also emphasizes the importance of addressing poor performance promptly.
4. Stifling Growth & Lack of Interest: The presentation highlights the importance of providing opportunities for learning and growth, as well as showing genuine care for employees' well-being.
5. Unclear Communication & Micromanaging: It exposes the frustration and resentment caused by vague expectations and excessive control, advocating for clear communication and employee empowerment.
The presentation then shifts its focus to the power of recognition and empowerment, highlighting how a culture of appreciation can fuel engagement and motivation. It provides actionable takeaways for managers, emphasizing the need to stop demotivating behaviors and start actively fostering a positive workplace culture.
The presentation concludes with a strong call to action, encouraging viewers to explore the accompanying blog post, "9 Proven Ways to Crush Employee Morale (and How to Avoid Them)," for a more in-depth analysis and practical solutions.
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
Disaster management;
Cyclone Disaster Management;;
Biparjoy Cyclone Case Study;
Meteorological Observations;
Best practices in Disaster Management;
Synchronization of Agencies;
GSDMA in Cyclone disaster Management;
History of Cyclone in Arabian ocean;
Intensity of Cyclone in Gujarat;
Cyclone preparedness;
Miscellaneous observations - Biparjoy cyclone;
Role of social Media in Disaster Management;
Unique features of Biparjoy cyclone;
Role of IMD in Biparjoy Prediction;
Lessons Learned; Disaster Preparedness; published paper;
Case study; for disaster management agencies; for guideline to manage cyclone disaster; cyclone management; cyclone risks; rescue and rehabilitation for cyclone; timely evacuation during cyclone; port closure; tourism closure etc.
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...Istanbul Beykent University (İstanbul Beykent Üniversitesi)
Many companies have perceived CRM that accompanied by numerous
uncoordinated initiatives as a technological solution for problems in
individual areas. However, CRM should be considered as a strategy when
a company decides to implement it due to its humanitarian, technological
and process-related effects (Mendoza et al., 2007, p. 913). CRM is
evolving today as it should be seen as a strategy for maintaining a longterm relationship with customers.
A CRM business strategy includes the internet with the marketing,
sales, operations, customer services, human resources, R&D, finance, and
information technology departments to achieve the company’s purpose and
maximize the profitability of customer interactions (Chen and Popovich,
2003, p. 673).
After Corona Virus Disease-2019/Covid-19 (Coronavirus) first
appeared in Wuhan, China towards the end of 2019, its effects began to
be felt clearly all over the world. If the Coronavirus crisis is not managed
properly in business-to-business (B2B) and business-to-consumer
(B2C) sectors, it can have serious negative consequences. In this crisis,
companies can typically face significant losses in their sales performance,
existing customers and customer satisfaction, interruptions in operations
and accordingly bankruptcy一比一原版(philau毕业证书)美国费城大学毕业证如何办理
原版一模一样【微信：741003700 】【(philau毕业证书)美国费城大学毕业证成绩单】【微信：741003700 】学位证，留信认证（真实可查，永久存档）原件一模一样纸张工艺/offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原。
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
【主营项目】
一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！
二.真实使馆公证(即留学回国人员证明,不成功不收费)
三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）
四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度)
如果您处于以下几种情况：
◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】
◇面对父母的压力，希望尽快拿到；
◇不清楚认证流程以及材料该如何准备；
◇回国时间很长，忘记办理；
◇回国马上就要找工作，办给用人单位看；
◇企事业单位必须要求办理的
◇需要报考公务员、购买免税车、落转户口
◇申请留学生创业基金
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
办理(philau毕业证书)美国费城大学毕业证【微信：741003700 】外观非常简单，由纸质材料制成，上面印有校徽、校名、毕业生姓名、专业等信息。
办理(philau毕业证书)美国费城大学毕业证【微信：741003700 】格式相对统一，各专业都有相应的模板。通常包括以下部分：
校徽：象征着学校的荣誉和传承。
校名:学校英文全称
授予学位：本部分将注明获得的具体学位名称。
毕业生姓名：这是最重要的信息之一，标志着该证书是由特定人员获得的。
颁发日期：这是毕业正式生效的时间，也代表着毕业生学业的结束。
其他信息：根据不同的专业和学位，可能会有一些特定的信息或章节。
办理(philau毕业证书)美国费城大学毕业证【微信：741003700 】价值很高，需要妥善保管。一般来说，应放置在安全、干燥、防潮的地方，避免长时间暴露在阳光下。如需使用，最好使用复印件而不是原件，以免丢失。
综上所述，办理(philau毕业证书)美国费城大学毕业证【微信：741003700 】是证明身份和学历的高价值文件。外观简单庄重，格式统一，包括重要的个人信息和发布日期。对持有人来说，妥善保管是非常重要的。
Maximize Your Efficiency with This Comprehensive Project Management Platform ...
In today's work environment, staying organized and productive can be a daunting challenge. With multiple tasks, projects, and tools to juggle, it's easy to feel overwhelmed and lose focus. Fortunately, liftOS offers a comprehensive solution to streamline your workflow and boost your productivity. This innovative platform brings together all your essential tools, files, and tasks into a single, centralized workspace, allowing you to work smarter and more efficiently.
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Is Agile dead? It depends on what you mean by 'Agile'. If you mean that the organizations are not getting the promised benefits because they were focusing too much on the team-level agile "ways of working" instead of systemic global improvements -- then we are in agreement. It is a misunderstanding of Agility that led us down a dead-end. At Org Topologies, we see bright sparks -- the signs of the 'second wave of Agile' as we call it. The emphasis is shifting towards both in-team and inter-team collaboration. Away from false dichotomies. Both: team autonomy and shared broad product ownership are required to sustain true result-oriented organizational agility. Org Topologies is a package offering a visual language plus thinking tools required to communicate org development direction and can be used to help design and then sustain org change aiming at higher organizational archetypes.
Recently uploaded (11)
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
9 Ways Managers Kill Morale (and What to Do Instead)
9 Ways Managers Kill Morale (and What to Do Instead)
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
team presentation of the role and responsibility of HSE teamreviewed.pptx
team presentation of the role and responsibility of HSE teamreviewed.pptx
Maximize Your Efficiency with This Comprehensive Project Management Platform ...
Maximize Your Efficiency with This Comprehensive Project Management Platform ...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
High Bandwidth Communication
- 3. ●Lowers the barrier ●Minimum viable framework ●Not just for software development! Why?
- 5. ●Continuous improvement ●Empirical process control ●Deming A great way to get fit!
- 7. backfeed
- 8. Daily Scrum Sprint Planning Sprint Review Sprint Retrospective Backlog Refinement
- 9. big small
- 10. Daily Scrum Sprint Planning Sprint Review Sprint Retrospective Backlog Refinement
- 11. Scrum from Hell
- 12. 1. Six volunteers 2. Join me on the stage
- 13. 3. Pick your Scrum Master!
- 14. Now you’re part of a scrum team 4. Let’s meet your task board
- 15. To Do Doing Done Search Nav Bar Home page Twitter feed on homepage Link to Instagram Account About Us page Link to Twitter AWS Infra User Admin feature Site instance Layout and design Go Live Party
- 16. 5. Look at your card – but keep it quiet!
- 17. ●What I did yesterday ●What I’m doing today ●What’s blocking me The ‘What’ What How Why
- 18. We’re about to begin…
- 19. ●Watch what they’re doing ●Make a note of it ●Let’s review together at the end! More audience participation required
- 20. 6. Let’s begin
- 21. To Do Doing Done Search Nav Bar Home page Twitter feed on homepage Link to Instagram Account About Us page Link to Twitter AWS Infra User Admin feature Site instance Layout and design Go Live Party
- 22. ●What happened there? ●How did they communicate? ●Signals or noise? Retrospective
- 23. 7% words 38% vocals 55% expressions, gestures, posture What How Why Going through the motions?
- 24. backfeed
- 25. coach the how
- 27. backfeed
- 28. What How Why
- 29. smooth
- 30. improve
- 31. “sustainably reducing the lead time to business impact” Dan North
- 32. big small
- 33. SCSISource: Herb Johnson. 2010. USB or FireWire to SCSI for Macs. [ONLINE] Available at: http://www.retrotechnology.com/herbs_stuff/usb_scsi_conn.jpg.