How we make agile work
•Download as PPTX, PDF•
0 likes•76 views
The document discusses how UX can work within an Agile framework. There are three main challenges: 1) Sprints which have short timelines, so UX must test while planning and have product increments over multiple sprints. UX is also part of quality assurance. 2) Fixing issues when developers may not want to fix code or prioritize new features over fixes. The solution is dedicating time in sprints for UX fixes and having an iterative mindset. 3) Syncing between teams which requires clear communication through activities like feature kickoffs, standups, hanging designs visibly, and participating in task management software. The key is ensuring open communication throughout the process.
Report
Share
Report
Share
Recommended
How we Sort of Make Agile Work - A Case Study
This document discusses how UX designers can make agile work by addressing three main challenges: sprints, fixing issues, and syncing. For sprints, the author recommends testing while planning, using product increments over 7 weeks, and treating UX as part of QA. For fixing issues, the author suggests allocating 2 days in each sprint for UX/UI fixes and adopting an iterative mindset. For syncing, the key strategies are holding feature kickoffs, attending daily standups, sitting with developers, hanging up designs, and accessing work items in TFS. Effective communication is emphasized as critical for agile success.
Scrum Quick Overview
The document describes the Scrum process for developing software using roles like Product Owner, Scrum Master, Developers, and Testers. It outlines how the Product Owner prioritizes a backlog of features, Developers work in sprints to complete the highest priority tasks, and there are daily stand-ups and sprint demos to track progress and provide feedback.
Sharethrough's process evolution
The document describes the evolution of Sharethrough's product development processes from 2008 to the present. It began with an informal "cowboy" approach with 3 engineers in 2008. In 2009, they adopted Agile Scrum with 4-5 engineers and 1 product manager. In 2010, they tried DIY XP with pairing and testing but found it slowed productivity. They worked with Pivotal from 2011-2012 using XP which worked well with the right discipline. In 2013, they experimented with balanced teams but found the approach only worked on average. Currently, they use Agile XP with roadmapping, milestones, and 2 week sprints planned by cross-functional teams of 12 engineers, 2 PMs, and 1 designer.
Spécial levée de fonds par Nicolas Venet de Meero
This document summarizes the scaling of Meero's product team from 5 developers in 2018 to over 70 developers spread across 13 squads and 3 tribes in 2019 as the company grew rapidly. Key phases included initially having no formal product team and responsibilities dispersed (Phase 1), forming an initial product team of 5 people (Phase 2), moving to 3 squads of 5-18 people each (Phase 3), and expanding further to 13 squads organized into 3 tribes (Phase 4) as the workforce and needs grew. The scaling process emphasized continuous improvement, a human-first approach, team spirit, and necessary delegation and overcommunication.
MBTS Round 2, Week 2
The team made significant progress on their plate scanner hardware and software. They finished constructing the plate scanner hardware by mounting the microscope and adding metal braces for stability. On the software side, they are able to take individual pictures using OpenCV but still need to calibrate motor movement, implement image stitching, and update the GUI. They also designed a new microgravity habitat for tardigrades consisting of a minimalistic container that holds grow lights over an acrylic top with a cutout for a carbon sheet and spring to secure a petri dish. Their goals for the next period are to finish the plate scanner software, build the tardigrade habitat, finalize the summer program details, and find a location and teachers. Overall, the team
Agile Processes
The document discusses processes in software development and Agile methodologies like Scrum. It defines a process as a set of tasks and activities that take place during development, like programming, selling, testing, etc. Traditional "waterfall" processes are inflexible, while Agile focuses on feedback, working software, and responding to change. Scrum is presented as an Agile methodology, with roles like Product Owner and Scrum Master, and artifacts like the burndown chart. The document encourages learning from mistakes and having fun.
Multipack
In 11 steps, the document outlines a process for rapidly developing and launching an online web app product within 1 week using lean development principles. It discusses identifying a problem to solve, building a minimum viable product, using agile and scrum methodologies, launching early, incorporating testing and continuous integration, engaging early adopters for feedback, being prepared to pivot based on feedback, planning for future iterations, considering revenue strategies, and drawing inspiration from quick wins.
Distributed Teams - Hello? Can anyone hear me?
In the ideal perfect world there will be rainbows and unicorns and teams that all sit together. In reality, most teams have to deal with distribution in one form or another. For some: it’s team members spread across a building, for others it’s team members in other parts of the world in different time zones.
Have you even been on a call where you can hear someone ordering coffee, or a dog barking? My favorite is being told someone is joining the call, after you've spent 5 minutes explaining something in detail. Mostly distributed meetings are boring, and not really worth the time and effort.
As agile coaches we truly value face to face communication and visible boards and sticky-notes, we also value working from anywhere, having pets in the office and not having to travel. So what is possible here? We decided to fully immerse ourselves into the distributed world and see what happened. We were amazed - we managed to build trust, explore and discover great collaborative tools and we improved communication.
We would like to share some of our discoveries and tips with you. Join us to explore how agile can work for distributed teams.
Recommended
How we Sort of Make Agile Work - A Case Study
This document discusses how UX designers can make agile work by addressing three main challenges: sprints, fixing issues, and syncing. For sprints, the author recommends testing while planning, using product increments over 7 weeks, and treating UX as part of QA. For fixing issues, the author suggests allocating 2 days in each sprint for UX/UI fixes and adopting an iterative mindset. For syncing, the key strategies are holding feature kickoffs, attending daily standups, sitting with developers, hanging up designs, and accessing work items in TFS. Effective communication is emphasized as critical for agile success.
Scrum Quick Overview
The document describes the Scrum process for developing software using roles like Product Owner, Scrum Master, Developers, and Testers. It outlines how the Product Owner prioritizes a backlog of features, Developers work in sprints to complete the highest priority tasks, and there are daily stand-ups and sprint demos to track progress and provide feedback.
Sharethrough's process evolution
The document describes the evolution of Sharethrough's product development processes from 2008 to the present. It began with an informal "cowboy" approach with 3 engineers in 2008. In 2009, they adopted Agile Scrum with 4-5 engineers and 1 product manager. In 2010, they tried DIY XP with pairing and testing but found it slowed productivity. They worked with Pivotal from 2011-2012 using XP which worked well with the right discipline. In 2013, they experimented with balanced teams but found the approach only worked on average. Currently, they use Agile XP with roadmapping, milestones, and 2 week sprints planned by cross-functional teams of 12 engineers, 2 PMs, and 1 designer.
Spécial levée de fonds par Nicolas Venet de Meero
This document summarizes the scaling of Meero's product team from 5 developers in 2018 to over 70 developers spread across 13 squads and 3 tribes in 2019 as the company grew rapidly. Key phases included initially having no formal product team and responsibilities dispersed (Phase 1), forming an initial product team of 5 people (Phase 2), moving to 3 squads of 5-18 people each (Phase 3), and expanding further to 13 squads organized into 3 tribes (Phase 4) as the workforce and needs grew. The scaling process emphasized continuous improvement, a human-first approach, team spirit, and necessary delegation and overcommunication.
MBTS Round 2, Week 2
The team made significant progress on their plate scanner hardware and software. They finished constructing the plate scanner hardware by mounting the microscope and adding metal braces for stability. On the software side, they are able to take individual pictures using OpenCV but still need to calibrate motor movement, implement image stitching, and update the GUI. They also designed a new microgravity habitat for tardigrades consisting of a minimalistic container that holds grow lights over an acrylic top with a cutout for a carbon sheet and spring to secure a petri dish. Their goals for the next period are to finish the plate scanner software, build the tardigrade habitat, finalize the summer program details, and find a location and teachers. Overall, the team
Agile Processes
The document discusses processes in software development and Agile methodologies like Scrum. It defines a process as a set of tasks and activities that take place during development, like programming, selling, testing, etc. Traditional "waterfall" processes are inflexible, while Agile focuses on feedback, working software, and responding to change. Scrum is presented as an Agile methodology, with roles like Product Owner and Scrum Master, and artifacts like the burndown chart. The document encourages learning from mistakes and having fun.
Multipack
In 11 steps, the document outlines a process for rapidly developing and launching an online web app product within 1 week using lean development principles. It discusses identifying a problem to solve, building a minimum viable product, using agile and scrum methodologies, launching early, incorporating testing and continuous integration, engaging early adopters for feedback, being prepared to pivot based on feedback, planning for future iterations, considering revenue strategies, and drawing inspiration from quick wins.
Distributed Teams - Hello? Can anyone hear me?
In the ideal perfect world there will be rainbows and unicorns and teams that all sit together. In reality, most teams have to deal with distribution in one form or another. For some: it’s team members spread across a building, for others it’s team members in other parts of the world in different time zones.
Have you even been on a call where you can hear someone ordering coffee, or a dog barking? My favorite is being told someone is joining the call, after you've spent 5 minutes explaining something in detail. Mostly distributed meetings are boring, and not really worth the time and effort.
As agile coaches we truly value face to face communication and visible boards and sticky-notes, we also value working from anywhere, having pets in the office and not having to travel. So what is possible here? We decided to fully immerse ourselves into the distributed world and see what happened. We were amazed - we managed to build trust, explore and discover great collaborative tools and we improved communication.
We would like to share some of our discoveries and tips with you. Join us to explore how agile can work for distributed teams.
What Makes an Agile Manager?
The document discusses what makes an agile project manager by outlining that an agile project manager facilitates change through conversations and user-centered practices, leads through servant leadership rather than incentives or punishment, and focuses on adapting to change rather than rigidly following a predetermined plan. The document also briefly defines a project and manager before presenting an "Agile Management Manifesto" with these principles.
Agile myth 1 no plan and no doc
Agile projects do involve planning contrary to a common myth. There are five levels of planning - product vision, roadmap, release plan, iteration plan, and daily plan. While detailed upfront planning is not done, planning occurs continuously. Another myth is that there is no feedback on progress without a plan, but product and sprint backlogs provide burn down visibility. Finally, while the scope may be adjusted, Agile projects have timeboxes and budgets, and documentation is still created when prioritized and not a roadblock to delivery.
Agile UX with Lego
Are you struggling to integrate User Experience techniques with your agile teams? Are any of these patterns familiar?
The UX team works one sprint ahead of the development team.
UX designers spend lots of energy on high fidelity mock-ups which the developers then ignore.
You produce working software each sprint, but recruiting users is time consuming so you only test with users before you release.
There is no time to incorporate changes from user feedback into the sprints before release.
The UX designers and the developers seem to speak a different language.
Developers get annoyed because the UX design work great on iOS, but clashes with Android standards.
If so join us for a fun interactive session where we use Lego to explore how you can overcome challenges like this in your own environment. You’ll work as a team doing both UX design, and development (with Lego), and see how and why these patterns happen, as well as what you can do about them.
This workshop is ideal for people from both the UX world, struggling to understand how to work with developers, and for developers struggling to understand what UX designers are trying to achieve.
PRINCE2 is dead! Long live Agile!
Presentation and workshop, looking at the question "Why still work with PRINCE"?
Part of the Agile Carnival evening, hosted by Agile Holland and LINKIT on February 21st, 2017
GETTING THINGS DONE: WHAT I LEARNED FROM APPLYING GTD
The document discusses lessons learned from applying the Getting Things Done (GTD) productivity system. It warns against making too many lists, trying to connect every action to a project, and putting projects on context lists. It also cautions spending too much time setting up apps instead of getting work done, and stresses that the motivation for using GTD is more important than the tools or system used. The key is to trust the process, avoid overcomplicating it, and stick to the system rather than getting distracted by perfecting the setup.
Scrum Basics
The document describes a typical project where a customer requests an object with 4 legs, 2 ears, 1 trunk, 1 tail, and 2 tusks to be delivered in 6 months. After 6 months, the project team delivers an object meeting all requirements plus a bonus pumpkin. However, the stakeholders were expecting an elephant and are unhappy with the delivered object. The document then discusses adopting agile and scrum practices like collaboration and feedback loops to better meet stakeholder expectations. It provides an overview of scrum roles, events, artifacts, and principles like transparency, inspection, and adaptation.
Guntis Smaukstelis (MightyFingers) @ TechHub Riga Meetup
MightyFingers CEO Guntis Smaukstelis visited TechHub Riga Meetup to tell the story behind the games and their MightyEditor.
First steps towards agility
Agile methodologies encourages teams to embrace the change and react quickly to the market & customer’s demands. Let’s look at how DevOps practices are meant to help teams achieve the agility they want.
Professional Progression - Gavin Elliott [Camp Digital 2018]
Discussing seniority in design, professional and personal development, the skills needed in more senior roles and how to become a great manager and leader.
Why Constraints are Good? A Case Study of an Enterprise Agile Transformation
Agile transformation requires understanding its rules by management. It is hard to leave status quo and change your way of thinking. It is especially hard when the previous model has been in use for many years. A frequent problem with Scrum / Kanban / Lean transformation is to go hard on deep water. Starting tommorow we're doing Scrum. Lack of understanding, communication chaos and rules distortion "just because daily is not working for us". What if take a different approach: slow and prudent? Let say iteratively. Gradually introduce another steps of chosen framework. However the question persists. How to effectively change our conservative organization into agile and constantly changing in response to business needs company?
Skalowanie Agile
The document discusses three case studies of scaling Agile practices to the enterprise level. The first case study describes challenges with a team using only Scrum practices and how adopting additional XP practices like test-driven development and continuous integration helped. The second case study explains problems that arose from multiple teams working on a shared backlog and lack of synchronization; Kanban was introduced to help. The third case study outlines issues with multiple outsourced teams and lack of integration; Kanban, additional roles, and improved coordination helped address these challenges at the portfolio level.
AgileHead - Product Development Services for Startups
This document describes AgileHead, an 18-member consulting group in Bangalore, India that provides product development services using an agile approach. They propose using a small core team of highly experienced developers, testers, and managers rather than large outsourced teams. Their process focuses on rapid, incremental releases and modern technologies to improve efficiency. They provide estimates for building example applications ranging from $10,000-$27,000 within 5 weeks.
UXPin: State of the Union Product Keynote by Marcin Treder
How UXPin unifies design with code in design systems
Recent design system features in UXPin alongside roadmap
Predictions for the future of design tools.
Project management: from Stone Age to DevOps - TopConf Tallinn 2017
The document discusses the evolution of project management from traditional waterfall approaches to more modern DevOps approaches. It describes how project managers historically focused on tasks like planning and reporting but now must adapt to facilitate communication and continuous delivery. The role is transitioning from command and control to that of a delivery enabler who nurtures improvement, coordinates teams, and advocates for DevOps practices.
Get Your Productivity Game On!
Are you struggling with delivering a potentially releasable working product every iteration? Ever wonder what one of biggest reasons we have difficulty getting things done at the individual, team and organizational level are? Do you keep doing something even though you know it reduces your productivity and lowers quality? We are going to run an exercise that highlights one of the major culprits that you have all experienced and continue to experience. The exercise will likely ignite a little fire that will help you become more productive and improve the quality of your work. We will also discuss ways to improve this at the individual, team and organization levels.
Knowing this will help anyone to understand the consequences of not prioritizing and increase their desire to. This will lead to producing faster, higher quality products that should lead to delighted customers.
DevOpsDays Seattle 2017 - Continuous Integration: A bittersweet story
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
Presented at DevOpsDays Seattle 2017.
Continuous Integration: a bittersweet love story
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
5 Level of AI Assistants from the Chatbot Conference
Follow Alex's presentation of the 5 levels of Smart Assistants, where we are now and where we are headed next.
MM072015
Magnetic Moment Issue 99, Quarter 2, 2015: from Supreme Magnets Pte Ltd
99th Issue of Magnetic Moment - please visit www.suprememagnets.com
Copyright & content exclusively created by the Founder of the original Lifton Magnets brand and now the owner, developer & creator of Supreme Magnets. Linking or embedding this presentation without the express authorization of Supreme Magnets is will be subject to prosecution.
Supreme Magnets Pte Ltd : Design, Manufacture and Distribution of innovative magnetic clamping, magnetic lifting and ferrous and non-ferrous impurity separating products and solutions to all kinds of Industrial work holding and ferrous handling and separation challenges.
UX @ agile - myths, legends and the path to success
This document discusses integrating UX practices into Agile development. It addresses three common misconceptions: 1) that Agile projects don't require planning ahead, 2) that Agile doesn't allow time for research and validation, and 3) that Agile means less mistakes. It provides four tips: 1) ensure UX is part of the MVP, 2) define clear requirements for each design task, and 3) focus on effective communication within cross-functional teams. Overall, the document advocates frontloading research in Sprint 0 and design spikes, allowing the UX team to work one sprint ahead of developers to plan effectively in Agile.
User-Centered Design at The Economist
insights and practical steps to improve UX contribution in Agile environment based on my experience of implementing User-Centered Design for The Economist mobile team.
The Agile PMP - Pillar Technology
The document discusses how Agile project management differs from traditional project management. It explains that Agile uses iterative planning with short timeboxes, focuses on delivering working software frequently in small batches, emphasizes individuals/interactions over processes/tools, and values customer collaboration over contract negotiation. The document outlines how Agile manages scope, time, costs, risks, and other factors using techniques like user stories, burndown charts, and frequent inspection and adaptation. It encourages the reader to start implementing Agile practices like iterative planning and daily stand-ups.
More Related Content
What's hot
What Makes an Agile Manager?
The document discusses what makes an agile project manager by outlining that an agile project manager facilitates change through conversations and user-centered practices, leads through servant leadership rather than incentives or punishment, and focuses on adapting to change rather than rigidly following a predetermined plan. The document also briefly defines a project and manager before presenting an "Agile Management Manifesto" with these principles.
Agile myth 1 no plan and no doc
Agile projects do involve planning contrary to a common myth. There are five levels of planning - product vision, roadmap, release plan, iteration plan, and daily plan. While detailed upfront planning is not done, planning occurs continuously. Another myth is that there is no feedback on progress without a plan, but product and sprint backlogs provide burn down visibility. Finally, while the scope may be adjusted, Agile projects have timeboxes and budgets, and documentation is still created when prioritized and not a roadblock to delivery.
Agile UX with Lego
Are you struggling to integrate User Experience techniques with your agile teams? Are any of these patterns familiar?
The UX team works one sprint ahead of the development team.
UX designers spend lots of energy on high fidelity mock-ups which the developers then ignore.
You produce working software each sprint, but recruiting users is time consuming so you only test with users before you release.
There is no time to incorporate changes from user feedback into the sprints before release.
The UX designers and the developers seem to speak a different language.
Developers get annoyed because the UX design work great on iOS, but clashes with Android standards.
If so join us for a fun interactive session where we use Lego to explore how you can overcome challenges like this in your own environment. You’ll work as a team doing both UX design, and development (with Lego), and see how and why these patterns happen, as well as what you can do about them.
This workshop is ideal for people from both the UX world, struggling to understand how to work with developers, and for developers struggling to understand what UX designers are trying to achieve.
PRINCE2 is dead! Long live Agile!
Presentation and workshop, looking at the question "Why still work with PRINCE"?
Part of the Agile Carnival evening, hosted by Agile Holland and LINKIT on February 21st, 2017
GETTING THINGS DONE: WHAT I LEARNED FROM APPLYING GTD
The document discusses lessons learned from applying the Getting Things Done (GTD) productivity system. It warns against making too many lists, trying to connect every action to a project, and putting projects on context lists. It also cautions spending too much time setting up apps instead of getting work done, and stresses that the motivation for using GTD is more important than the tools or system used. The key is to trust the process, avoid overcomplicating it, and stick to the system rather than getting distracted by perfecting the setup.
Scrum Basics
The document describes a typical project where a customer requests an object with 4 legs, 2 ears, 1 trunk, 1 tail, and 2 tusks to be delivered in 6 months. After 6 months, the project team delivers an object meeting all requirements plus a bonus pumpkin. However, the stakeholders were expecting an elephant and are unhappy with the delivered object. The document then discusses adopting agile and scrum practices like collaboration and feedback loops to better meet stakeholder expectations. It provides an overview of scrum roles, events, artifacts, and principles like transparency, inspection, and adaptation.
Guntis Smaukstelis (MightyFingers) @ TechHub Riga Meetup
MightyFingers CEO Guntis Smaukstelis visited TechHub Riga Meetup to tell the story behind the games and their MightyEditor.
First steps towards agility
Agile methodologies encourages teams to embrace the change and react quickly to the market & customer’s demands. Let’s look at how DevOps practices are meant to help teams achieve the agility they want.
Professional Progression - Gavin Elliott [Camp Digital 2018]
Discussing seniority in design, professional and personal development, the skills needed in more senior roles and how to become a great manager and leader.
Why Constraints are Good? A Case Study of an Enterprise Agile Transformation
Agile transformation requires understanding its rules by management. It is hard to leave status quo and change your way of thinking. It is especially hard when the previous model has been in use for many years. A frequent problem with Scrum / Kanban / Lean transformation is to go hard on deep water. Starting tommorow we're doing Scrum. Lack of understanding, communication chaos and rules distortion "just because daily is not working for us". What if take a different approach: slow and prudent? Let say iteratively. Gradually introduce another steps of chosen framework. However the question persists. How to effectively change our conservative organization into agile and constantly changing in response to business needs company?
Skalowanie Agile
The document discusses three case studies of scaling Agile practices to the enterprise level. The first case study describes challenges with a team using only Scrum practices and how adopting additional XP practices like test-driven development and continuous integration helped. The second case study explains problems that arose from multiple teams working on a shared backlog and lack of synchronization; Kanban was introduced to help. The third case study outlines issues with multiple outsourced teams and lack of integration; Kanban, additional roles, and improved coordination helped address these challenges at the portfolio level.
AgileHead - Product Development Services for Startups
This document describes AgileHead, an 18-member consulting group in Bangalore, India that provides product development services using an agile approach. They propose using a small core team of highly experienced developers, testers, and managers rather than large outsourced teams. Their process focuses on rapid, incremental releases and modern technologies to improve efficiency. They provide estimates for building example applications ranging from $10,000-$27,000 within 5 weeks.
UXPin: State of the Union Product Keynote by Marcin Treder
How UXPin unifies design with code in design systems
Recent design system features in UXPin alongside roadmap
Predictions for the future of design tools.
Project management: from Stone Age to DevOps - TopConf Tallinn 2017
The document discusses the evolution of project management from traditional waterfall approaches to more modern DevOps approaches. It describes how project managers historically focused on tasks like planning and reporting but now must adapt to facilitate communication and continuous delivery. The role is transitioning from command and control to that of a delivery enabler who nurtures improvement, coordinates teams, and advocates for DevOps practices.
Get Your Productivity Game On!
Are you struggling with delivering a potentially releasable working product every iteration? Ever wonder what one of biggest reasons we have difficulty getting things done at the individual, team and organizational level are? Do you keep doing something even though you know it reduces your productivity and lowers quality? We are going to run an exercise that highlights one of the major culprits that you have all experienced and continue to experience. The exercise will likely ignite a little fire that will help you become more productive and improve the quality of your work. We will also discuss ways to improve this at the individual, team and organization levels.
Knowing this will help anyone to understand the consequences of not prioritizing and increase their desire to. This will lead to producing faster, higher quality products that should lead to delighted customers.
DevOpsDays Seattle 2017 - Continuous Integration: A bittersweet story
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
Presented at DevOpsDays Seattle 2017.
Continuous Integration: a bittersweet love story
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
5 Level of AI Assistants from the Chatbot Conference
Follow Alex's presentation of the 5 levels of Smart Assistants, where we are now and where we are headed next.
MM072015
Magnetic Moment Issue 99, Quarter 2, 2015: from Supreme Magnets Pte Ltd
99th Issue of Magnetic Moment - please visit www.suprememagnets.com
Copyright & content exclusively created by the Founder of the original Lifton Magnets brand and now the owner, developer & creator of Supreme Magnets. Linking or embedding this presentation without the express authorization of Supreme Magnets is will be subject to prosecution.
Supreme Magnets Pte Ltd : Design, Manufacture and Distribution of innovative magnetic clamping, magnetic lifting and ferrous and non-ferrous impurity separating products and solutions to all kinds of Industrial work holding and ferrous handling and separation challenges.
What's hot (19)
GETTING THINGS DONE: WHAT I LEARNED FROM APPLYING GTD
GETTING THINGS DONE: WHAT I LEARNED FROM APPLYING GTD
Guntis Smaukstelis (MightyFingers) @ TechHub Riga Meetup
Guntis Smaukstelis (MightyFingers) @ TechHub Riga Meetup
Professional Progression - Gavin Elliott [Camp Digital 2018]
Professional Progression - Gavin Elliott [Camp Digital 2018]
Why Constraints are Good? A Case Study of an Enterprise Agile Transformation
Why Constraints are Good? A Case Study of an Enterprise Agile Transformation
AgileHead - Product Development Services for Startups
AgileHead - Product Development Services for Startups
UXPin: State of the Union Product Keynote by Marcin Treder
UXPin: State of the Union Product Keynote by Marcin Treder
Project management: from Stone Age to DevOps - TopConf Tallinn 2017
Project management: from Stone Age to DevOps - TopConf Tallinn 2017
DevOpsDays Seattle 2017 - Continuous Integration: A bittersweet story
DevOpsDays Seattle 2017 - Continuous Integration: A bittersweet story
5 Level of AI Assistants from the Chatbot Conference
5 Level of AI Assistants from the Chatbot Conference
Similar to How we make agile work
UX @ agile - myths, legends and the path to success
This document discusses integrating UX practices into Agile development. It addresses three common misconceptions: 1) that Agile projects don't require planning ahead, 2) that Agile doesn't allow time for research and validation, and 3) that Agile means less mistakes. It provides four tips: 1) ensure UX is part of the MVP, 2) define clear requirements for each design task, and 3) focus on effective communication within cross-functional teams. Overall, the document advocates frontloading research in Sprint 0 and design spikes, allowing the UX team to work one sprint ahead of developers to plan effectively in Agile.
User-Centered Design at The Economist
insights and practical steps to improve UX contribution in Agile environment based on my experience of implementing User-Centered Design for The Economist mobile team.
The Agile PMP - Pillar Technology
The document discusses how Agile project management differs from traditional project management. It explains that Agile uses iterative planning with short timeboxes, focuses on delivering working software frequently in small batches, emphasizes individuals/interactions over processes/tools, and values customer collaboration over contract negotiation. The document outlines how Agile manages scope, time, costs, risks, and other factors using techniques like user stories, burndown charts, and frequent inspection and adaptation. It encourages the reader to start implementing Agile practices like iterative planning and daily stand-ups.
TDD in Agile
The document discusses test driven development (TDD) in an agile environment. It covers topics like the agile manifesto, evolutionary design, TDD steps and philosophy, myths about TDD, test qualities, benefits and costs of TDD, plugins and language support. The author shares their experience with TDD, noting that it improved code quality and refactoring while requiring support from leads to be effective long-term. Acceptance TDD is recommended to ensure shared understanding of what is being built.
Just Married: User Centered Design and Agile
User Centred Design (UCD) and Agile Development are two of the most exciting and productive Methods to achieve high quality appication both desired by the customers and loved by the users. UCD and Agile Development are though often said to be impossible to combine and that despite their great advantages any attempt would most certainly lead to disaster.
This talk picks up the main points of both methods, shows the key issues and tries to offer a pragmatic approach on how to successfully combine User Centered Design and Agile Development.
Scrum 101+
This document provides an overview of Scrum, an agile framework for project management. It defines Scrum roles like Product Owner, Scrum Master, and Development Team. It describes Scrum events like Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. It also outlines Scrum artifacts like the Product Backlog, Sprint Backlog, and Product Increment. The goal is to help teams address complex problems and deliver valuable products through short development cycles with transparency, inspection, and adaptation.
Real world experience from Microsoft - Deniz Ercoskun
Microsoft developer division has implemented SCRUM while developing Visual Studio 2012, and TFS 2012. In this talk we will cover information on this implementation. You will learn about why Microsoft has decided to implement SCRUM, best practices that was helpful for us. How implementing SCRUM has changed our cadence and product delivery cycle. The content will be our developer division SCRUM journey. We are not pure SCRUM put at future leavel we are. I will also discuss which part of our process is SCRUm which part still is not.
Agile SharePoint Development With Scrum
Provide an introduction to Agile development using Scrum and discuss how the iterative approach to development helps the customer to get the solution they want. Look at how this approach works when applied to SharePoint projects, how it helps leverage more of the core platform and focuses effort on the biggest value areas. We will look at the challenges this brings to your development team by doing early integration, dealing with upgrades and changes and understand how addressing the hard things early is the right approach. We will also discuss how Scrum gives visibility of the project and brings both good and bad news. How getting customer engagement is the primary challenge and how the flexible approach is often at odds with the way work is contracted.
Agile Methodology and Scrum Framework
The document provides an overview of Agile methodology and Scrum framework for project management. It discusses that Agile focuses on adaptability, collaboration, and frequent delivery of working software. Scrum is the most commonly used Agile framework and involves sprints, daily stand-ups, sprint planning and reviews to manage projects. The roles in Scrum include the Product Owner, Scrum Master, and Development Team who work together using artifacts like the Product Backlog, Sprint Backlog and delivered Product Increment.
Our Journey to Agile in the Microsoft Developer Division
This is the story about the Microsoft Developer Division and their two-year journey to agile—from shipping every three years to shipping every three weeks. In the old days, long stabilization phases were part of its DNA. Managers were rewarded for micromanagement. Commitments were made months in advance. Maintaining the appearance of meeting commitments was valued over transparency. Gregg Boer shares how this organization within Microsoft transitioned to one that values agile principles—controlling technical debt, enabling teams, eliminating bogus commitments, and rewarding transparency. When applying agile to such a large, traditional organization, the key to success is allowing autonomy at the team level, while ensuring alignment with the organization. Gregg shares successes as well as colossal failures. Learn how management sets direction while teams own their own backlog, how communication up and down can be transparent and healthy, and other lessons on their journey to agile.
Ran Liron
כיצד מסתדרת עבודה על אפיון ממשק במתודולוגיה מוכוונת משתמש עם הקצב המהיר של עבודה במתודולוגיית Agile? האם ניתן לעשות UX טוב ב- Agile ? איך מתמודדים עם השילוב של Agile ו-UX בארגונים גדולים?
בהרצאה קצרה זו אפריך כמה מהמיתוסים הנפוצים בנוגע לעבודה על UX בארגונים גדולים ככלל ועבודה ב-Agile בפרט, ואנסה להציע מספר טיפים כיצד להתמודד עם האתגר הלא פשוט של אפיון ממשקים למערכות מורכבות בסביבת Agile.
Andriy bahlay
This document summarizes an agile transformation journey at a product company. It describes the current functional structure and process, which led to issues with efficiency, quality, transparency and expectations. An assessment was conducted which recommended transitioning to a cross-functional agile model with value streams aligned to products. A proposed solution included agile training, establishing roles and teams, and implementing ceremonies and practices. Initial results showed improvements in productivity, quality, time to market and visibility. Strengthening the product owner function and embedding changes into corporate culture were also recommended.
Introduction to agile and scrum
1. The document provides an overview of practical scrum concepts including lean thinking, agile principles, scrum roles and ceremonies.
2. It discusses the roles of the product owner, scrum master and team in scrum and describes the four main scrum ceremonies: sprint planning, daily scrum, sprint review, and retrospective.
3. Key aspects of each ceremony are outlined such as their purpose, participants, and goals to continuously deliver working software and improve the process.
UX @ Agile - Myths, Legends and the path to success
This document discusses integrating UX practices into large Agile organizations. It dispels common misconceptions that UX planning and research are not needed in Agile. Instead, it advocates for a Sprint 0 to define vision, recurring design spikes, and continuous research and validation. It also emphasizes the importance of clear definitions of done and effective communication between teams. The overall message is that Agile requires adapting UX practices, not abandoning them, in order to deliver viable, usable products through a focus on the user experience.
Agile Methodology
The document provides an overview of agile methodology and scrum framework. It begins with a short history of traditional waterfall software development processes and their limitations. It then introduces the agile manifesto and values, as well as the 12 agile principles. A key part of agile is iterative development with short sprints. Scrum is discussed as one of the major agile frameworks, outlining its ceremonies like sprint planning, daily standups, and retrospectives. Scrum roles of product owner, scrum master, and self-organizing team are also summarized.
Speed up Continuous Delivery with BigData Analytics
Use Spark, Apache Flume and ElasticSearch-Kibana to unleash the power of your Code Review and Continuous Delivery Pipeline logs. Jenkins and Gerrit Code Review are the sources of your Analytics KPI dashboards.
The Guide to Agile UX Design Sprint Playbook
Alex Gamble is a product designer at Price Waterhouse Coopers New Zealand. He has helped a variety of businesses, from small start-ups to big corporates, develop user-centred products. Alex’s goal is to bring forward a lean product revolution.
Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...
This document discusses testing challenges for a software company that develops a video management system product with frequent changes to requirements, priorities, and hardware platforms. The key challenges include long-term planning difficulties due to constantly changing priorities, limited testing resources compared to the size of the product and number of developers, and setup time for complex integration tests. It provides recommendations for achieving high team effectiveness through minimizing interruptions, focusing testing on individual stories, and establishing trust in story-level testing to reduce risks for major releases.
How to Plan for Hyper Growth Success by Slack Software Engineer
The document summarizes a presentation given by a Slack software engineer on how to plan for success during periods of hyper growth. It discusses common challenges startups face like rapid scaling, communication issues, and lack of experience. It provides a case study of challenges Slack faced with an MDM project and lessons learned. The key messages are to provide strong leadership through documentation like a living product specification, use concise user stories, and over-organize to avoid issues as a company scales rapidly.
Agile and Design: creating and implementing products (in Italy) is possible
The wiseman says: "A company specialized in IT consultancy cannot make products."
If you decide to break this taboo, the road is only one: understanding how that product can be realized and working hard to make it.
This is the story of Indyco, a tool born merging an agile dev team and a lean design team. Teams that didn't know each other before. And they made Indyco real in 6 months.
We will share the simple but powerful principles that lead us up to the go-live.
Now we are measuring and collecting data for next step.
These slides have been presented at Better Software 2014.
Similar to How we make agile work (20)
UX @ agile - myths, legends and the path to success
UX @ agile - myths, legends and the path to success
Real world experience from Microsoft - Deniz Ercoskun
Real world experience from Microsoft - Deniz Ercoskun
Our Journey to Agile in the Microsoft Developer Division
Our Journey to Agile in the Microsoft Developer Division
UX @ Agile - Myths, Legends and the path to success
UX @ Agile - Myths, Legends and the path to success
Speed up Continuous Delivery with BigData Analytics
Speed up Continuous Delivery with BigData Analytics
Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...
Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...
How to Plan for Hyper Growth Success by Slack Software Engineer
How to Plan for Hyper Growth Success by Slack Software Engineer
Agile and Design: creating and implementing products (in Italy) is possible
Agile and Design: creating and implementing products (in Italy) is possible
Recently uploaded
How to write a program in any programming language
How to write a program in any programming language
LORRAINE ANDREI_LEQUIGAN_HOW TO USE ZOOM
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
https://2024.springio.net/sessions/automated-software-refactoring-with-openrewrite-and-generative-ai/
E-commerce Application Development Company.pdf
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
What is Master Data Management by PiLog Group
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
WhatsApp offers simple, reliable, and private messaging and calling services for free worldwide. With end-to-end encryption, your personal messages and calls are secure, ensuring only you and the recipient can access them. Enjoy voice and video calls to stay connected with loved ones or colleagues. Express yourself using stickers, GIFs, or by sharing moments on Status. WhatsApp Business enables global customer outreach, facilitating sales growth and relationship building through showcasing products and services. Stay connected effortlessly with group chats for planning outings with friends or staying updated on family conversations.
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
OpenMetadata Community Meeting - 5th June 2024
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Presentation from Ghazal Aakel and Eric Jochum at the GSD Community Stage Meetup on June 6th, 2024
E-commerce Development Services- Hornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Graspan: A Big Data System for Big Code Analysis
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
原版定制美国纽约州立大学奥尔巴尼分校毕业证学位证书原版一模一样
原版一模一样【微信：741003700 】【美国纽约州立大学奥尔巴尼分校毕业证学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Recently uploaded (20)
How to write a program in any programming language
How to write a program in any programming language
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
How we make agile work
- 1. Howwe makeagilework Sort of Yael Keren | June 2017
- 2. Who am I? Yael Keren Head of UX at Clicktale Mentor at GoogleTLV Campus
- 3. 3 Clicktale
- 4. Clicktale
- 5. 5 AGILEvs UX
- 6. 6 AGILE+ UX
- 8. 8
- 9. Sprint 1 Sprint 2 Sprint 3 Sprint 4 9Confidential Sprint 1 Sprint 2 Sprint 3 week week Sprints week week week week Sprint 0 3-9 weeks UX / UI
- 10. Why is Agile challenging for UX
- 12. 12Confidential week week Sprints week week week week Sprint 1 Sprint 3 Sprint 4Sprint 2 week week Sprint 0 week week
- 13. 13Confidential week week Sprints Sprint Sprint 3Sprint 2 Validate Sprint 1 Design Sprint 3 Support + QA Sprint 2
- 14. Sprints Challenge #1 What we do…
- 16. 16Confidential Sprint 1 Sprint 2 Sprint 3 week week SAFe (Scaled Agile Framework) methodology week week week week week Sprint 4 Sprint 5 week week week
- 17. 17Confidential Sprint 1 Sprint 2 Sprint 3 week week SAFe (Scaled Agile Framework) methodology week week week week Planning week Product Increment 1 Sprint 1 Spr week week week Product Increment 2 Design Product Increment 2 Validate + QA Product increment 0
- 18. 18
- 19. 19
- 20. UX is part of QA
- 23. Didi - Developer: “If the code works – no need to fix it” Gili - Product Manager: “Let’s add another feature instead!”
- 24. What we do… Fixing issues Challenge #2
- 25. 25Confidential Sprint 1 Sprint 2 Sprint 3 week week 2 days design bugs week week week week Sprint 0 3-9 weeks
- 27. Negotiation Give me $100 and I will do it in a day…
- 29. How will the developer understand exactly what you meant? How do you know he understood?
- 30. 30Confidential Actual - Date pickerPlan - Date range picker
- 31. What we do… Sync Challenge #3
- 32. Feature Kickoff
- 34. 34 Confid I freeze here DEV DEV DEV QA DEV Sit amongst the developers PM
- 35. 35 Confid Hang designs on the wall
- 36. 36
- 37. Summary
- 38. #1 - Sprints • Test while planning • Product Increments – 7 weeks • UX is part of QA TAKEAWAYS #3 - Sync • Feature kick-off • Attend daily stand-up • Sit with developers • Hang designs on the wall • Go intoTFS #2 - Fixing issues • 2 days UI/UX fixes in a sprint • Iteration mindset • Negotiation
- 39. Agile is all about communication The most important thing…
Editor's Notes
- I
- No time for documentation Dev needs to know exactly what you meant
- Sit next to dev