Learn more about the most popular Agile framework - Scrum. This training should be paired with the pre-training learning materials in Trello. Learn more about the Scrum artifacts (product backlog, sprint backlog, etc.), Scrum roles (Scrum Master, Product Owner, and the team), and the Sprint.
The training offers an overview of Agile development and Scrum practices, focusing on how the Scrum framework follows the Agile Manifesto principles. ... The Scrum framework uses simple iterative practices for team collaboration on complex projects.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
Why Scrum? Scrum is conceptually a very, very simple process framework. What is it about Scrum that is generating some much buzz in the software development community? Why are companies, both big and small, abandoning traditional approaches such as Water Fall and RUP, in favour of Scrum?
Learn more about the most popular Agile framework - Scrum. This training should be paired with the pre-training learning materials in Trello. Learn more about the Scrum artifacts (product backlog, sprint backlog, etc.), Scrum roles (Scrum Master, Product Owner, and the team), and the Sprint.
The training offers an overview of Agile development and Scrum practices, focusing on how the Scrum framework follows the Agile Manifesto principles. ... The Scrum framework uses simple iterative practices for team collaboration on complex projects.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
Why Scrum? Scrum is conceptually a very, very simple process framework. What is it about Scrum that is generating some much buzz in the software development community? Why are companies, both big and small, abandoning traditional approaches such as Water Fall and RUP, in favour of Scrum?
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
Data Con LA 2020
Description
The Agile Scrum Overview training will provide you with the essentials to effectively practice scrum as a scrum team member. You'll gain knowledge on the agile manifesto's values and principles, scrum framework, ceremonies, and tools used with practicing scrum. You'll be inspired and on boarded as an agile scrum practitioner!
*Agile history, background and the agile manifesto's values and principles.
*Agile Scrum framework for software development
* Scrum roles: Product Owner, Scrum Team, Scrum Master
*Sprint Ceremonies: Sprint Planning, Daily Stand-up, Sprint Review (Demo), Sprint Retrospective
*High performing teams, velocity charts, burndown charts
Speaker
Sonia Macias, Consultant, Scrum Master / Project Manager
Introduction to Agile Project Management and ScrumVoximate
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they're doing today, and any blocking issues they're encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
I decided to help all the freshmen and share the basic Kanban principles with them.
Good luck!
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
Data Con LA 2020
Description
The Agile Scrum Overview training will provide you with the essentials to effectively practice scrum as a scrum team member. You'll gain knowledge on the agile manifesto's values and principles, scrum framework, ceremonies, and tools used with practicing scrum. You'll be inspired and on boarded as an agile scrum practitioner!
*Agile history, background and the agile manifesto's values and principles.
*Agile Scrum framework for software development
* Scrum roles: Product Owner, Scrum Team, Scrum Master
*Sprint Ceremonies: Sprint Planning, Daily Stand-up, Sprint Review (Demo), Sprint Retrospective
*High performing teams, velocity charts, burndown charts
Speaker
Sonia Macias, Consultant, Scrum Master / Project Manager
Introduction to Agile Project Management and ScrumVoximate
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they're doing today, and any blocking issues they're encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
I decided to help all the freshmen and share the basic Kanban principles with them.
Good luck!
Kanban is an Lean practice that focuses on completing work. Used alone Kanban provides an evolutionary approach to agile development and better fits many SW development teams (like maintenance or sysadmin) that don't have an iterative cadence. Used in combination with agile processes like Scrum or Extreme Programming, Kanban practices like WIP limits and Service Level swim lanes solve issues real teams and companies encounter every day. Project managers should pay special attention to Kanban Lead Time metric.
WebCamp: Project Management Day: World of Agile: Kanban - Евгений АндрушкоGeeksLab Odessa
World of Agile: Kanban
Евгений Андрушко
Project Manager at Softserve
- Что общего между садом сакуры и тойота?
- Какую методологию выбрать на Вашем проекте?
- Реальная практика примения Kanban SDLC.
- Kanban kick-start.
- Kanban vs Iterative agile.
- Софт для Agile: Lean Kanban vs Jira vs Trello.
We prize our ability to multitask yet we rarely acknowledge the impact this has on our ability to get work done. Teams look to process to create efficiencies but ignore one simple tool that has the ability to transform the amount, the speed, and the quality of their work: Limiting Work In Progress. In this talk I will share my stories and experiences of the power that limiting WIP has to bring a team focus, flexibility and follow through.
While most Kanban games usually focus only on the flow of an existing Kanban system demonstrating the path from an existing process to Kanban, this game allows you to learn more about the Kanban philosophy and how to work with it. Learning by doing and having fun at the same time.
In the 1940s, Toyota developed a scheduling system to improve their manufacturing production. Aligning the supply of materials with the demand of the production line reduced the amount of inventory in the system, and enabled a flexibility never before seen in the automobile industry.
Over the years, teams dealing with knowledge work (e.g. software development) adapted many of these ‘lean’ ideas, such as limiting the amount of work in progress, to improve the flow of work through their system.
Ideal for product owners, business analysts, developers, testers, and any users of Agile/Scrum, this presentation explains the basics of this system, called Kanban, and how it can be used to improve workflow and delivery rate.
Sam McAfee talks about how they have applied Kanban and lean methodologies at RadicalFusion during the San Francisco Agile User Group meeting at Atlassian.
http://youtu.be/RkV1WgeQX8A
Welcome to the Program Your Destiny course. In this course, we will be learning the technology of personal transformation, neuroassociative conditioning (NAC) as pioneered by Tony Robbins. NAC is used to deprogram negative neuroassociations that are causing approach avoidance and instead reprogram yourself with positive neuroassociations that lead to being approach automatic. In doing so, you change your destiny, moving towards unlocking the hypersocial self within, the true self free from fear and operating from a place of personal power and love.
7. To DO Doing (2) Done
The Board:
Each column represents
one phase of your
process.
The Card:
Each card represents a
task or project.
The WIP:
Numbers on top
represent WIP limits.
8. Developed
process to track
objects through a
production stream
Taiichi Ohno,
Father of Lean
Manufacturing
Focus on
transparency
Designed to
empower line
workers to be
able to improve
processes
Based on pull
system where
work is
controlled by
demand
Use of visual
signals is the
foundation of
the system
13. To DO Doing Done
A big board
+
cards
+
columns
Kanban Rule #1: Visualize
14. Kanban Rule #1: Visualize
While you are traveling down
this road, there is a chance
that one or more rocks of
varying size may fall from
the slopes on one or both
sides of you. You should be
aware of this before you
travel this way so that you
are cautious of this particular
type of hazard.
Research shows that the brain can process visual
information over 50,000 times faster than text.
Why did you choose this session today? Is it because....
You’re juggling multiple priorities?
Have too much work to do?
Can’t get it all done?
What’s your favorite excuse for this?
Time with family or friends
Not enough hours in the day
Nobody can do it but you
Unrealistic goals
But what’s the real reason or reasons?
Won’t say no
Can’t focus
Too much multi-tasking
Forget about due dates, out of sight
Hard to prioritize, 5 #1s
People, tasks, responsibilities, deadlines in and outside of work are constantly competing for your attention.
Juggling too many things at once is bad for our brains which can cause:
Problems on the team: burnout, productivity issues, bottlenecks
Problems personally: health, relationships, spirituality
But yet we keep doing it day in and day out....
... This is insanity!
Let’s do something about it.
Big board with cards
Board represents the state of a project at any point in time
The number of tasks in each phase is limited by the WIP limits specified
Taiichi Ohno Developed Lean
Taiichi introduced concepts that include tracking objects of value through a production stream:
Designed after grocery store stocking of shelves. The inspiration for the Kanban system were retail stores or, more exactly, store clerks in supermarkets who restocked the items to the shelves every time that the item was being sold to the customer. The inventory was not restocked directly by their vendor’s on their own estimates, but when an item was nearly sold out, the clerks were allowed to order new supplies. The restocking of the inventory was therefore completely demand driven. That much about the inspiration for the Kanban system.
Needed a way to communicate how much work is currently being done, what stages the work was in, and how it was being done
Wanted transparency so any worker would know the answers to these questions
Kanban in Japanese is a common term for “signboard” or “billboard”
David J. Anderson introduced Kanban for Software Development for JIT delivery
Manufacturing in 1940s at Toyota
Over time, your understanding of your work will evolve
Big board with cards
Board represents the state of a project at any point in time
Less complex, you don’t have to think
Our worklows are inherently invisible
Kanban enables you to take a quick look and see the status of the project
Cards move along the board to show workflow
Projects take longer when people are not working 100% of the time, so we fill our or our team’s time to the max. But tasks’ speed, efficiency, and output quality decrease when we’re at 100%.
Work is only pulled into the next phase when there is capacity or availability
Improves quality by giving greater focus to fewer tasks
Maximum utilization is not efficient and is contrary to popular belief
Get the most important things done one by one,
focus on what’s “Done” rather than what was worked on or is in WIP
A highway can hold 0 – 100% capacity. But when a highway extends beyond 65% capacity, it slows down. When it reaches 100% capacity, it stops.
Multitasking is a poor way to manage your work. If your brain is a highway and you fill it with work, after a while you start to slow down.
Benefits of a white board – easy to change process around
Different colored post-its can be used for different types
(the last 20% takes 80% of our time)
Put WIP limits in the swimlanes to limit the amount of work for a kind of work type
Put WIP limits in the WIP to limit work in a particular phase