The CTO of Wolters Kluwer Italia asked if they could improve their time-to-market. The response was yes, if they followed an evolutionary approach. Initially a Kanban board was set up for a pilot team to manage business ideas, projects, and urgerncies. This was later expanded to a larger pilot project using Scrum. With 200 initiatives and 400 people involved, they created a "Sala Caravaggio" room to visualize projects using Kanban boards. They began measuring initiatives from pre-funnel through implementation to monitor the effects of the transition. Goals were reached, including regular board meetings, improved project control, training over 125 people, and continuous business-ICT alignment on
Behind every great product is a great team doing work in a way that guarantees results. They are following a roadmap from the starting point to the end product. But a product roadmap can be elusive. This talk addresses why it is important and presents an approach to make one.
The product roadmap is a plan of action that outlines of tactical steps to execute the product strategy pushing the product ahead in the trajectory of planned direction in alignment with the product vision while accomplishing short-term and long-term product objectives
Discovery Phase [What is it and why is it important?]Stfalcon
Nowadays it’s unreasonable to start a software development project without a preliminary comprehensive analysis. Discovery phase should become an initial stage of any project you
deal with. It’s an information-gathering procedure, which brings you in-depth comprehension of the industry, the client’s business, and target audience.
Portfolio for JIRA & Kanban: How Thrillist Manages Their Product RoadmapAtlassian
We at Thrillist need to move fast to stay competitive. That's why we use Kanban. We also need to keep a grip on the big picture, and that's why we use Portfolio for JIRA. Can Kanban work together with high-level planning? Yes, it can.
Dive into the Thrillist process of planning and executing our product roadmap with Portfolio. Learn how the combination of Kanban methodologies with Portfolio can enable a team to become fast, flexible, and forward-thinking.
For more on Thrillist and their Atlassian setup, check out Mike's website: http://mike-solomon.com/abstract/
Products covered:
Portfolio for JIRA
(Last change, July 2: Removed as beyond most teams' scope Eyetracking Study, Clickstream Analysis, Usability Benchmarking; Added Live-Data Prototypes, Demand Validation Test, Wizard of Oz Tests)
For our teams tasked with building products and features for The New York Times, we face a common challenge with many: how do we figure out what’s worth spending our time on?
The answer seems straightforward: test your ideas with real customers, leveraging the expertise of your product, UX, and engineering talent. Figure out the smallest test that you can come up with to test a specific hypothesis, gather data and insights, and keep iterating on it until you know whether the problem is real and your solution will prove valuable, usable, and feasible.
As part of our efforts to adopt such a data-driven, experimental approach to product development, we recently kicked off a product discovery pilot program. Small, cross-functional teams were paired with coaches and facilitators over a six week period to demonstrate how product discovery and Lean Startup techniques could work for real-world customer opportunities at The New York Times.
One of the first things that we learned about the process from our participants was that they wanted a "toolkit" - something to help them figure out what they should be doing, asking or making to get as quickly as possible towards the validated learning, prototypes and user tests that would have the most impact.
To help the facilitate the learning process for our dual-track Agile teams, the Product Architecture team here at The Times (Christine Yom, Jim Lamiell, Josh Turk, Priya Ollapally, and Al Ming) built a "Product Discovery Activity Guide" that rolled up activities, exercises, and testing techniques from all our favorite thought leaders.
This included brainstorming exercises from Gamestorming and Innovation Games, testing techniques from traditional user research, and rapid test-and-learn tactics from Google Ventures, Eric Ries (The Lean Startup), Jeff Gothelf (Lean UX), Steve Blank (Customer Development) and our spirit guide, Marty Cagan (Inspired), among others.
Our goal was to make it a tool not just for learning how to get started, but to be a living document for teams to share knowledge about the process itself. What techniques worked and didn't work? What tactics did they learn elsewhere that might be worth sharing with the rest of the company?
We hope you find it useful, and whether you’d like to share with us what you’re doing with it, or you have suggestions (big or small) to improve it for future product generations, please let us know! (nyt.tech.productarchitecture@nytimes.com)
Al Ming
July 2015
What are the Agile Metrics That Matter Most? Are they at the team-level? project/project? What about the people-side of agile (the "soft stuff"). What are common pitfalls to avoid? We categorize agile metrics into those about Value, Flow, Quality & Culture, and identify the most frequently used (and misused) in each of those areas.
Creation and refinement of the product backlog can be achived in different ways.
Roman Pichler, in is post originally written in Jul, 16 2012 - http://www.romanpichler.com/blog/agile-product-innovation/the-product-canvas , has proposed a really interesting approach: use canvas to create and share product vision and product backlog creation and refinement.
I used this approach for a while with cool results.
These slides are a step-by-step introduction of the tool.
Please send me feedbacks to correct and improve it!
You can use these slides under Creative Commons Attribution-ShareAlike 3.0 Unported License.
In this presentation, you will know about the role and responsibilities of an Agile Business Analyst? What is the context and need for an Agile business Analyst
Behind every great product is a great team doing work in a way that guarantees results. They are following a roadmap from the starting point to the end product. But a product roadmap can be elusive. This talk addresses why it is important and presents an approach to make one.
The product roadmap is a plan of action that outlines of tactical steps to execute the product strategy pushing the product ahead in the trajectory of planned direction in alignment with the product vision while accomplishing short-term and long-term product objectives
Discovery Phase [What is it and why is it important?]Stfalcon
Nowadays it’s unreasonable to start a software development project without a preliminary comprehensive analysis. Discovery phase should become an initial stage of any project you
deal with. It’s an information-gathering procedure, which brings you in-depth comprehension of the industry, the client’s business, and target audience.
Portfolio for JIRA & Kanban: How Thrillist Manages Their Product RoadmapAtlassian
We at Thrillist need to move fast to stay competitive. That's why we use Kanban. We also need to keep a grip on the big picture, and that's why we use Portfolio for JIRA. Can Kanban work together with high-level planning? Yes, it can.
Dive into the Thrillist process of planning and executing our product roadmap with Portfolio. Learn how the combination of Kanban methodologies with Portfolio can enable a team to become fast, flexible, and forward-thinking.
For more on Thrillist and their Atlassian setup, check out Mike's website: http://mike-solomon.com/abstract/
Products covered:
Portfolio for JIRA
(Last change, July 2: Removed as beyond most teams' scope Eyetracking Study, Clickstream Analysis, Usability Benchmarking; Added Live-Data Prototypes, Demand Validation Test, Wizard of Oz Tests)
For our teams tasked with building products and features for The New York Times, we face a common challenge with many: how do we figure out what’s worth spending our time on?
The answer seems straightforward: test your ideas with real customers, leveraging the expertise of your product, UX, and engineering talent. Figure out the smallest test that you can come up with to test a specific hypothesis, gather data and insights, and keep iterating on it until you know whether the problem is real and your solution will prove valuable, usable, and feasible.
As part of our efforts to adopt such a data-driven, experimental approach to product development, we recently kicked off a product discovery pilot program. Small, cross-functional teams were paired with coaches and facilitators over a six week period to demonstrate how product discovery and Lean Startup techniques could work for real-world customer opportunities at The New York Times.
One of the first things that we learned about the process from our participants was that they wanted a "toolkit" - something to help them figure out what they should be doing, asking or making to get as quickly as possible towards the validated learning, prototypes and user tests that would have the most impact.
To help the facilitate the learning process for our dual-track Agile teams, the Product Architecture team here at The Times (Christine Yom, Jim Lamiell, Josh Turk, Priya Ollapally, and Al Ming) built a "Product Discovery Activity Guide" that rolled up activities, exercises, and testing techniques from all our favorite thought leaders.
This included brainstorming exercises from Gamestorming and Innovation Games, testing techniques from traditional user research, and rapid test-and-learn tactics from Google Ventures, Eric Ries (The Lean Startup), Jeff Gothelf (Lean UX), Steve Blank (Customer Development) and our spirit guide, Marty Cagan (Inspired), among others.
Our goal was to make it a tool not just for learning how to get started, but to be a living document for teams to share knowledge about the process itself. What techniques worked and didn't work? What tactics did they learn elsewhere that might be worth sharing with the rest of the company?
We hope you find it useful, and whether you’d like to share with us what you’re doing with it, or you have suggestions (big or small) to improve it for future product generations, please let us know! (nyt.tech.productarchitecture@nytimes.com)
Al Ming
July 2015
What are the Agile Metrics That Matter Most? Are they at the team-level? project/project? What about the people-side of agile (the "soft stuff"). What are common pitfalls to avoid? We categorize agile metrics into those about Value, Flow, Quality & Culture, and identify the most frequently used (and misused) in each of those areas.
Creation and refinement of the product backlog can be achived in different ways.
Roman Pichler, in is post originally written in Jul, 16 2012 - http://www.romanpichler.com/blog/agile-product-innovation/the-product-canvas , has proposed a really interesting approach: use canvas to create and share product vision and product backlog creation and refinement.
I used this approach for a while with cool results.
These slides are a step-by-step introduction of the tool.
Please send me feedbacks to correct and improve it!
You can use these slides under Creative Commons Attribution-ShareAlike 3.0 Unported License.
In this presentation, you will know about the role and responsibilities of an Agile Business Analyst? What is the context and need for an Agile business Analyst
Product roadmaps are an important product management tool. But traditionally, they map features onto a timeline that often extends many months into the future. This makes them hard to apply in an agile context where change and uncertainty are present. My talk shows how you can use agile product roadmaps, roadmaps that describe the value the product should create, align the stakeholders and development teams, and unburden the product backlog while avoiding premature commitments and preserving the ability to inspect and adapt.
The slides are for a course that is LIVE on Udemy.com (https://www.udemy.com/product-roadmap-101/)
The slides outline how to build an effective product by translating product strategy into product roadmap for enterprise products.
Nguyen Vu Hung - Software Project Management with Jira AgileVu Hung Nguyen
Biography:
Nguyen Vu Hung is the CLO of Septeni Technology, a development center of Tokyo based Septeni Group that focuses on developing and operating, mostly, web-based online advertisement systems. He has numerous years of IT and software development, project/product management in both Japan and Vietnam. Considering himself as a FOSS and Agile evangelist and being a Agile lover and an CLO, he is also interested in not-so-related domains such as human resource management and (organization) (re)structuring. Hung is interested in: – Agile/Scrum and the alikes – Open Source – Project Management
Software project management with Jira Agile:
In this workshop, I will share hand-on experience on how using Jira Agile to manage project in Agile/Scrum ways. The workshop will guide you:
– How to create and manage your product backlog, sprints backlog using Confluence
– How to manage sprint backlog using Confluence, link it with JIRA
– How to manage daily tasks and stories in JIRA
– Using Scrum board, Epic
– Make Sprint report, Velocity chart
– Using Planning and Estimating
Goal of this session:
Master Scrum Artifacts using JIRA
References:
http://agiletourvietnam.org/speakers/
http://agiletourvietnam.org/speaker/nguyen-vu-hung/
http://agiletourvietnam.org/session/software-project-management-with-jira-agile/
This presentation discusses how you can leverage the innovation strategy and the product lifecycle to get your product strategy right and achieve product success; how to make your product stand out from the crowd; and how you can effectively capture your product strategy.
This is one hour free webinar about Agile principles for software development.
Main purpose for this webinar is to give attendees overview of Agile methodology for software development and provide understanding of main Agile principles.
Presenter:
Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence
Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale.
Topics will include:
• Basic agile and lean methods
• Scrum of Scrums
• SAFe
• Disciplined Agile Delivery (DAD)
• Agility at Scale (Ambler/Lines)
• Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).
Product Roadmaps - Tips on how to create and manage roadmapsMarc Abraham
This presentation is focused on two areas with respect to product roadmaps. Firstly, a roadmap is a not a loose collection of timings and features. Secondly, it is key to define a product vision, goals and strategy before creating a roadmap.
As product managers and product owners, we make a myriad of decisions—from shaping the product strategy to deciding the detailed functionality of our products. But do we make all these decisions effectively? And do we always secure the necessary buy-in? This slide deck wants to helps you make better decisions. It discusses five common decision rules and explains when to apply them.
Tips for Effectively Applying the Product Owner RoleRoman Pichler
This slide deck offers tips to successfully apply the product owner role. It distinguishes different product owner flavours, explains hope the Scrum product owner role differs from the SAFe one, and how product ownership can be scaled.
Portfolio Kanban - Seeing the Big Picture Sandy Mamoli
Doing too many things at once can slow an entire organisation down. As every successful organisation will have more great ideas than they have capacity to build, it is tempting to start too many of them at the same time. However, too many projects in progress will slow down delivery of each and every one of them.
So, how can we make sure we work to our organisational capacity and don’t try to do too much? How do we make sure we’re working on the important and not just the urgent stuff? This is where Portfolio Kanban can help: In this session we will explore how Portfolio Kanban can help an organisation prioritise, plan and visually track its projects.
Through the example of Trade Me, New Zealand's biggest e-commerce site, I will demonstrate the practical application of Portfolio Kanban. I will explore how Trade Me have benefitted from the increased visibility and reduced work in progress, and how they are using Portfolio Kanban to direct the organisation’s Agile teams. Come along and enjoy tales of our successes, challenges and struggles on our (still continuing) journey towards awesome portfolio management.
Very frequently, when we discuss a change initiative failure, we point as one of key reasons of the failure lack of support from top management. Much effort on team level is wasted because the organization on high level is set up to preserve status quo.
For a change agent looking to set an organization on a path on continuous, evolutionary change addressing the issue of stale mindset of the leaders of the company is frequently the key obstacle to overcome. Usually, a different set of tools is required to achieve that, especially for internal change agents who have hierarchy working against them.
I will show how we can use Portfolio Kanban as a low-friction method, which might be used by change agents, to steer mindset change among top managers. Similarly to team-level Kanban a few simple rules help to change how we look at project or product portfolio and how the work flows on high level.
Thinking about Kanban on portfolio level introduces the whole new set of challenges that can’t be solved with standard approach, so it is also a story about Kanban versatility and adaptability.
After all, if end results include better understanding of how the work is done, improved effectiveness and healthier work environment for teams it is worth giving a try, isn’t it?
Product roadmaps are an important product management tool. But traditionally, they map features onto a timeline that often extends many months into the future. This makes them hard to apply in an agile context where change and uncertainty are present. My talk shows how you can use agile product roadmaps, roadmaps that describe the value the product should create, align the stakeholders and development teams, and unburden the product backlog while avoiding premature commitments and preserving the ability to inspect and adapt.
The slides are for a course that is LIVE on Udemy.com (https://www.udemy.com/product-roadmap-101/)
The slides outline how to build an effective product by translating product strategy into product roadmap for enterprise products.
Nguyen Vu Hung - Software Project Management with Jira AgileVu Hung Nguyen
Biography:
Nguyen Vu Hung is the CLO of Septeni Technology, a development center of Tokyo based Septeni Group that focuses on developing and operating, mostly, web-based online advertisement systems. He has numerous years of IT and software development, project/product management in both Japan and Vietnam. Considering himself as a FOSS and Agile evangelist and being a Agile lover and an CLO, he is also interested in not-so-related domains such as human resource management and (organization) (re)structuring. Hung is interested in: – Agile/Scrum and the alikes – Open Source – Project Management
Software project management with Jira Agile:
In this workshop, I will share hand-on experience on how using Jira Agile to manage project in Agile/Scrum ways. The workshop will guide you:
– How to create and manage your product backlog, sprints backlog using Confluence
– How to manage sprint backlog using Confluence, link it with JIRA
– How to manage daily tasks and stories in JIRA
– Using Scrum board, Epic
– Make Sprint report, Velocity chart
– Using Planning and Estimating
Goal of this session:
Master Scrum Artifacts using JIRA
References:
http://agiletourvietnam.org/speakers/
http://agiletourvietnam.org/speaker/nguyen-vu-hung/
http://agiletourvietnam.org/session/software-project-management-with-jira-agile/
This presentation discusses how you can leverage the innovation strategy and the product lifecycle to get your product strategy right and achieve product success; how to make your product stand out from the crowd; and how you can effectively capture your product strategy.
This is one hour free webinar about Agile principles for software development.
Main purpose for this webinar is to give attendees overview of Agile methodology for software development and provide understanding of main Agile principles.
Presenter:
Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence
Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale.
Topics will include:
• Basic agile and lean methods
• Scrum of Scrums
• SAFe
• Disciplined Agile Delivery (DAD)
• Agility at Scale (Ambler/Lines)
• Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).
Product Roadmaps - Tips on how to create and manage roadmapsMarc Abraham
This presentation is focused on two areas with respect to product roadmaps. Firstly, a roadmap is a not a loose collection of timings and features. Secondly, it is key to define a product vision, goals and strategy before creating a roadmap.
As product managers and product owners, we make a myriad of decisions—from shaping the product strategy to deciding the detailed functionality of our products. But do we make all these decisions effectively? And do we always secure the necessary buy-in? This slide deck wants to helps you make better decisions. It discusses five common decision rules and explains when to apply them.
Tips for Effectively Applying the Product Owner RoleRoman Pichler
This slide deck offers tips to successfully apply the product owner role. It distinguishes different product owner flavours, explains hope the Scrum product owner role differs from the SAFe one, and how product ownership can be scaled.
Portfolio Kanban - Seeing the Big Picture Sandy Mamoli
Doing too many things at once can slow an entire organisation down. As every successful organisation will have more great ideas than they have capacity to build, it is tempting to start too many of them at the same time. However, too many projects in progress will slow down delivery of each and every one of them.
So, how can we make sure we work to our organisational capacity and don’t try to do too much? How do we make sure we’re working on the important and not just the urgent stuff? This is where Portfolio Kanban can help: In this session we will explore how Portfolio Kanban can help an organisation prioritise, plan and visually track its projects.
Through the example of Trade Me, New Zealand's biggest e-commerce site, I will demonstrate the practical application of Portfolio Kanban. I will explore how Trade Me have benefitted from the increased visibility and reduced work in progress, and how they are using Portfolio Kanban to direct the organisation’s Agile teams. Come along and enjoy tales of our successes, challenges and struggles on our (still continuing) journey towards awesome portfolio management.
Very frequently, when we discuss a change initiative failure, we point as one of key reasons of the failure lack of support from top management. Much effort on team level is wasted because the organization on high level is set up to preserve status quo.
For a change agent looking to set an organization on a path on continuous, evolutionary change addressing the issue of stale mindset of the leaders of the company is frequently the key obstacle to overcome. Usually, a different set of tools is required to achieve that, especially for internal change agents who have hierarchy working against them.
I will show how we can use Portfolio Kanban as a low-friction method, which might be used by change agents, to steer mindset change among top managers. Similarly to team-level Kanban a few simple rules help to change how we look at project or product portfolio and how the work flows on high level.
Thinking about Kanban on portfolio level introduces the whole new set of challenges that can’t be solved with standard approach, so it is also a story about Kanban versatility and adaptability.
After all, if end results include better understanding of how the work is done, improved effectiveness and healthier work environment for teams it is worth giving a try, isn’t it?
Le slide del workshop tenuto il 13 dicembre 2013 alla conferenza Agile del PMI-NIC da Dario Giannoccaro e Giulio Roggero. Vengono presentate le basi di Lean e il Value Stream Mapping.
Visualizing the Product - PMI-NIC Agile Workshop 2013Giulio Roggero
Le slide del workshop tenuto il 13 dicembre 2013 alla conferenza Agile del PMI-NIC da Dario Giannoccaro e Giulio Roggero. Vengono presentati i Canvas come strumento di dialogo e condivisione.
Agilità interculturale
I valori dell'Agile Manifesto come fattore abilitante alla collaborazione dei team interculturali.
La collaborazione tra persone avviene grazie anche a una buona comunicazione. Culture differenti possono interpretare in modo diametralmente opposto atteggiamenti, frasi e situazioni. Se non opportunamente gestita la situazione porta a problemi critici di collaborazione all'interno del team minando le possibilità il successo del progetto.
L'approccio Agile al progetto tende a mitigare questo rischio grazie alla intrinseca resilienza dei principi ai quali si ispira. Comunicazione trasparente e feedback continui sul prodotto incrementale riducono notevolmente il rischio di non capirsi e di remare in direzioni diverse.
In questa presentazione vedremo alcune pratiche che favoriscono la collaborazione e fanno emergere il potenziale che i team interculturali possono dare ad un progetto.
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.
The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban
[Agile Adria Croatia 2014] The Road to a Fairly Predictable SystemZsolt Fabok
I see agile software development methodologies (Scrum and XP) and modern management methods (Kanban) as tools for predictability. The development organisation would like to know what is coming and whether it will be the right thing to do. On the other side, the management would like to know when the new features can hit the market. Both want predictability but in a different way. At Prezi, we are on the road to a fairly predictable system that can accurately tell us what the next right thing to do will be and also when it is going to be ready. We are far from a perfect system, we had our ups and downs, but after every down we are more up than before.
Full Cycle Traceability via a Product Portfolio KanbanStephen Chin
For large enterprises, successful Lean-Kanban development teams produce a huge amount of strain on the organization. The fast cycle time and rapid pace of change exposes dysfunctions in surrounding departments and exacerbates the need for traceability of requirements through the entire flow. In this presentation, we will show a practical application of a Product Portfolio Kanban to achieve the following:
* Executive visibility into the product development flow
* Strategic allocation and botteneck avoidance
* Full cycle mapping of delivered functionality back to requirements and revenue targets
* Results-based prioritization
Agile ways of working can be scaled from very small organizations to very large organizations. This requires adapting the teams and organization as the scale of operations change. Scrum and Kanban as well as Scrum-Ban can be used simultaneously in the organization. Ideally, individual teams should be able to select the best suited way to apply agile to their work. Priorities and changes should come both from top down and bottom up. Transparency is essential for right and justified decisions.
Portfolio Kanban - Low-Friction Method to Improve Organization's EffectivenessPawel Brodzinski
When we think about improving effectiveness we often focus on team level. The sources of ineffectiveness, however, are often rooted on a different level - in project portfolio. Too many concurrent projects, little knowledge about available capabilities and lack of discussion on cost and value often result in a situation where main decision factor is a gut feeling.
Common approaches to solve the problem are heavy-weight and strongly formalized. On the other hand Portfolio Kanban is a low-friction method that allows tackling the issue steering change at PMO level. As with every Kanban implementation there is little, if any, changes at the very beginning and changes are steered in evolutionary manner.
The picture isn’t rosy though. As long as you can say that there are standard approaches to introducing Kanban on a team level, there are no for portfolio level. As long as the method itself is easy to operate, its implementation is going to be anything but obvious and simple.
In the last 24 months, we've transformed the way we work using the Scaled Agile Framework. To help with the transformation, we are also using UX practices, design thinking and lean startup methods.
By the end of this presentation, you will understand how we have leveraged UX practices, innovation games and design sprints to improve the maturation of the business needs and their prioritisation to best fit what our users want and deliver value in a continuous flow.
Lean Kanban India 2018 | A Design Thinking Approach towards Business Agility...LeanKanbanIndia
Session Title:
A Design Thinking Approach towards Business Agility with The Kanban Method
Session Overview:
In this talk, we go through the journey of an organization towards Business Agility. Wikipedia defines Business Agility as the distinct qualities that allow organisations to respond rapidly to changes in the internal and external environment without losing momentum or vision. Adaptability, flexibility and balance are three qualities essential to long-term business agility.
This talk is not about a specific Agile method. We will explain how we took a Design Thinking approach to create a Transformation roadmap that will help the organization move towards Business Agility. We will share a measurement framework that we put in place to help teams continuously evolve.
We will end this session with a quick comparison of this approach versus the STATIK approach and how they complement each other.
Learning objectives
Understand the approach on how to create a Transformation roadmap - what "key" elements to follow
How to continuously Inspect and Adapt?
Define a simple/easy measurement framework to assist in this journey.
The agile journey of Telia Estonia: experiments and discoveries - Agile Satur...Kristjan Sillmann
How to deal with 150 projects on a waiting list, if they are on the same level of importance and urgency? How to help business overcome the fear of building only small part of their grand vision? How to grow intrapreneurship in the hierarchic and matrix organization and support the people in their new roles?
In this talk you’ll see what experiments we had, what we learned from these, where we failed and where we succeeded.
Scaling Scrum using Lean/Kanban in AmdocsYuval Yeret
Learn how Amdocs and Agilesparks took an enterprise Scrum implementation to the next step with Lean/Kanban - Presented in the Lean Software and Systems Conference 2010 in Atlanta
Epic are used in Agile product management to structure tasks and establish hierarchy during the Agile Development phase. A user story is a smaller task that is part of an epic, which is a larger piece of work. An Epic frequently spans several sprints, teams, and even numerous projects. Before they can begin to extract functionality from epics, product folks must first deconstruct them into stories.
Within an Epic, all user stories have the same strategic objective i.e. Agile Development and high-level client objective. Similar to this, when numerous epics have a similar goal, they are compiled into a larger body of work known as a "theme." The scope of an Epic will alter as sprints are finished and our knowledge of the demands of the client grows, and new user stories may be added to or taken out of the epic.
Creating a Lean PMO. Empower People, Enable FlowJulee Everett
Align. Fund teams, not projects. Leave them alone to do what they said they would do. Adapt. Sound easy? Then why do we make it so complicated? Stop being good at process & start getting good at business.
Lean Startup: It's Not Just Technology, Lives are at StakeKen Power
This is the slide deck from my keynote talk at the first Serbian ICT conference on Technology and Entrepreneurship, held Thursday November 22, 2012 in Belgrade.
For more notes, please see my corresponding Blog entry at http://systemagility.com/2012/11/22/lean-startup-and-lives/
I would love to hear your thoughts and feedback.
10 steps to a successsful enterprise agile transformation global scrum 2018Agile Velocity
Presented at Scrum Gathering Minneapolis, Senior Agile Coach and Trainer Mike Hall provides leaders and managers 10 steps to a successful enterprise Agile transformation.
Telligent - Spur Your Employees to InnovationTelligent
Leverage employee collaboration to spur innovation.
How can you surface innovation opportunities within your organization? Challenge each employee to continuous improvement and innovation by providing a robust, transparent platform for clear and constant communication.
See how Mota-Engil is enhancing collaboration by leveraging Telligent Community and Telligent Enterprise to:
Surface and evaluate employee-based knowledge
Capture the innovation process from beginning to completion
Align key employees with strategic initiatives
Foster inter-department collaboration to enhance quality assurance
Transform the way your employees work with these practical insights from Mota-Engil and weListen executives.
هذه المحاضرة تتحدث عن مكتب إدارة المشاريع الرشيق
The Agile PMO
قمت في هذه المحاضرة بتعريف الإدارة الرشيقة للمشاريع او ال
Agile
وعرفت أيضا مكتب إدارة المشاريع
PMO
ومن ثم شرحت معني مكتب إدارة المشاريع الرشيق
Agile PMO.
بعد ذلك شرحت الأسباب التي أدت لقيام مكتب إدارة المشاريع الرشيق
Agile PMO
والفوائد الناتجة من تطبيقه في المؤسسات.
ومن ثم تطرقت للطرق الأربعة التي يمكن أن يلجأ إليها مكتب إدارة المشاريع الرشيق
Agile PMO
وذلك لجلب الرشاقة او ال
Agility
للمؤسسة التي يعمل فيها ال
PMO.
ProductCamp Singapore #1 - Lean in Product ManagementMichael Ong
Presented at ProductCamp Singapore #1
Conversations driven so slides would only provide half the story
Sharing my experience with Lean thinking in two different organisations at iProperty (250+ people) & bellabox (20 people)
Great to hear feedback from participants in unconference sessions
Similar to Kanban Portfolio Management, a real case. (20)
What a Platform is? Which is the role of Engineers? How to improve time-to-market and reduce total cost of ownership moving from project to product mindset?
Those are just of some questions that Platform Engineers are answering everyday. This is a draft presentation of my next presentation about Platforms and Software Engineering.
Platform governance, gestire un ecosistema di microservizi a livello enterpriseGiulio Roggero
A livello enterprise, le moderne architetture distribuite coinvolgono molti team differenti, centinaia di sviluppatori e operations e migliaia microservizi ed API in produzione. Come si può gestire questa
e o
un'esplosione di costi e preservando il time-to-market?
Molte aziende hanno costruito negli anni sistemi informatici complessi che gestiscono i processi interni e i processi di gestione i clienti/fornitori. Con il cambiamento delle abitudini dei consumatori quello che una volta si faceva intermediato da un agente, commesso o addetto che usava il sistema gestionale per rispondere alla richiesta del cliente ora si fa in modalità self service semplicemente con uno smartphone, il cliente si aspetta di essere autonomo nel rapporto con l’azienda. L’esperienza che ci si aspetta come consumatore è quella che si vive usando piattaforma native digitali come ad esempio Netflix e Spotify. Il problema è che la maggior parte delle aziende non è partita nativamente digitale e non è possibile azzerare tutto e ripartire da capo senza correre rischi di business continuity importanti che vedono milioni di clienti coinvolti e impatti significativi a livello economico in caso di down. Se non è possibile ripartire da zero, quindi come fare? Una risposta è un approccio graduale di evoluzione architetturale e tecnologica dove Kubernetes, e il suo ecosistema, giocano un ruolo chiave. In questa presentazione vedremo i tre principi cardine sulla quale si basa questa strategia: API as a Product; architetture evolutive; fast data con pattern CQRS; che si uniscono per creare una strategia di Modernizzazione delle Applicazioni utilizzando i componenti dell’ecosistema del landscape CNCF (https://landscape.cncf.io). Da qui capiremo quali siano i benefici nel breve, medio e lungo termine e quali passi iniziare a fare per avviare questa strategia.
E’ meglio separare i microservizi per layer o per scopo? Quanti gateway devo avere? E’ necessario un pub/sub per far comunicare i microservizi? La persistenza dove la metto? Quali linguaggi uso? Sono alcune delle domande tipiche che ci si pone quando si parte a disegnare e sviluppare una piattaforma moderna basata su microservizi e containers. In questo talk vedremo alcuni stili architetturali e buone pratiche di test, deploy, monitoraggio e business continuity per creare piattaforme robuste e scalabili. Spoiler: non parlerò di Twelve-Factor App :-)
Do pair programming with an artificial intelligenceGiulio Roggero
Si prevede che nel 2022 il 40% dello sviluppo di applicazioni software sia co-sviluppato insieme ad una intelligenza artificiale (sorgente Gartner 2019).
Ci pensate? Come sarà sviluppare in pairing? Saremo più produttivi? Faremo meno errori? Il codice sarà più pulito? La gestione dei feature toggle sarà più semplice? I rilasci saranno ancora più semplici?
Immaginate fare ping-pong programming con la vostra intelligenza artificiale personale, quanto sarebbe motivante e divertente scrivere codice. E se applichiamo TDD potremmo arrivare ad un livello di clean code mai visto. Anche le persone meno esperte potrebbero imparare a sviluppare in modo pulito ed efficace.
In questa mezz’ora voglio esplorare insieme a voi questo modo che sembra lontano (vi ricordate 10 anni fa delle macchine che guidano da sole? :-) ) ma in realtà è già intorno a noi e si sta facendo sempre più pervasivo.
Come i Microservizi favoriscono il lavoro dei Feature TeamsGiulio Roggero
In un contesto Agile i Feature Teams sono una delle strutture organizzative più efficaci per sviluppare un ecosistema complesso in modo rapido, mantenendo alta la qualità e basso il TCO (total cost of ownership). Spesso questi team sono però vincolati da architetture monolitiche, o a lasagna/spaghetti, che non consentono di operare end-to-end sulle feature, creando dipendenze tra team, colli di bottiglia e frustrazione. Lo stile architetturale a Microservizi (sì, è uno stile e non un pattern e quindi va interpretato a seconda dei casi) da una mano a questi team ad essere più indipendenti tra loro e li aiuta a lavorare tutti con lo stesso scopo: generare valore per gli utenti finali in modo continuo. In questo talk vedremo come organizzare più team che lavorano su uno stesso prodotto e come lo stile architetturale a Microservizi supporti questa organizzazione evolvendo con l'evolversi dei team.
La crescita veloce è uno degli aspetti più rilevanti dell'economia negli ultimi anni. Startup, scaleup e unicorni sono tutte aziende che, anno su anno, crescono in modo vertiginoso a livello di numeri di business e di persone, facendo scaling dei sistemi IT.
Le aziende "pre native digitali" stanno guardando a queste realtà come a potenziali (o reali) competitor e si stanno organizzando per scalare. Ma un conto è avere una struttura di business nata per scalare, un conto è scalare con un business avviato da almeno 20/30 anni. Cultura aziendale, sistemi IT e tecnologie si sono stratificati nel tempo e possono essere un ostacolo a questa corsa verso l'alto.
In questo talk vedremo buone pratiche, tecniche e modelli per scalare realtà enterprise sia a livello tecnico (e tecnologico), sia a livello organizzativo. Lo faremo attraverso esempi concreti di casi reali e proponendo spunti su come superare le difficoltà che si incontrano durante il percorso.
Parleremo di Cloud Native, di migrazione da Monoliti e Microservices, di API as a Product, di Organizzazioni Enterprise in stile Open Source e di Cultura Aziendale.
Microservices, Microfrontends and Feature TeamsGiulio Roggero
Quali sono le buone pratiche per progettare un'architettura in stile Microservices?
Come rendere evolutiva un'applicazione Frontend senza che invecchi dopo poco tempo?
Come organizzare più team che lavorano su una Piattaforma che ha centinaia di Microservices e decine di Frontend?
A queste tre domande risponderò durante il talk con esempi pratici e casi di vita vissuta.
L’eccellenza tecnica è uno dei principi cardine dell’agilità e come tale favorisce la creazione di valore mantenendo le architetture semplici e i processi snelli. I sistemi legacy sono però un ostacolo per la ricerca dell’eccellenza tecnica. Di fatto il debito tecnico che si stratifica negli anni non aiuta la continua innovazione e la business agility.
Le nuove tecnologie, come Cloud e Big Data, sono degli abilitatori per creare applicazioni semplici e mantenibili nel futuro. Ma da soli non bastano.
Il problema è che ogni tecnologia ha le sue complessità e spesso queste sono indipendenti dalle logiche applicative. Può succedere che il team spenda più tempo a mettere in piedi l’infrastruttura e la connessione a tutti i servizi Cloud, che a scrivere le parti applicative. E questo tempo spesso si replica N-volte quanti sono gli N-progetti sviluppati da diversi team.
Manca un concetto comune di infrastruttura e piattaforma.
In questo talk vedremo come l’ “infrastruttura invisibile” possa semplificare il lavoro dei team favorendo l’eccellenza tecnica e la business agility.
Piccola anticipazione. L’infrastruttura invisibile é come le rotaie per un viaggiatore in treno: si gode il viaggio sorseggiando la sua bevanda preferita senza preoccuparsi della complessità che letteralmente viaggia sotto i suoi piedi.
Agile è entrato nel gergo comune di molte aziende che hanno a che fare con progetti IT. Questa è una buona cosa: il termine è conosciuto e accettato come una buona prassi, le persone sono ben disposte ad adottare metodi e pratiche che consentono di migliorare la gestione del ciclo di vita di un prodotto software e sono favorevoli al cambiamento.
Quando però si parte veramente mi sono trovato in diverse situazioni dove Agile si limitava alla parte “persone” e “organizzazione” ma non entrava nel merito di come si sviluppa il codice!
La provocazione “Stop Meeting, Start Coding” vuol ridurre all’essenziale i momenti di confronto e concentrarsi a scrivere buon codice, insieme!
In questo talk presenterò alcune buone pratiche di coding che favoriscono anche l’efficacia organizzativa.
Il software che oggi produce valore è stato scritto parecchi anni fa. Il costo di manutenzione ed evoluzione sta diventando sempre più alto.
Parallelamente stiamo vivendo una forte accelerazione sul digitale: omnicanalità, self-service e ubiquità sono fattori che stanno influenzando i comportamenti delle persone. Alle aziende si chiede sempre più innovazione e semplicità dei servizi offerti.
In questa presentazione guarderemo avanti nel futuro, sui software che produrranno valore nei prossimi 10 anni e che stiamo costruendo ora.
Proveremo a dare una possibile risposta a questa domanda:
“come possiamo evitare di accumulare un debito tecnico difficilmente ripagabile e nel contempo seguire l’accelerazione che il mercato ci sta chiedendo senza impattare sul business esistente?”
La multicanalità è il contesto del Cliente digitale di oggi e le spaghetti API stanno prendendo il sopravvento. Il Business e l'IT sono in prima linea a garantire time-to-market e qualità mettendo sotto stress la struttura organizzativa e le tecnologie. Organizzarsi in modo agile non basta, serve anche una strategia chiara di piattaforma!
La presentazione introduce il problema che oggi le aziende hanno a livello IT: tante applicazioni sparse che accedono ai sistemi core in modo non organico (spaghetti API). Questo comporta: rallentamento del time-to-market, attriti nelle relazioni e prodotti poco coerenti tra di loro. Durante una trasformazione digitale si pensa in primo luogo a riorganizzare persone in modo da snellire i processi. Questo è di sicuro aiuto ma da solo non è sufficiente: se i sistemi sui quali lavorano i team non evolvono i team possono essere agili quanto vogliono ma non riescono a tenere il passo con il mercato. La zavorra del debito tecnico di codice e API a spaghetti non è facilmente ripagabile. E’ necessario cambiare le strategie architetturali e creare un sistema che si possa rifare a pezzi e far evolvere. Vedremo come una strategia di Piattaforma Digitale possa essere a supporto per la trasformazione Agile.
This is the updated version of the presentation https://www.slideshare.net/GiulioRoggero/how-a-kanban-board-works.
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
--- BONUS ---
Here you can find a more details on lead time and CFD and a new board about Scrum Team Roadmap.
API Conf 2017 - Allineare il business e la tecnologia grazie alle apiGiulio Roggero
Spesso i termini usati dal business non si ritrovano nell'architettura informatica sottostante. E questo alla lunga genera incomprensioni e problemi. In questi 10' vedremo come, in 3 semplici passi, sia possibile allineare i termini usati dal business e dai tecnici. Per facilitare la spiegazione vedremo due brevi esempi di casi reali: Trenord e Foorban.
Talk Agile O'Day Napoli - 2017
Cosa contraddistingue uno sviluppatore affidabile? In questa presentazione si parla di:
- Semplicità
- Debito tecnico e valore
- Test prima!
- Tutto automatico
- Utenti al centro
Favorire i feature teams con architetture microservicesGiulio Roggero
Il talk parte da una osservazione sui progetti che sto sviluppando: Agile Scaling significa prima di tutto Software Scaling.
Si parla spesso di come "scalare agile" e di quali siano le strategie migliori per dominare la complessità che comporta il moltiplicarsi dei canali di comunicazione di tante persone che lavorano sullo stesso progetto.
Molte soluzioni sono proposte ed adottate, a volte hanno successo a volte falliscono. Molti concordano che team organizzati a "strati" sono disfunzionali e alla lunga portano a conflitti e colli di bottiglia. Organizzarsi a Feature Teams, Spotify ne è un esempio, favorisce la semplificazione delle relazioni e un miglioramento di qualità e velocità di sviluppo.
Ma come? La risposta non è semplice e dipende da tanti fattori tra i quali: maturità del prodotto, cultura aziendale e competenza delle persone.
La soluzione che presenterò si basa sul principio che le persone si organizzano per lavorare al meglio sulla codebase che stanno creando. Il vero cambiamento culturale agile avviene quando questo si riflette sul codice. Cambiare tutta l'azienda e avere ancora il codice organizzato a silos è comunque inefficiente e alla lunga porterà nuovamente ad un'organizzazione a Silos 2.0 :-)
In questo talk vedremo come sia possibile favorire la riorganizzazione dei team adottando un pattern architetturale a microservizi con esempi pratici di team che hanno iniziato ad adottare questo approccio e si sono ri-organizzati in modo naturale.
Buy Verified PayPal Account | Buy Google 5 Star Reviewsusawebmarket
Buy Verified PayPal Account
Looking to buy verified PayPal accounts? Discover 7 expert tips for safely purchasing a verified PayPal account in 2024. Ensure security and reliability for your transactions.
PayPal Services Features-
🟢 Email Access
🟢 Bank Added
🟢 Card Verified
🟢 Full SSN Provided
🟢 Phone Number Access
🟢 Driving License Copy
🟢 Fasted Delivery
Client Satisfaction is Our First priority. Our services is very appropriate to buy. We assume that the first-rate way to purchase our offerings is to order on the website. If you have any worry in our cooperation usually You can order us on Skype or Telegram.
24/7 Hours Reply/Please Contact
usawebmarketEmail: support@usawebmarket.com
Skype: usawebmarket
Telegram: @usawebmarket
WhatsApp: +1(218) 203-5951
USA WEB MARKET is the Best Verified PayPal, Payoneer, Cash App, Skrill, Neteller, Stripe Account and SEO, SMM Service provider.100%Satisfection granted.100% replacement Granted.
Remote sensing and monitoring are changing the mining industry for the better. These are providing innovative solutions to long-standing challenges. Those related to exploration, extraction, and overall environmental management by mining technology companies Odisha. These technologies make use of satellite imaging, aerial photography and sensors to collect data that might be inaccessible or from hazardous locations. With the use of this technology, mining operations are becoming increasingly efficient. Let us gain more insight into the key aspects associated with remote sensing and monitoring when it comes to mining.
RMD24 | Retail media: hoe zet je dit in als je geen AH of Unilever bent? Heid...BBPMedia1
Grote partijen zijn al een tijdje onderweg met retail media. Ondertussen worden in dit domein ook de kansen zichtbaar voor andere spelers in de markt. Maar met die kansen ontstaan ook vragen: Zelf retail media worden of erop adverteren? In welke fase van de funnel past het en hoe integreer je het in een mediaplan? Wat is nu precies het verschil met marketplaces en Programmatic ads? In dit half uur beslechten we de dilemma's en krijg je antwoorden op wanneer het voor jou tijd is om de volgende stap te zetten.
Explore our most comprehensive guide on lookback analysis at SafePaaS, covering access governance and how it can transform modern ERP audits. Browse now!
As a business owner in Delaware, staying on top of your tax obligations is paramount, especially with the annual deadline for Delaware Franchise Tax looming on March 1. One such obligation is the annual Delaware Franchise Tax, which serves as a crucial requirement for maintaining your company’s legal standing within the state. While the prospect of handling tax matters may seem daunting, rest assured that the process can be straightforward with the right guidance. In this comprehensive guide, we’ll walk you through the steps of filing your Delaware Franchise Tax and provide insights to help you navigate the process effectively.
Personal Brand Statement:
As an Army veteran dedicated to lifelong learning, I bring a disciplined, strategic mindset to my pursuits. I am constantly expanding my knowledge to innovate and lead effectively. My journey is driven by a commitment to excellence, and to make a meaningful impact in the world.
Attending a job Interview for B1 and B2 Englsih learnersErika906060
It is a sample of an interview for a business english class for pre-intermediate and intermediate english students with emphasis on the speking ability.
"𝑩𝑬𝑮𝑼𝑵 𝑾𝑰𝑻𝑯 𝑻𝑱 𝑰𝑺 𝑯𝑨𝑳𝑭 𝑫𝑶𝑵𝑬"
𝐓𝐉 𝐂𝐨𝐦𝐬 (𝐓𝐉 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬) is a professional event agency that includes experts in the event-organizing market in Vietnam, Korea, and ASEAN countries. We provide unlimited types of events from Music concerts, Fan meetings, and Culture festivals to Corporate events, Internal company events, Golf tournaments, MICE events, and Exhibitions.
𝐓𝐉 𝐂𝐨𝐦𝐬 provides unlimited package services including such as Event organizing, Event planning, Event production, Manpower, PR marketing, Design 2D/3D, VIP protocols, Interpreter agency, etc.
Sports events - Golf competitions/billiards competitions/company sports events: dynamic and challenging
⭐ 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐝 𝐩𝐫𝐨𝐣𝐞𝐜𝐭𝐬:
➢ 2024 BAEKHYUN [Lonsdaleite] IN HO CHI MINH
➢ SUPER JUNIOR-L.S.S. THE SHOW : Th3ee Guys in HO CHI MINH
➢FreenBecky 1st Fan Meeting in Vietnam
➢CHILDREN ART EXHIBITION 2024: BEYOND BARRIERS
➢ WOW K-Music Festival 2023
➢ Winner [CROSS] Tour in HCM
➢ Super Show 9 in HCM with Super Junior
➢ HCMC - Gyeongsangbuk-do Culture and Tourism Festival
➢ Korean Vietnam Partnership - Fair with LG
➢ Korean President visits Samsung Electronics R&D Center
➢ Vietnam Food Expo with Lotte Wellfood
"𝐄𝐯𝐞𝐫𝐲 𝐞𝐯𝐞𝐧𝐭 𝐢𝐬 𝐚 𝐬𝐭𝐨𝐫𝐲, 𝐚 𝐬𝐩𝐞𝐜𝐢𝐚𝐥 𝐣𝐨𝐮𝐫𝐧𝐞𝐲. 𝐖𝐞 𝐚𝐥𝐰𝐚𝐲𝐬 𝐛𝐞𝐥𝐢𝐞𝐯𝐞 𝐭𝐡𝐚𝐭 𝐬𝐡𝐨𝐫𝐭𝐥𝐲 𝐲𝐨𝐮 𝐰𝐢𝐥𝐥 𝐛𝐞 𝐚 𝐩𝐚𝐫𝐭 𝐨𝐟 𝐨𝐮𝐫 𝐬𝐭𝐨𝐫𝐢𝐞𝐬."
3.0 Project 2_ Developing My Brand Identity Kit.pptxtanyjahb
A personal brand exploration presentation summarizes an individual's unique qualities and goals, covering strengths, values, passions, and target audience. It helps individuals understand what makes them stand out, their desired image, and how they aim to achieve it.
India Orthopedic Devices Market: Unlocking Growth Secrets, Trends and Develop...Kumar Satyam
According to TechSci Research report, “India Orthopedic Devices Market -Industry Size, Share, Trends, Competition Forecast & Opportunities, 2030”, the India Orthopedic Devices Market stood at USD 1,280.54 Million in 2024 and is anticipated to grow with a CAGR of 7.84% in the forecast period, 2026-2030F. The India Orthopedic Devices Market is being driven by several factors. The most prominent ones include an increase in the elderly population, who are more prone to orthopedic conditions such as osteoporosis and arthritis. Moreover, the rise in sports injuries and road accidents are also contributing to the demand for orthopedic devices. Advances in technology and the introduction of innovative implants and prosthetics have further propelled the market growth. Additionally, government initiatives aimed at improving healthcare infrastructure and the increasing prevalence of lifestyle diseases have led to an upward trend in orthopedic surgeries, thereby fueling the market demand for these devices.
Enterprise Excellence is Inclusive Excellence.pdfKaiNexus
Enterprise excellence and inclusive excellence are closely linked, and real-world challenges have shown that both are essential to the success of any organization. To achieve enterprise excellence, organizations must focus on improving their operations and processes while creating an inclusive environment that engages everyone. In this interactive session, the facilitator will highlight commonly established business practices and how they limit our ability to engage everyone every day. More importantly, though, participants will likely gain increased awareness of what we can do differently to maximize enterprise excellence through deliberate inclusion.
What is Enterprise Excellence?
Enterprise Excellence is a holistic approach that's aimed at achieving world-class performance across all aspects of the organization.
What might I learn?
A way to engage all in creating Inclusive Excellence. Lessons from the US military and their parallels to the story of Harry Potter. How belt systems and CI teams can destroy inclusive practices. How leadership language invites people to the party. There are three things leaders can do to engage everyone every day: maximizing psychological safety to create environments where folks learn, contribute, and challenge the status quo.
Who might benefit? Anyone and everyone leading folks from the shop floor to top floor.
Dr. William Harvey is a seasoned Operations Leader with extensive experience in chemical processing, manufacturing, and operations management. At Michelman, he currently oversees multiple sites, leading teams in strategic planning and coaching/practicing continuous improvement. William is set to start his eighth year of teaching at the University of Cincinnati where he teaches marketing, finance, and management. William holds various certifications in change management, quality, leadership, operational excellence, team building, and DiSC, among others.
Skye Residences | Extended Stay Residences Near Toronto Airportmarketingjdass
Experience unparalleled EXTENDED STAY and comfort at Skye Residences located just minutes from Toronto Airport. Discover sophisticated accommodations tailored for discerning travelers.
Website Link :
https://skyeresidences.com/
https://skyeresidences.com/about-us/
https://skyeresidences.com/gallery/
https://skyeresidences.com/rooms/
https://skyeresidences.com/near-by-attractions/
https://skyeresidences.com/commute/
https://skyeresidences.com/contact/
https://skyeresidences.com/queen-suite-with-sofa-bed/
https://skyeresidences.com/queen-suite-with-sofa-bed-and-balcony/
https://skyeresidences.com/queen-suite-with-sofa-bed-accessible/
https://skyeresidences.com/2-bedroom-deluxe-queen-suite-with-sofa-bed/
https://skyeresidences.com/2-bedroom-deluxe-king-queen-suite-with-sofa-bed/
https://skyeresidences.com/2-bedroom-deluxe-queen-suite-with-sofa-bed-accessible/
#Skye Residences Etobicoke, #Skye Residences Near Toronto Airport, #Skye Residences Toronto, #Skye Hotel Toronto, #Skye Hotel Near Toronto Airport, #Hotel Near Toronto Airport, #Near Toronto Airport Accommodation, #Suites Near Toronto Airport, #Etobicoke Suites Near Airport, #Hotel Near Toronto Pearson International Airport, #Toronto Airport Suite Rentals, #Pearson Airport Hotel Suites
Cracking the Workplace Discipline Code Main.pptxWorkforce Group
Cultivating and maintaining discipline within teams is a critical differentiator for successful organisations.
Forward-thinking leaders and business managers understand the impact that discipline has on organisational success. A disciplined workforce operates with clarity, focus, and a shared understanding of expectations, ultimately driving better results, optimising productivity, and facilitating seamless collaboration.
Although discipline is not a one-size-fits-all approach, it can help create a work environment that encourages personal growth and accountability rather than solely relying on punitive measures.
In this deck, you will learn the significance of workplace discipline for organisational success. You’ll also learn
• Four (4) workplace discipline methods you should consider
• The best and most practical approach to implementing workplace discipline.
• Three (3) key tips to maintain a disciplined workplace.
What are the main advantages of using HR recruiter services.pdfHumanResourceDimensi1
HR recruiter services offer top talents to companies according to their specific needs. They handle all recruitment tasks from job posting to onboarding and help companies concentrate on their business growth. With their expertise and years of experience, they streamline the hiring process and save time and resources for the company.
The world of search engine optimization (SEO) is buzzing with discussions after Google confirmed that around 2,500 leaked internal documents related to its Search feature are indeed authentic. The revelation has sparked significant concerns within the SEO community. The leaked documents were initially reported by SEO experts Rand Fishkin and Mike King, igniting widespread analysis and discourse. For More Info:- https://news.arihantwebtech.com/search-disrupted-googles-leaked-documents-rock-the-seo-world/
1. Kanban Portfolio Management
supported by Canvas,
a Real Case in Wolters Kluwer Italia.
Lean Kanban Southern Europe 2014
@giulioroggero www.agilereloaded.it
6. July 2013
“pilots are going well and now?”
“how can we scale the Pilot?”
200 initiative in-flight
400 person involved
We have
7. Visualize to share!
Projects Canvas Portfolio Kanban Boards
“Sala Caravaggio”
A room dedicated only to Initiatives Visualization
Executives meet every two weeks in this room to check impediments and to rank initiatives.
All departments are involved.
8. Pre-Funnel Funnel
Vision and T-Shirt Sizing Business Model, Business Case, Backlog, Devel, UAT, Deploy
Initiatives Gathering Initiatives Analysis and Implementation
12. May 2014 – Goals reached
• Board meetings are regular and useful.
• All information about project are now under control.
• All company departments are involved, not only ICT!
• More than 125 person, trained on Agile, Canvas and Kanban Boards, are participating to the portfolio model definition and
evolution.
• New roles have been identified: Demand Manager, Portfolio Facilitator.
• Only one reference per Initiative: the Product Owner.
• Some project have been discarded because other opportunities have been revealed by the Kanban Board.
• Continuous alignment
between Business and ICT
on more than 180 projects.
• Identified bottlenecks.
• Low resistance to change.
and more…
13. Next Challenges
Reduce WIP, sustain POs and avoid exceptions.
• The Product Owner role is vital for the Flow. We are defining a path to help POs in this journey.
• We are defining WIP limits monitoring a first rough estimation of them.
• Cross-department ranking is still to be done.
• We are preparing the 2015 budget starting from Pre-Funnel.
• Initiatives KPIs have to be defined.
• Initiatives Business Case definition is in draft.
• We need a better way to keep aligned the room and Atlassian Jira.
and more…
14. Thanks to Wolters Kluwer Italia for having given the permission for this presentation
@giulioroggero www.agilereloaded.it