The document discusses "dejirafication", or freeing product development processes from over-reliance on Jira and other backlog management tools. It argues that meetings often become focused on updating the tool rather than team collaboration. The author proposes a "jira rehab program" using paper artifacts instead of Jira, including mind maps for themes, just-in-time story slicing, mixed group backlog refinement, and lean coffee discussions with confidence voting. Following these steps is said to make meetings more lively and focused on shared understanding rather than tool updates.
From Scrum to Flow using Actionable Agile MetricsPeter Pito
‘When are we done?’ Can we predict when a project is done without estimating?
This talk covers the transformation journey of a project from an ‘estimation and planning’ based process to a ‘measurement and observation’ one.
By monitoring metrics such as work in progress, cycle time, throughput, ageing items and using Monte Carlo simulations for forecasting we can move towards answering the perennial question of ‘When are we done?’.
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
An Introduction to Agile; written by a developer for developers. Bringing together concepts of OODA, Agile, Lean, and Freelancing this into guild starts a conversation about practical agile in the enterprise.
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.
From the GitLab Data Team member, a first-face story about how the asynchronous way of working helps us manage the “chaos” (as folks usually think about remote work) in the 24/7 work environment. In this session, I like to demystify transparency and how it can leverage your success. The narrative is related to the Data team in GitLab and can be used for any matter. Will wrap the topics and guide you through: - Why transparency is an organic way to communicate and cooperate, - How to stay secure when you share everything or almost everything with the outer world, - How to leverage your data usage and still stay a good boy of the IT world, - What you should promise to your community
How to Ship in 8 Weeks or Less (via Cross-Functional Teams)QuekelsBaro
Get you clued up on what the development methodology Shape Up looks like in practice and sneak-peak into what we do at Process Street as our EPD team shares their secrets.
Making the Transition to Agile: what we did, what worked, and what we learnedAri Davidow
In 2008 the Jewish Women's Archive (JWA) tried Agile Software development as a tool to select the necessary User Stories and develop a working, lightweight interface to the Fedora Commons digital archive. The project succeeded. That software was later taken by the developer and open sourced as the "hydra" project.
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.
Industry stories on agile, scrum and kanbanBusiness901
Eric is an Agile Project Manager who has been using Kanban for software development since 2007. He has worked with Scrum, XP and other agile methods for over the past 5 years, and has been managing software projects for over 10 years. Eric has his own blog, Corporate Coder which can be found at http://EricLandes.com. He is also a frequent contributor to http://developer.com.
From Scrum to Flow using Actionable Agile MetricsPeter Pito
‘When are we done?’ Can we predict when a project is done without estimating?
This talk covers the transformation journey of a project from an ‘estimation and planning’ based process to a ‘measurement and observation’ one.
By monitoring metrics such as work in progress, cycle time, throughput, ageing items and using Monte Carlo simulations for forecasting we can move towards answering the perennial question of ‘When are we done?’.
In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
An Introduction to Agile; written by a developer for developers. Bringing together concepts of OODA, Agile, Lean, and Freelancing this into guild starts a conversation about practical agile in the enterprise.
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.
From the GitLab Data Team member, a first-face story about how the asynchronous way of working helps us manage the “chaos” (as folks usually think about remote work) in the 24/7 work environment. In this session, I like to demystify transparency and how it can leverage your success. The narrative is related to the Data team in GitLab and can be used for any matter. Will wrap the topics and guide you through: - Why transparency is an organic way to communicate and cooperate, - How to stay secure when you share everything or almost everything with the outer world, - How to leverage your data usage and still stay a good boy of the IT world, - What you should promise to your community
How to Ship in 8 Weeks or Less (via Cross-Functional Teams)QuekelsBaro
Get you clued up on what the development methodology Shape Up looks like in practice and sneak-peak into what we do at Process Street as our EPD team shares their secrets.
Making the Transition to Agile: what we did, what worked, and what we learnedAri Davidow
In 2008 the Jewish Women's Archive (JWA) tried Agile Software development as a tool to select the necessary User Stories and develop a working, lightweight interface to the Fedora Commons digital archive. The project succeeded. That software was later taken by the developer and open sourced as the "hydra" project.
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.
Industry stories on agile, scrum and kanbanBusiness901
Eric is an Agile Project Manager who has been using Kanban for software development since 2007. He has worked with Scrum, XP and other agile methods for over the past 5 years, and has been managing software projects for over 10 years. Eric has his own blog, Corporate Coder which can be found at http://EricLandes.com. He is also a frequent contributor to http://developer.com.
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
Org Topologies at Scrum Day Europe 2022, AmsterdamAlexey Krivitsky
Organizational Topologies: your roadmap towards an innovative, resilient and adaptive product development organization.
Many organizations struggle to adopt "agile" in a way that delivers on its promise to make the company fast, flexible and efficient.
Global consultancy firms have great pitches on how to adopt different so-called “Agile frameworks”. The marketing is great, but are the results too? We see how our clients get stuck in adopting a framework - forming “agile teams”, appointing “product owners” and then clustering all this into “tribes”. Thus creating robust structures that make further organizational improvements and adaptability difficult, slow, and expensive.
This talk offers ideas how to go beyond these limiting ideas and explores a map of organizational transformation based on orgtopologies.com.
Organizational Topologies: a roadmap towards a resilient and adaptive product...Alexey Krivitsky
Many organizations struggle to adopt "agile" in a way that delivers on its promise to make the company fast, flexible and efficient. Global consultancy firms have great pitches on how to adopt different so-called “Agile frameworks”. The marketing is great, but are the results too? We see how our clients get stuck in adopting a framework - forming “agile teams”, appointing “product owners” and then clustering all this into “tribes”. Thus creating robust structures that make further organizational improvements and adaptability difficult, slow, and expensive.
For more details visit www.orgtopologies.com
How to grow learning multi-site agile organizationsAlexey Krivitsky
What is making organizations so complex and slow? Why an "enterprise" is an equivalent to "inefficient"? How to de-scale organizations? There is no easy answers. But understanding the internal system dynamics is the key skill here.
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
Oprah Winfrey: A Leader in Media, Philanthropy, and Empowerment | CIO Women M...CIOWomenMagazine
This person is none other than Oprah Winfrey, a highly influential figure whose impact extends beyond television. This article will delve into the remarkable life and lasting legacy of Oprah. Her story serves as a reminder of the importance of perseverance, compassion, and firm determination.
9. Jirandicitis (or the ‘jira symptom’)
An observable process
when team collaboration
(such as a meeting)
is degrading to become
a plain tool-updating activity
(with a sole goal of updating the tool).
23. Get clean today.
#1 mind-mapping for product themes – no more lists
#2 JIT story slicing – minimal inventories
#3 backlog refinement with mixed teams – amplify learning
#4 shape discussions – lean coffee with confidence voting
Sign up for jira rehab program now!