Agile EE 2010
•Download as PPT, PDF•
0 likes•291 views
The document discusses several Agile methodologies and techniques for distributed teams. It covers Scrum, Extreme Programming (XP), Kanban, challenges of distributed teams, visualization tools like burn down charts and task boards, and games that can help improve team cohesion and efficiency like 6 hats brainstorming and scrum games.
Report
Share
Report
Share
![Quick look on Agile methodologies: ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Retrospective
The purpose of the Sprint Retrospective is to:
- Inspect how the last Sprint went with regards to people, relationships, process, and tools;
- Identify and order the major items that went well and potential improvements; and,
- Create a plan for implementing improvements to the way the Scrum Team does its work.
Олександр Стороха "Why you can`t lead alone huge team effectively or importan...
Lviv Project Management Day 2017
Олександр Стороха "Why you can`t lead alone huge team effectively or importance of delegation and developing agile leaders"
Ксенія Кобрин "Stop babysitting your teams, let them grow!" Lviv Project Mana...
Scrum masters should let teams grow independently and avoid excessively managing them. Product owners are not owners of the team, and scrum masters are not mothers. During planning, the whole scrum team which includes the product owner, scrum master, and development team should collaborate through planning poker and backlog refinement to clarify stories, dependencies, and acceptance criteria before sprints. This helps estimate work and refine the backlog into smaller batches for the next iteration. Scrum masters must ensure planning and refinement events are consistent and that incomplete stories don't enter sprints.
Effective Daily Scrum Patterns
This webinar highlights different styles of useful daily scrum patterns.
Should your Daily Scrum be done round robin, random order, or should you “Walk the Items” instead? Should you run your Daily Scrum quite differently if your team is remote or distributed? What are some good techniques for distributed Daily Scrums These are all challenging questions, and Scrum Patterns help us decide what to do when there are no straightforward, easy answers, for how to implement Scrum.
Original copy at https://www.synerzip.com/webinar/webinar-effective-daily-scrum-patterns-march-2013/
Артем Биковець "Why Scrum is so often "Failed" and criticised" Lviv Project M...
Scrum is often criticized as "failed" due to typical barriers such as a project mindset instead of a product mindset, isolated teams instead of interconnected networks, and rushing into agile practices without establishing software craftsmanship. The document outlines seven common barriers to successful scrum implementation and provides solutions such as adopting a product mindset, establishing self-managing cross-functional teams, emphasizing software craftsmanship principles, replacing heroism with collaborative problem solving, taking an empirical view instead of a certainty mindset, practicing professional scrum over mechanical scrum processes, and scaling the product rather than scrum practices.
Agile Retrospectives
This document discusses Agile Retrospectives, which are meetings held at the end of an iteration or project to inspect what went well and identify improvements for the next iteration. The document outlines how to effectively plan and facilitate a retrospective using different frameworks and activities. It emphasizes the importance of preparing well, deliberately facilitating the meeting, varying activities to engage participants, and tracking any actions identified to ensure continuous improvement.
Agile Retrospective - part I
Retrospective is probably the most important ceremony as it helps to improve the team.
There are great sources how to do retrospective.
Agile Retrospectives
The document discusses agile retrospectives and provides guidance on facilitating effective retrospectives. It outlines a 5-step format for retrospectives: 1) set the stage, 2) gather data, 3) generate insights, 4) decide what to do, and 5) close the retrospective. The facilitator's role is to make sure everyone contributes and a plan is created without solving problems for the team. The Scrum Master reflects the team's behavior back to help them improve. Team members should focus on the content, discuss openly, and make decisions. Retrospectives help teams continuously improve and change their definition of done, working agreements, and generate action items.
Recommended
Retrospective
The purpose of the Sprint Retrospective is to:
- Inspect how the last Sprint went with regards to people, relationships, process, and tools;
- Identify and order the major items that went well and potential improvements; and,
- Create a plan for implementing improvements to the way the Scrum Team does its work.
Олександр Стороха "Why you can`t lead alone huge team effectively or importan...
Lviv Project Management Day 2017
Олександр Стороха "Why you can`t lead alone huge team effectively or importance of delegation and developing agile leaders"
Ксенія Кобрин "Stop babysitting your teams, let them grow!" Lviv Project Mana...
Scrum masters should let teams grow independently and avoid excessively managing them. Product owners are not owners of the team, and scrum masters are not mothers. During planning, the whole scrum team which includes the product owner, scrum master, and development team should collaborate through planning poker and backlog refinement to clarify stories, dependencies, and acceptance criteria before sprints. This helps estimate work and refine the backlog into smaller batches for the next iteration. Scrum masters must ensure planning and refinement events are consistent and that incomplete stories don't enter sprints.
Effective Daily Scrum Patterns
This webinar highlights different styles of useful daily scrum patterns.
Should your Daily Scrum be done round robin, random order, or should you “Walk the Items” instead? Should you run your Daily Scrum quite differently if your team is remote or distributed? What are some good techniques for distributed Daily Scrums These are all challenging questions, and Scrum Patterns help us decide what to do when there are no straightforward, easy answers, for how to implement Scrum.
Original copy at https://www.synerzip.com/webinar/webinar-effective-daily-scrum-patterns-march-2013/
Артем Биковець "Why Scrum is so often "Failed" and criticised" Lviv Project M...
Scrum is often criticized as "failed" due to typical barriers such as a project mindset instead of a product mindset, isolated teams instead of interconnected networks, and rushing into agile practices without establishing software craftsmanship. The document outlines seven common barriers to successful scrum implementation and provides solutions such as adopting a product mindset, establishing self-managing cross-functional teams, emphasizing software craftsmanship principles, replacing heroism with collaborative problem solving, taking an empirical view instead of a certainty mindset, practicing professional scrum over mechanical scrum processes, and scaling the product rather than scrum practices.
Agile Retrospectives
This document discusses Agile Retrospectives, which are meetings held at the end of an iteration or project to inspect what went well and identify improvements for the next iteration. The document outlines how to effectively plan and facilitate a retrospective using different frameworks and activities. It emphasizes the importance of preparing well, deliberately facilitating the meeting, varying activities to engage participants, and tracking any actions identified to ensure continuous improvement.
Agile Retrospective - part I
Retrospective is probably the most important ceremony as it helps to improve the team.
There are great sources how to do retrospective.
Agile Retrospectives
The document discusses agile retrospectives and provides guidance on facilitating effective retrospectives. It outlines a 5-step format for retrospectives: 1) set the stage, 2) gather data, 3) generate insights, 4) decide what to do, and 5) close the retrospective. The facilitator's role is to make sure everyone contributes and a plan is created without solving problems for the team. The Scrum Master reflects the team's behavior back to help them improve. Team members should focus on the content, discuss openly, and make decisions. Retrospectives help teams continuously improve and change their definition of done, working agreements, and generate action items.
Execute Your Strategy Before It Executes You
This document outlines a 4-step process for transforming strategic plans into strategic action: 1) initialize and start by balancing focus on a single idea with openness to possibilities, 2) explore and develop by balancing a single option with multiple options, 3) decide and act by balancing a single solution with multiple solutions, and 4) maintain and sustain by balancing a generic with customized approaches. It emphasizes balancing focus and possibilities at each step to maintain momentum from idea to execution.
The Slippery Slope
This document discusses how teams can unintentionally slip away from Agile practices over time if they are not careful. It provides examples of common "slippery slopes" such as skipping story estimation, not using relative sizing, carrying stories between sprints, and stopping daily standups. The author urges coaches to focus on helping teams form good habits in the first 3-6 months and celebrate successes while also constructively pointing out areas for improvement. Teams are reminded that Agile requires discipline and that changing habits is difficult, so they should avoid picking up bad practices.
10 Graphic design tools and graphic designer must haves
4- The Extraordinary Wacom BambooIf you are a designer, and you don't have one of these in your "des...
Facebook retrospective
This document describes a retrospective method called the "Facebook retrospective" designed by the author. It involves printing topics related to the Scrum process on cards and having team members vote on whether they "like" or "dislike" each topic. The results are analyzed to identify topics the team agrees or disagrees on, and actions are generated for topics of disagreement. The retrospective is timeboxed to one hour and includes an energizer, voting activity, discussion of results, and generating actions for the next sprint. Feedback from trying this method is to allow a neutral option for voting and to allow custom topic cards.
Design Sprint
Do you know what Design Sprint is? Are you able to easily explain it to your Boss? Don't worry; we've got you covered!
Jake Knapp explains Design Sprint as - "The 'greatest hits' of business strategy, innovation, behavioural science, and more — packaged into a step-by-step process that any team can use."
1. Map: Map out the problem and pick a critical area to focus
2. Sketch: Sketch out competing solutions on paper
3. Decide: Make decisions and turn your ideas into testable hypotheses
4. Prototype: Hack together a realistic prototype
5. Test: Get feedback from real-life users
These slides highlights the essential tasks to be done each day, eventually resulting in a five-day process for validating ideas and solving challenges.
Hands on with the Design Studio Method
In this hands-on, interactive session, Len will share some basic principles of the design studio method, share how you can use the design studio method to rapidly generate ideas for your own digital products, and then facilitate a mini design studio challenge that is sure to leave you with practical skills to apply to your work and bonded with meetup attendees.
Design Sprint - Day 1
This 3 Day Design Sprint was delivered to teenagers between the ages of 13 -18 to teach them how to quickly test ideas without writing a line of code. It has been adapted from Tom Lombardo's course from Fresh Tiled Soil.
Attaining Agile Fluency: Coaching Techniques - Focus on Goals Over Process
What is coaching?
“It is helping to identify the skills and capabilities that are within the person, and enabling them to use them to the best of their ability” — wikipedia
Individuals and Interactions over Process and Tools.
The above is one of the 4 values espoused in the manifesto but yet it is common to see many agile coaches engage with teams and organisations advocating more and more processes. This is a common sight with new teams and also with teams on the path of agile transition from few months to few years irrespective of the competency, skills and maturity of the teams. Agile Fluency model created by Diana Larse and James Shore highlights the focus on value over compliance and practices at any given level
“ Team fluency depends on more than just the capability of the individuals on the team. It also depends on management structures, relationships, organizational culture, and more. Don’t make the mistake of blaming individuals for low team fluency, or assuming that one highly-skilled individual will guarantee high team fluency ”
An agile coach responsible for building high performing teams will need right set of powerful tools and techniques to leverage while working with teams and also to set the right expectations to both management and teams. This talk will draw from experience using few such powerful tools mentioned below while coaching teams attain fluency.
1) Using Agile Fluency @ High Level to Set Expectations
2) Setting Team Norms & Working Agreements
3) Deliberate Practice
4) Creating Enablers for a Learning Organisation
5) Simple Measures
Design Sprint
The document discusses the design sprint process, which involves prototyping, validating, and learning over the course of a week to address an idea. On Monday, the team unpacks the problem by creating user stories and scoping it. On Tuesday, they sketch and take notes to generate ideas. Wednesday involves deciding on a path by critiquing ideas. On Thursday, the team focuses on prototyping the minimal viable product. Finally, on Friday, they validate the prototype by observing users and gathering feedback to learn what works and what needs improvement.
Delivering Business Value - The Deal Breakers
This document discusses delivering business value through agile practices. It notes that being agile is about exhibiting agility through one's work rather than labeling oneself as agile. It also discusses deal breakers such as prioritizing story points over value delivered, focusing on customer needs over features, dysfunctional teams, lack of demos, and ignoring business factors like budgets, forecasts and economics. The document advocates an approach combining lean manufacturing principles with agile software development to scale delivery while also emphasizing strategy, collaboration, autonomy and learning.
Scrum - the basics
An introduction to the basic principles and practices of scrum. This presentation is designed to help convince your boss or colleagues that agile practices such as scrum have a solid set of theories behind them and a useful set of tools to implement them. There are also examples of success stories as well as how to learn more. The presentation is designed to be used by someone who already knows a bit about scrum, and wants to explain it to someone else. Some of the slides are cues for the speaker, so let me know if you find any of it confusing.
Agile retrospectives - why, what and how
This document discusses agile retrospectives, including why they are important, what they involve, and how to conduct them successfully. Retrospectives allow teams to continuously improve by reflecting on what went well and what could be improved in the last sprint or iteration. The key aspects covered are preparing an agenda and materials, gathering feedback from the team, analyzing the feedback to select a few key items to action, and planning follow-ups to ensure improvements are implemented. Conducting regular retrospectives helps teams enhance their processes and productivity over time.
Retrospective Meeting Knowledge Sharing
The document provides an overview of retrospective meetings, including their purpose, benefits, and tips for effective facilitation. Retrospectives allow teams to learn from past experiences and plan improvements for future iterations. They provide feedback on processes, surface issues, and record what is and isn't working to share knowledge across teams. The document outlines tips like focusing on actionable outcomes, prioritizing actions, analyzing recurring themes, and rotating leadership to keep retrospectives impactful.
Courage, Curiosity, and Connection
This document discusses practical tools for navigating a changing world with courage, curiosity and connection. It outlines common responses to distress like trying to control situations, getting stuck ruminating, and lack of emotional management. It then presents newer tools like mindfulness, awareness, reducing distractions, finding intrinsic rewards, giving time to connect with others, and using checklists to standardize best practices and reduce mistakes. The overall message is that developing skills like managing emotions, creating space for reflection instead of just reaction, and cooperating with others can help one adapt successfully to changes.
Product vision
A sharp product vision allows teams to focus their time on building the right product and meeting goals, while a fuzzy vision causes teams to spend more time trying to determine what to build. A clear vision leads to better products, stronger brand alignment, and meeting objectives, whereas an unclear vision results in more wasted effort and churn.
Guideline for retrospective & sprint planning
This document provides guidance on conducting retrospective and sprint planning meetings in Scrum. It discusses inspecting and adapting processes through retrospectives, which aim to continuously improve the team. Retrospectives use techniques like KPT (Keep, Problem, Try) to review previous work and plan improvements. Sprint planning determines what can be completed in the sprint by selecting product backlog items and estimating tasks. Teams define "Done" criteria and acceptance criteria to ensure clarity on completed work. The overall goal is to maximize transparency, collaboration and process improvement through regular inspection and adaptation.
Turn fear to passion
A guide on how to train staff to accept new technology and use them to your full advantage. The presentation is geared towards libraries.
Po session
This document provides an overview of Agile concepts and practices. It discusses key Agile principles like empirical process control, transparency, inspection, and adaptation. It also covers the pull principle of allowing teams to pull in work as needed. The document then describes specific Agile roles, ceremonies, and artifacts like the Scrum Master, Product Owner, sprint planning, daily standups, and product backlog. It provides guidance on splitting stories, ranking backlog items, and scaling the Product Owner role for larger products and multiple teams.
Advantages & Benefits of Kanban for Software Teams - Part 2 of "How to build ...
Part 2 of the "How to build the best Software Products" Series, brought to you by Blossom.co
Tips on how to and why you build the best products with Kanban, effectively.
Advantages & Benefits:
1. Continuous Delivery
2. No Estimations
3. Iterative Workflow
4. Continuous Improvement
5. Seamless Communication
6. Cycle Time
7. Reduction of Waste
8. Frequent Shipping, faster Feedback
9. No Planning Overhead, less Meetings
10. Reduced PM Overhead
11. Focus on Quality
12. Pull Principle
13. Never miss Blockers
14. Push Notifications with Integrations
15. One-click Analytics
Design sprint slideshare
A design sprint is simply a structured brainstorm based on design thinking, agile development and gamestorming.
Agile camp2016 agile101
The document provides an overview of Agile principles and the Scrum framework. It describes key Scrum roles like the Product Owner and Scrum Master. It also summarizes Scrum ceremonies such as Sprint Planning, Daily Standup, Sprint Review, and Retrospective. User stories and tracking work using a Kanban or Scrum board in TFS are also covered at a high level.
The Elephant In The Room: Motivation (2nd revision)
This is the second revision of one of my favorite talk about how to improve people's motivation during agile adaptation. I presented it in the April'13 event of Google Developers Group (GDG) Istanbul.
More Related Content
What's hot
Execute Your Strategy Before It Executes You
This document outlines a 4-step process for transforming strategic plans into strategic action: 1) initialize and start by balancing focus on a single idea with openness to possibilities, 2) explore and develop by balancing a single option with multiple options, 3) decide and act by balancing a single solution with multiple solutions, and 4) maintain and sustain by balancing a generic with customized approaches. It emphasizes balancing focus and possibilities at each step to maintain momentum from idea to execution.
The Slippery Slope
This document discusses how teams can unintentionally slip away from Agile practices over time if they are not careful. It provides examples of common "slippery slopes" such as skipping story estimation, not using relative sizing, carrying stories between sprints, and stopping daily standups. The author urges coaches to focus on helping teams form good habits in the first 3-6 months and celebrate successes while also constructively pointing out areas for improvement. Teams are reminded that Agile requires discipline and that changing habits is difficult, so they should avoid picking up bad practices.
10 Graphic design tools and graphic designer must haves
4- The Extraordinary Wacom BambooIf you are a designer, and you don't have one of these in your "des...
Facebook retrospective
This document describes a retrospective method called the "Facebook retrospective" designed by the author. It involves printing topics related to the Scrum process on cards and having team members vote on whether they "like" or "dislike" each topic. The results are analyzed to identify topics the team agrees or disagrees on, and actions are generated for topics of disagreement. The retrospective is timeboxed to one hour and includes an energizer, voting activity, discussion of results, and generating actions for the next sprint. Feedback from trying this method is to allow a neutral option for voting and to allow custom topic cards.
Design Sprint
Do you know what Design Sprint is? Are you able to easily explain it to your Boss? Don't worry; we've got you covered!
Jake Knapp explains Design Sprint as - "The 'greatest hits' of business strategy, innovation, behavioural science, and more — packaged into a step-by-step process that any team can use."
1. Map: Map out the problem and pick a critical area to focus
2. Sketch: Sketch out competing solutions on paper
3. Decide: Make decisions and turn your ideas into testable hypotheses
4. Prototype: Hack together a realistic prototype
5. Test: Get feedback from real-life users
These slides highlights the essential tasks to be done each day, eventually resulting in a five-day process for validating ideas and solving challenges.
Hands on with the Design Studio Method
In this hands-on, interactive session, Len will share some basic principles of the design studio method, share how you can use the design studio method to rapidly generate ideas for your own digital products, and then facilitate a mini design studio challenge that is sure to leave you with practical skills to apply to your work and bonded with meetup attendees.
Design Sprint - Day 1
This 3 Day Design Sprint was delivered to teenagers between the ages of 13 -18 to teach them how to quickly test ideas without writing a line of code. It has been adapted from Tom Lombardo's course from Fresh Tiled Soil.
Attaining Agile Fluency: Coaching Techniques - Focus on Goals Over Process
What is coaching?
“It is helping to identify the skills and capabilities that are within the person, and enabling them to use them to the best of their ability” — wikipedia
Individuals and Interactions over Process and Tools.
The above is one of the 4 values espoused in the manifesto but yet it is common to see many agile coaches engage with teams and organisations advocating more and more processes. This is a common sight with new teams and also with teams on the path of agile transition from few months to few years irrespective of the competency, skills and maturity of the teams. Agile Fluency model created by Diana Larse and James Shore highlights the focus on value over compliance and practices at any given level
“ Team fluency depends on more than just the capability of the individuals on the team. It also depends on management structures, relationships, organizational culture, and more. Don’t make the mistake of blaming individuals for low team fluency, or assuming that one highly-skilled individual will guarantee high team fluency ”
An agile coach responsible for building high performing teams will need right set of powerful tools and techniques to leverage while working with teams and also to set the right expectations to both management and teams. This talk will draw from experience using few such powerful tools mentioned below while coaching teams attain fluency.
1) Using Agile Fluency @ High Level to Set Expectations
2) Setting Team Norms & Working Agreements
3) Deliberate Practice
4) Creating Enablers for a Learning Organisation
5) Simple Measures
Design Sprint
The document discusses the design sprint process, which involves prototyping, validating, and learning over the course of a week to address an idea. On Monday, the team unpacks the problem by creating user stories and scoping it. On Tuesday, they sketch and take notes to generate ideas. Wednesday involves deciding on a path by critiquing ideas. On Thursday, the team focuses on prototyping the minimal viable product. Finally, on Friday, they validate the prototype by observing users and gathering feedback to learn what works and what needs improvement.
Delivering Business Value - The Deal Breakers
This document discusses delivering business value through agile practices. It notes that being agile is about exhibiting agility through one's work rather than labeling oneself as agile. It also discusses deal breakers such as prioritizing story points over value delivered, focusing on customer needs over features, dysfunctional teams, lack of demos, and ignoring business factors like budgets, forecasts and economics. The document advocates an approach combining lean manufacturing principles with agile software development to scale delivery while also emphasizing strategy, collaboration, autonomy and learning.
Scrum - the basics
An introduction to the basic principles and practices of scrum. This presentation is designed to help convince your boss or colleagues that agile practices such as scrum have a solid set of theories behind them and a useful set of tools to implement them. There are also examples of success stories as well as how to learn more. The presentation is designed to be used by someone who already knows a bit about scrum, and wants to explain it to someone else. Some of the slides are cues for the speaker, so let me know if you find any of it confusing.
Agile retrospectives - why, what and how
This document discusses agile retrospectives, including why they are important, what they involve, and how to conduct them successfully. Retrospectives allow teams to continuously improve by reflecting on what went well and what could be improved in the last sprint or iteration. The key aspects covered are preparing an agenda and materials, gathering feedback from the team, analyzing the feedback to select a few key items to action, and planning follow-ups to ensure improvements are implemented. Conducting regular retrospectives helps teams enhance their processes and productivity over time.
Retrospective Meeting Knowledge Sharing
The document provides an overview of retrospective meetings, including their purpose, benefits, and tips for effective facilitation. Retrospectives allow teams to learn from past experiences and plan improvements for future iterations. They provide feedback on processes, surface issues, and record what is and isn't working to share knowledge across teams. The document outlines tips like focusing on actionable outcomes, prioritizing actions, analyzing recurring themes, and rotating leadership to keep retrospectives impactful.
Courage, Curiosity, and Connection
This document discusses practical tools for navigating a changing world with courage, curiosity and connection. It outlines common responses to distress like trying to control situations, getting stuck ruminating, and lack of emotional management. It then presents newer tools like mindfulness, awareness, reducing distractions, finding intrinsic rewards, giving time to connect with others, and using checklists to standardize best practices and reduce mistakes. The overall message is that developing skills like managing emotions, creating space for reflection instead of just reaction, and cooperating with others can help one adapt successfully to changes.
Product vision
A sharp product vision allows teams to focus their time on building the right product and meeting goals, while a fuzzy vision causes teams to spend more time trying to determine what to build. A clear vision leads to better products, stronger brand alignment, and meeting objectives, whereas an unclear vision results in more wasted effort and churn.
Guideline for retrospective & sprint planning
This document provides guidance on conducting retrospective and sprint planning meetings in Scrum. It discusses inspecting and adapting processes through retrospectives, which aim to continuously improve the team. Retrospectives use techniques like KPT (Keep, Problem, Try) to review previous work and plan improvements. Sprint planning determines what can be completed in the sprint by selecting product backlog items and estimating tasks. Teams define "Done" criteria and acceptance criteria to ensure clarity on completed work. The overall goal is to maximize transparency, collaboration and process improvement through regular inspection and adaptation.
Turn fear to passion
A guide on how to train staff to accept new technology and use them to your full advantage. The presentation is geared towards libraries.
Po session
This document provides an overview of Agile concepts and practices. It discusses key Agile principles like empirical process control, transparency, inspection, and adaptation. It also covers the pull principle of allowing teams to pull in work as needed. The document then describes specific Agile roles, ceremonies, and artifacts like the Scrum Master, Product Owner, sprint planning, daily standups, and product backlog. It provides guidance on splitting stories, ranking backlog items, and scaling the Product Owner role for larger products and multiple teams.
Advantages & Benefits of Kanban for Software Teams - Part 2 of "How to build ...
Part 2 of the "How to build the best Software Products" Series, brought to you by Blossom.co
Tips on how to and why you build the best products with Kanban, effectively.
Advantages & Benefits:
1. Continuous Delivery
2. No Estimations
3. Iterative Workflow
4. Continuous Improvement
5. Seamless Communication
6. Cycle Time
7. Reduction of Waste
8. Frequent Shipping, faster Feedback
9. No Planning Overhead, less Meetings
10. Reduced PM Overhead
11. Focus on Quality
12. Pull Principle
13. Never miss Blockers
14. Push Notifications with Integrations
15. One-click Analytics
Design sprint slideshare
A design sprint is simply a structured brainstorm based on design thinking, agile development and gamestorming.
What's hot (20)
10 Graphic design tools and graphic designer must haves
10 Graphic design tools and graphic designer must haves
Attaining Agile Fluency: Coaching Techniques - Focus on Goals Over Process
Attaining Agile Fluency: Coaching Techniques - Focus on Goals Over Process
Advantages & Benefits of Kanban for Software Teams - Part 2 of "How to build ...
Advantages & Benefits of Kanban for Software Teams - Part 2 of "How to build ...
Similar to Agile EE 2010
Agile camp2016 agile101
The document provides an overview of Agile principles and the Scrum framework. It describes key Scrum roles like the Product Owner and Scrum Master. It also summarizes Scrum ceremonies such as Sprint Planning, Daily Standup, Sprint Review, and Retrospective. User stories and tracking work using a Kanban or Scrum board in TFS are also covered at a high level.
The Elephant In The Room: Motivation (2nd revision)
This is the second revision of one of my favorite talk about how to improve people's motivation during agile adaptation. I presented it in the April'13 event of Google Developers Group (GDG) Istanbul.
Game changers
This document outlines four levels of agile implementation: 1) Process, 2) Technical Practices, 3) Product Teams, and 4) Scale. It provides examples for each level, such as Kanban and Scrum for process and Lean Startup for product teams. Additional resources are recommended for further learning. The summary emphasizes that the four levels can reduce waste, empower teams, and create less work if implemented properly during growth and scaling.
T3CON 19 Scrum for web agencies, does it really work?
Scrum frameworks can work for web agencies but may need adaptation. Typical challenges for web agencies include small projects, budgets, teams, and stakeholders not being fully involved in Scrum. Scrum works best for long-term, complex products with dedicated teams and POs. Some adaptations include using smaller Scrum teams, hybrid Scrumban approaches, no estimates, integrating designers into teams, and focusing on deploying MVPS and learning from feedback. Open discussion of how others have implemented Scrum in web agencies is encouraged.
JDD2014: Game of Throneware, or how not to get killed when a developer become...
You are a good developer, each year you learn more, each year you earn more. You become senior, you become architect, chief architect, chief principal officer architect, and, one day, you are at the top-payroll level, and there is no place to go. You are happy with what you do, but your wife/husband/bank keeps asking for more. What do you do? You go to middle management.
What happens, when you become a manager? How do you organize teams, workspace? How do you help people? How do you deal with politics, communication? What has the position of your desk to do with the architecture of your systems? How do you make decisions?
Retrospective & review
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
Agile Retrospective & review
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
Redesigning everything (avanscoperta meeutp edition)
EventStorming was born as a massively in-person workshop to discover and model complex businesses and design event-driven software. But the old ways are no longer viable. After one year of experiments and discoveries in a forced-remote setting we know a lot more about what is still working and what is not.
Team up
Lately, it seems that process became trendier than core leadership skills. Agile, Scrum, Kanban stole the focus.
BUT - it is leadership that fuels process adoption rather than process auto-magically fixing disfunction teams.
In this talk we'll explore what went wrong in this process adoption race: from hiring or promoting the wrong people, avoid setting clear expectations from our leaders, to dropping lean practices due to lack of deep understanding (forgetting why we started to begin with).
The dark side is interesting to explore, but we are here for the bright light - we will bring the FOCUS back to how we want our leadership to look like.
We'll try to figure out how we want our leaders to look like in the "Agile era"
Agenda:
== THE WHY ==
- The essence
- Goals balance
- Surviving in chaos
- Team leader definition
- Business vision
- Throughput .vs. latency
- Confidence is not cheap
- Risks management
- Beautiful code
- Beautiful document
== THE HOW ==
- Visibility over progress
- Must, Delegate and External
- Ownership as a driver
- Define “minimum working unit” early
- Define “done” that works for you
- Quality is God (or at least Jesus)
- Test to last
- Bullets knowledge base
- Estimate together
- Teach to move forward
How to make your retrospectives the heart of your agile proces
The slides from my talk at WebExpo about how to make your retrospectives the heart of your agile proces
Making agile work for you - conduit 2017 -- John Garison
This document discusses how technical communicators can make agile development processes work for them. It provides tips for participating effectively in common agile meetings and activities like backlog grooming, sprint planning, daily scrums, demonstrations, and retrospectives. The document emphasizes speaking up in meetings, advocating for users, and adapting agile practices as needed. Technical communicators are encouraged to put effort into agile processes to get value from them and drive continuous improvement.
Scrum and-xp-from-the-trenches 04 sprint demo & retrospective
This document summarizes how a scrum team conducts various scrum activities including sprint demos, retrospectives, and slack time between sprints. It provides details on:
- Conducting sprint demos and insisting they include a demo at the end of each sprint for feedback.
- Organizing sprint retrospectives to identify what went well, opportunities for improvement, and action items for the next sprint.
- The importance of slack time between sprints for rest and learning, such as dedicating lab days for skills development.
UX Research - Discussion Guide basics
- A proper call plan structures research by providing focus to conversations through coherent organization of topics, questions, and objectives, rather than being a rigid script.
- Effective call planning requires generating initial questions, collaborating as a team to discuss assumptions and learning goals, drafting the plan with sections and timings, and practicing with a pilot call.
- With good planning through practicing and refining a call plan, researchers can feel prepared for conversations while allowing flexibility to explore new topics that emerge.
Redesigning everything ITARC Stockholm 2021
The document discusses lessons learned from transitioning collaborative modelling practices like EventStorming to remote formats. It describes how the author initially stopped all in-person workshops and trainings due to COVID-19. Through experimentation with online tools over 18 months, the author discovered both challenges and opportunities of the remote format. Some key lessons included the outsized impact of digital divides, the importance of asynchronous contributions alongside synchronous sessions, and the ability to leave modelling sessions permanently visible and accessible online. The author outlines various formats and how they may be used remotely or in hybrid formats going forward.
Leading Without Seeing: managing distributed teams
The rules are the same. Treat people well. Expect great things from them. Be human. The details though, they make all the difference. Managing the nuances of engagement and productivity with a couple thousand miles between you and your team is both science and art. My name is Shane. I have been running a fully distributed team of 20-40 North American creatives for the last 5 years. Our success has come from a cohesive set of technical and cultural systems: the right people, the right environment and the right tools.
* Build the right team: happy, helpful, curious & accountable
* The rhythm: offer consistency
* Relationships in the void
* Use the right tools
Scrum Master 101
This document provides an overview of the roles and responsibilities of a Scrum Master compared to a traditional Project Manager in a Waterfall methodology. It describes how a Scrum Master is primarily focused on facilitating Agile ceremonies like planning, daily standups, and retrospectives. Their key responsibilities include removing impediments for the team, coaching them in Agile practices, and helping to manage team dynamics. The document also provides examples of questions for clients and candidates to determine if a Scrum Master role and individual are a good fit.
Nasty Impediments: Unclog the Pipe for Business Agility
This presentation goes into details about impediments, how to identify them, how to create a strategy for, escalate, and ultimately - if not removing them entirely - moving the needle to improve the situation. Apologies for the outdated styling - it's on my backlog to improve it!
Masterclass IIMN - Agile (pensamiento y técnicas) - por José Carlos Gil Zambrana
Masterclass IIMN - Agile (pensamiento y técnicas) - por José Carlos Gil ZambranaIIMN. Instituto Internacional de Marketing
Masterclass de IIMN ofrecida en Marzo de 2015 "Agile (pensamiento y técnicas)" - por José Carlos Gil ZambranaHow to build a superstar self-organizing team?
This document discusses how to build a self-organizing team. It recommends giving the team the environment and support to get work done independently while still providing guidance. An exercise is described where participants self-organized into groups in different ways to understand the difference between command-and-control and self-organization. For effective self-organization, a team needs a shared goal, knowledge sharing, some delegated authority, team decision making, and proper metrics. Guidance is provided on establishing these elements step-by-step to transition a team to self-organization.
Agile in unfriendly territories
This session was given at the Agile Practitioners - IL 4th group meeting (November 2011).
In this talk i discussed how to apply Agile inside specific teams in a bigger waterfall organization, without the need to completely change it.
Similar to Agile EE 2010 (20)
The Elephant In The Room: Motivation (2nd revision)
The Elephant In The Room: Motivation (2nd revision)
T3CON 19 Scrum for web agencies, does it really work?
T3CON 19 Scrum for web agencies, does it really work?
JDD2014: Game of Throneware, or how not to get killed when a developer become...
JDD2014: Game of Throneware, or how not to get killed when a developer become...
Redesigning everything (avanscoperta meeutp edition)
Redesigning everything (avanscoperta meeutp edition)
How to make your retrospectives the heart of your agile proces
How to make your retrospectives the heart of your agile proces
Making agile work for you - conduit 2017 -- John Garison
Making agile work for you - conduit 2017 -- John Garison
Scrum and-xp-from-the-trenches 04 sprint demo & retrospective
Scrum and-xp-from-the-trenches 04 sprint demo & retrospective
Leading Without Seeing: managing distributed teams
Leading Without Seeing: managing distributed teams
Nasty Impediments: Unclog the Pipe for Business Agility
Nasty Impediments: Unclog the Pipe for Business Agility
Masterclass IIMN - Agile (pensamiento y técnicas) - por José Carlos Gil Zambrana
Masterclass IIMN - Agile (pensamiento y técnicas) - por José Carlos Gil Zambrana
More from alenalav
Quickpoint How To
Quickpoint allows users to open, view, edit, and present PowerPoint presentations on an iPad. It supports both 2003 and 2007 PowerPoint file formats. Presentations can be viewed in portrait or landscape mode and slides can be zoomed, panned, and navigated. Editing options include adding, deleting, and reordering slides. Images, shapes, and text boxes on slides can be manipulated and formatting options are available. Graphics, shapes, and text boxes can be inserted and slideshows can be presented on the iPad screen or an external display.
Getting Started
Quickoffice Connect Mobile Suite for iPad allows users to access, view, edit, and share files from cloud storage services and local files. It includes word processing, spreadsheet, and presentation applications that can open and edit Microsoft Office files. The suite also features integrated file management and storage across local, cloud, and remote locations.
??????? ????????
Quickpoint allows users to open, view, edit, and present PowerPoint presentations on an iPad. It supports both 2003 and 2007 PowerPoint file formats. Presentations can be viewed in portrait or landscape mode and slides can be zoomed, panned, and navigated. Editing options include adding, deleting, and reordering slides. Images, shapes, and text boxes on slides can be manipulated and formatting options are available. Graphics, shapes, and text boxes can be inserted and slideshows can be presented on the iPad screen or an external display.
Quickoffice
Eating disorders are defined as eating habits that are harmful to an individual's health and involve issues with food and weight. They affect about 5 million women and 1 million men and can impact anyone regardless of gender, class, race or age. The three most common eating disorders are anorexia nervosa, bulimia nervosa, and binge eating disorder, each with their own defining characteristics and warning signs. Left untreated, eating disorders can result in serious physical and emotional complications. Friends and family can help by educating themselves, expressing care and concern, and recommending counseling and support resources.
Forecast
This document contains a market forecast for different music instrument categories from 2008 to 2012. It shows the projected sales revenue for each category over those years as well as the total projected revenue. It also shows the projected percentage growth rates for each category from 2009 to 2012.
aaaaaaaaUntiytled
This document contains numbers that may be part of a code, reference, or data set. It includes 8 digits grouped into 4 sections separated by spaces. The meaning or significance of these numbers is not clear from the limited context provided.
edit delte me
A decade ago, people were skeptical about the idea that volunteers from around the world could work together to create an online encyclopedia like Wikipedia without ads or a commercial agenda. Now, almost 10 years later, Wikipedia has nearly 400 million monthly users and has proven that a collaborative, volunteer-driven model can create a large, freely accessible pool of knowledge for people.
delete me
Wikipedia started as a skeptical idea that volunteers could create an encyclopedia without ads or agendas but just for sharing knowledge, and after 10 years it has nearly 400 million monthly users, almost a third of internet users, showing it succeeded in creating a remarkable pool of human knowledge through collaboration.
Chicken Feed list
This document provides a list of ingredients for chicken feed including carbohydrates like corn and wheat, proteins like fish and peanuts, and vitamins/minerals. It also lists materials needed from the store such as boards, nails, wire mesh, a feeding tray, and a water tray to build an incubator.
Array formulas
The document shows a table with sales data for different car types (sedan and coupe) sold by various people. It includes the number of each type sold, the unit price, total sales for each type, and an array formula to calculate the total sales.
More from alenalav (13)
Agile EE 2010
- 1. Alena Lavrinenko & Tanya Mezentseva
- 8. Product burn down chart Purpose : Product progress visibility Advantages : Immediate reflection of the real deadline Disadvantages : Immediate reflection of the real deadline Audience : Everybody Who likes it the most : High Management
- 9. Task Board Purpose : Content visibility Advantages : Immediate understanding Disadvantages : Lack of overall visibility Audience : Everybody Who likes it the most : Scrum team Task Effort Owner
- 10. Example
- 13. Example
- 14. Example
- 15. Domain Chart
- 18. Summary
- 20. SOLUTION!
- 21. Scrum Games! Break from the usual routine Have some fun Learning in a snap! More EFFICIENT