Agile is an iterative approach to project management and software development that focuses on continuous improvement and delivering working software frequently. The key aspects of agile include iterative development with 2 week sprints, daily standups to track progress, sprint reviews to demo completed work, retrospectives to improve, and self-organizing cross-functional teams. Agile aims to deliver value to customers faster through collaboration, transparency, and adapting to changes in priorities.
This document discusses key principles of agile project management. It begins by explaining why agile is gaining popularity, namely that it allows for flexibility and faster delivery of results through frequent small deliveries and continuous customer feedback. It then presents the agile manifesto which prioritizes customer satisfaction, welcoming changing requirements, frequent delivery of working software through short iterations, close business/developer collaboration, self-organizing teams, face-to-face communication, measuring progress through working software, sustainability, technical excellence, simplicity, and self-reflection. The document suggests considering environment, team, ceremonies, tools, and techniques to make projects more agile and stresses the importance of self-organizing teams, time-boxing requirements, people
12 agile principles
***About Magestore***
Magestore là công ty cung cấp giải pháp phần mềm cho các doanh nghiệp bán lẻ. Đối tượng khách hàng chủ yếu là các chuỗi bán lẻ của Mỹ và Châu u. Giải pháp của Magestore được xây dựng based trên nền tảng Magento.
Các bạn có thể xem thêm thông tin về sản phẩm của Magestore tại: https://www.magestore.com
***About Magestore Culture***
Các bạn có thể tìm hiểu thêm nhiều thông tin nữa về con người và văn hóa của Magestore tại website https://insights.magestore.com
***Các vị trí mà Magestore đang tuyển dụng***
Magestore là một công ty phát triển sản phẩm nên cần đội ngũ nhân sự chất lượng cao ở nhiều vị trí như:
#Full-stack Developer, Global Retail Solution #Business Consultant #Digital Marketing Executive #AI Engineer
Các bạn có thể tham khảo thông tin cụ thể về các vị trí tuyển dụng tại link sau:
https://insights.magestore.com/nextgen
Practical roadmap for value driven product owner excellence
The product owner is vital for the effective transformation of the organization. This presentation provides a practical roadmap to product owner excellence. We discuss BABOK framework and a business analysis approach for product owners - defining key concepts and methods for success. We touch on:
The Business Analyst, Agile - the manifesto, and the Product Owner;
PO and BA differences and similarities;
Three key differentiators for Product Owner excellence.
Professional Product Owners - pivotal in leading organization growth
What Is Gaming Product Management Like by Zynga Product ManagerProduct School
Product Managers aren’t new to the gaming industry, and every day more and more gaming companies are realizing the significance of employing Product Managers to drive product strategy and business decisions. This event, was an overview on Product Management in Gaming and learn how gaming Product Managers are merging Art, Business and Technology to create value in this exciting and fast-paced industry.
The document introduces empirical process control and agile development methodologies. Projects are divided into sprints with meetings at the end of each sprint to assess progress and plan next steps. A Product Owner communicates requirements and a Scrum Master helps the team. Teams of 7 cross-functional members work to complete sprint goals. Benefits include saving time and money, and easier adaptation to changes. Committed team members are needed for success, while large teams or projects may not be suitable and quality management can be difficult without proper testing.
The document outlines the project program process from start to finish. It discusses choosing a project, creating a draft that involves developing, running, adjusting and finalizing the project. This includes developing the intended end result, getting feedback, and teaching the project out to leadership. Finally, it discusses rolling out the project by getting ready for implementation, teaching associates, and integrating it into the work environment. The overall process helps address annual problems, improve efficiency, and continue the organization's mission through learning opportunities and employee contributions.
How to Transition from Engineering to Product by LinkedIn's PMProduct School
Product managers are sometimes reviled and other times revered. We went over the differences between the roles and what to expect. We discussed how to shift your thinking and start working like a product manager, and how to shift your mindset and learn to think about "why" instead of just "what".
This document discusses key principles of agile project management. It begins by explaining why agile is gaining popularity, namely that it allows for flexibility and faster delivery of results through frequent small deliveries and continuous customer feedback. It then presents the agile manifesto which prioritizes customer satisfaction, welcoming changing requirements, frequent delivery of working software through short iterations, close business/developer collaboration, self-organizing teams, face-to-face communication, measuring progress through working software, sustainability, technical excellence, simplicity, and self-reflection. The document suggests considering environment, team, ceremonies, tools, and techniques to make projects more agile and stresses the importance of self-organizing teams, time-boxing requirements, people
12 agile principles
***About Magestore***
Magestore là công ty cung cấp giải pháp phần mềm cho các doanh nghiệp bán lẻ. Đối tượng khách hàng chủ yếu là các chuỗi bán lẻ của Mỹ và Châu u. Giải pháp của Magestore được xây dựng based trên nền tảng Magento.
Các bạn có thể xem thêm thông tin về sản phẩm của Magestore tại: https://www.magestore.com
***About Magestore Culture***
Các bạn có thể tìm hiểu thêm nhiều thông tin nữa về con người và văn hóa của Magestore tại website https://insights.magestore.com
***Các vị trí mà Magestore đang tuyển dụng***
Magestore là một công ty phát triển sản phẩm nên cần đội ngũ nhân sự chất lượng cao ở nhiều vị trí như:
#Full-stack Developer, Global Retail Solution #Business Consultant #Digital Marketing Executive #AI Engineer
Các bạn có thể tham khảo thông tin cụ thể về các vị trí tuyển dụng tại link sau:
https://insights.magestore.com/nextgen
Practical roadmap for value driven product owner excellence
The product owner is vital for the effective transformation of the organization. This presentation provides a practical roadmap to product owner excellence. We discuss BABOK framework and a business analysis approach for product owners - defining key concepts and methods for success. We touch on:
The Business Analyst, Agile - the manifesto, and the Product Owner;
PO and BA differences and similarities;
Three key differentiators for Product Owner excellence.
Professional Product Owners - pivotal in leading organization growth
What Is Gaming Product Management Like by Zynga Product ManagerProduct School
Product Managers aren’t new to the gaming industry, and every day more and more gaming companies are realizing the significance of employing Product Managers to drive product strategy and business decisions. This event, was an overview on Product Management in Gaming and learn how gaming Product Managers are merging Art, Business and Technology to create value in this exciting and fast-paced industry.
The document introduces empirical process control and agile development methodologies. Projects are divided into sprints with meetings at the end of each sprint to assess progress and plan next steps. A Product Owner communicates requirements and a Scrum Master helps the team. Teams of 7 cross-functional members work to complete sprint goals. Benefits include saving time and money, and easier adaptation to changes. Committed team members are needed for success, while large teams or projects may not be suitable and quality management can be difficult without proper testing.
The document outlines the project program process from start to finish. It discusses choosing a project, creating a draft that involves developing, running, adjusting and finalizing the project. This includes developing the intended end result, getting feedback, and teaching the project out to leadership. Finally, it discusses rolling out the project by getting ready for implementation, teaching associates, and integrating it into the work environment. The overall process helps address annual problems, improve efficiency, and continue the organization's mission through learning opportunities and employee contributions.
How to Transition from Engineering to Product by LinkedIn's PMProduct School
Product managers are sometimes reviled and other times revered. We went over the differences between the roles and what to expect. We discussed how to shift your thinking and start working like a product manager, and how to shift your mindset and learn to think about "why" instead of just "what".
The document discusses the technologies and programs used to create a magazine project. It describes using Adobe Photoshop to edit images, including adjusting brightness, lighting, and cropping. Adobe InDesign was used to layout the magazine pages. Through this process, the author learned new skills with these programs and how to successfully use various tools. They have gained more knowledge and confidence in using technology after overcoming initial uncertainties in bringing their design ideas to life through digital means.
Aligning Product Strategy with Customer Feature RequestsProductPlan
We’ve all been on customer calls where we’re asked for a feature that just does not align with our product strategy. It’s not a problem if one request is an outlier, but how should you handle recurring requests from your customers that do not align with your product strategy? In this webinar, product management veterans share real examples of feature requests that did not naturally fit with the company’s vision.
The document introduces LaSoft, a software development company founded in 2014 with 70 employees across 7 teams. LaSoft has successfully delivered 40 web projects for customers in the US, Europe, UK and Australia. The document outlines LaSoft's 5-stage process for cost-efficient project implementation, which includes defining the product vision and scope, designing the UI/UX, planning delivery through incremental releases, building the product incrementally, and delivering the final product. It emphasizes investing more time upfront in definition and design to efficiently deliver complex projects.
Teameze is a perfect, robust, lightweight, superfast web application to fulfill all your Team Collaboration, Project Management and CRM needs. https://teameze.com/
Succeeding with Agile in the Federal Government: A Coach's PerspectiveEd Seidewitz
The document summarizes key principles from the Agile Manifesto and provides advice for implementing Agile practices in government organizations. It discusses embracing individuals and interactions over processes; delivering working software over documentation; prioritizing customer collaboration over contract negotiation; and responding to change rather than rigidly following a plan. The document offers dos and don'ts for applying these Agile concepts when working with government agencies and contractors.
This document provides a template for evaluating completed webinars. It outlines 8 key areas to assess: overall assessment, scope management, deliverables quality, accomplishments, lessons learned, opportunities for improvement, future considerations, and best practices. The template includes questions for each area and spaces to document lessons learned, recommendations, and approval signatures.
I learned how to use InDesign to create a magazine and supporting documents without formal training, which helped me learn to take initiative. I used photo editing software to adjust lighting and clarity in images to make them look more professional for the target audience. I created presentations and posted my evaluation online using PowerPoint, SlideShare and Blogger to make my work more accessible and convenient for marking.
How to Manage Multiple Projects Effectively in 2021TaskOPad
Managing multiple projects at once is a #challenging task for every enterprise. Here are the top strategies to manage multiple projects at a workplace. Let's connect to TaskOPad to discuss more on project management software.
The product owner and the scrum team. Can one person do this at scale?Derek Huether
Presented at IIBA Baltimore on March 11, 2014. The last 10 years of Agile have focused on the team. The next 10 years of Agile will focus on the enterprise. That said, should the Product Owner continue to be a single person or does it need to evolve as well? Let's cover the basics and then see how LeadingAgile has been successful at leveraging the Product Owner role at scale.
Outcomes vs Outputs: How Outcome Driven Development Planning Changes EverythingChris Reynolds
As freelancers, developers and project managers working on a project, it’s easy to get blinded by outcomes. Tasks on a project are often defined by the specific thing that we expect to build or present to the client or customer. But what if our assumptions are wrong? Or the scope changes along the way? What if there was an easier way to produce a desirable, user-friendly end-product without specifically defining what that end-product is? (Spoiler: There is!) This talk will discuss how to shift your focus from outputs to outcomes and how that little mental shift, changes everything. Really!
This document outlines 5 key steps to establishing a smooth workflow using an agile approach: 1) Establish the workflow by mapping out major processes and stages, 2) Define policies for each stage, 3) Visualize work by adding cards for features and tasks, 4) Define work-in-progress limits for stages, and 5) Continuously improve by reviewing metrics and looking for areas of improvement. Following these steps helps minimize bottlenecks, focus work, and continuously refine the workflow.
This document discusses the app development process using sprints. It explains that sprints are two-week iterations where a team commits to completing tickets that have well-defined acceptance criteria. During a sprint, developers work on tickets, which may be broken into subtasks, and upon completion the changes are tested against the acceptance criteria before being deployed. Bugs are treated as tickets and time is allocated in each sprint for developers to address any issues found during testing.
Introduction to Agile Software Development - Eric Wu - MBAX6360 New Product D...Eric Wu
This document discusses agile software development and is presented by Eric Wu, co-founder of Bracket Labs. It outlines some of the key problems with traditional waterfall software development processes, such as unpredictable requirements and costs. It then introduces agile development principles from the Agile Manifesto, including an emphasis on working software, customer collaboration, and responding to change. Finally, it provides an example of an agile process incorporating sprints, demonstrations, retrospectives and stand-up meetings, and notes how agile practices have evolved and expanded beyond just software development over the past 10 years.
Capability Building is one of the top most strategic priority for an organization. Even after taking many measures, the real benefit is never realized. With this Presentation a small effort is made to analyze the effectiveness of the different measures taken by the Organizations in building capabilities. The various problems are discussed along with the Vision, Principles and frameworks to resolve the same.
What Are the Product Management Success Skills by Walmart Product ManagerProduct School
We’re all familiar with Product Managers, but you may have also heard of other “Product Management” roles - program manager, project manager, or even product marketer. Just what do all of these other roles do?
Susan Song, Product Manager at Walmart shared her insights on the responsibilities for each of these roles, having worked with all of them in her career as a Product Manager. She also discussed why if you’re not starting out as a Product Manager, it’s okay - you can still leverage your “Product Management” skills into your next product job.
Meetings should be collaborative experiences that help teams get things done. But in reality, the average meeting is delayed by more than 10 minutes due to technology glitches. We’ve listed the tell-tale warning signs of lackluster meetings along with smart tips to simplify collaboration with video so your team can keep moving forward.
A presentation on Agile Methodology for Project ManagersAdeolu Adeleye
A Presentation on Solutions for Project Managers such as useful tools that can help you in the process of human resource allocation, as well as an example of Scrum framework to the rescue.
La Unión Europea ha acordado un embargo petrolero contra Rusia en respuesta a la invasión de Ucrania. El embargo prohibirá la mayoría de las importaciones de petróleo ruso a la UE y se implementará de manera gradual durante los próximos seis meses. Algunos países de la UE aún dependen en gran medida del petróleo ruso y buscarán exenciones al embargo.
El BMX es una modalidad acrobática del ciclismo cuyo origen está en California, donde los niños usaban bicicletas para imitar carreras de motocross. Los corredores de BMX realizan trucos y acrobacias aéreas en pistas diseñadas especialmente para esta disciplina.
The document discusses the technologies and programs used to create a magazine project. It describes using Adobe Photoshop to edit images, including adjusting brightness, lighting, and cropping. Adobe InDesign was used to layout the magazine pages. Through this process, the author learned new skills with these programs and how to successfully use various tools. They have gained more knowledge and confidence in using technology after overcoming initial uncertainties in bringing their design ideas to life through digital means.
Aligning Product Strategy with Customer Feature RequestsProductPlan
We’ve all been on customer calls where we’re asked for a feature that just does not align with our product strategy. It’s not a problem if one request is an outlier, but how should you handle recurring requests from your customers that do not align with your product strategy? In this webinar, product management veterans share real examples of feature requests that did not naturally fit with the company’s vision.
The document introduces LaSoft, a software development company founded in 2014 with 70 employees across 7 teams. LaSoft has successfully delivered 40 web projects for customers in the US, Europe, UK and Australia. The document outlines LaSoft's 5-stage process for cost-efficient project implementation, which includes defining the product vision and scope, designing the UI/UX, planning delivery through incremental releases, building the product incrementally, and delivering the final product. It emphasizes investing more time upfront in definition and design to efficiently deliver complex projects.
Teameze is a perfect, robust, lightweight, superfast web application to fulfill all your Team Collaboration, Project Management and CRM needs. https://teameze.com/
Succeeding with Agile in the Federal Government: A Coach's PerspectiveEd Seidewitz
The document summarizes key principles from the Agile Manifesto and provides advice for implementing Agile practices in government organizations. It discusses embracing individuals and interactions over processes; delivering working software over documentation; prioritizing customer collaboration over contract negotiation; and responding to change rather than rigidly following a plan. The document offers dos and don'ts for applying these Agile concepts when working with government agencies and contractors.
This document provides a template for evaluating completed webinars. It outlines 8 key areas to assess: overall assessment, scope management, deliverables quality, accomplishments, lessons learned, opportunities for improvement, future considerations, and best practices. The template includes questions for each area and spaces to document lessons learned, recommendations, and approval signatures.
I learned how to use InDesign to create a magazine and supporting documents without formal training, which helped me learn to take initiative. I used photo editing software to adjust lighting and clarity in images to make them look more professional for the target audience. I created presentations and posted my evaluation online using PowerPoint, SlideShare and Blogger to make my work more accessible and convenient for marking.
How to Manage Multiple Projects Effectively in 2021TaskOPad
Managing multiple projects at once is a #challenging task for every enterprise. Here are the top strategies to manage multiple projects at a workplace. Let's connect to TaskOPad to discuss more on project management software.
The product owner and the scrum team. Can one person do this at scale?Derek Huether
Presented at IIBA Baltimore on March 11, 2014. The last 10 years of Agile have focused on the team. The next 10 years of Agile will focus on the enterprise. That said, should the Product Owner continue to be a single person or does it need to evolve as well? Let's cover the basics and then see how LeadingAgile has been successful at leveraging the Product Owner role at scale.
Outcomes vs Outputs: How Outcome Driven Development Planning Changes EverythingChris Reynolds
As freelancers, developers and project managers working on a project, it’s easy to get blinded by outcomes. Tasks on a project are often defined by the specific thing that we expect to build or present to the client or customer. But what if our assumptions are wrong? Or the scope changes along the way? What if there was an easier way to produce a desirable, user-friendly end-product without specifically defining what that end-product is? (Spoiler: There is!) This talk will discuss how to shift your focus from outputs to outcomes and how that little mental shift, changes everything. Really!
This document outlines 5 key steps to establishing a smooth workflow using an agile approach: 1) Establish the workflow by mapping out major processes and stages, 2) Define policies for each stage, 3) Visualize work by adding cards for features and tasks, 4) Define work-in-progress limits for stages, and 5) Continuously improve by reviewing metrics and looking for areas of improvement. Following these steps helps minimize bottlenecks, focus work, and continuously refine the workflow.
This document discusses the app development process using sprints. It explains that sprints are two-week iterations where a team commits to completing tickets that have well-defined acceptance criteria. During a sprint, developers work on tickets, which may be broken into subtasks, and upon completion the changes are tested against the acceptance criteria before being deployed. Bugs are treated as tickets and time is allocated in each sprint for developers to address any issues found during testing.
Introduction to Agile Software Development - Eric Wu - MBAX6360 New Product D...Eric Wu
This document discusses agile software development and is presented by Eric Wu, co-founder of Bracket Labs. It outlines some of the key problems with traditional waterfall software development processes, such as unpredictable requirements and costs. It then introduces agile development principles from the Agile Manifesto, including an emphasis on working software, customer collaboration, and responding to change. Finally, it provides an example of an agile process incorporating sprints, demonstrations, retrospectives and stand-up meetings, and notes how agile practices have evolved and expanded beyond just software development over the past 10 years.
Capability Building is one of the top most strategic priority for an organization. Even after taking many measures, the real benefit is never realized. With this Presentation a small effort is made to analyze the effectiveness of the different measures taken by the Organizations in building capabilities. The various problems are discussed along with the Vision, Principles and frameworks to resolve the same.
What Are the Product Management Success Skills by Walmart Product ManagerProduct School
We’re all familiar with Product Managers, but you may have also heard of other “Product Management” roles - program manager, project manager, or even product marketer. Just what do all of these other roles do?
Susan Song, Product Manager at Walmart shared her insights on the responsibilities for each of these roles, having worked with all of them in her career as a Product Manager. She also discussed why if you’re not starting out as a Product Manager, it’s okay - you can still leverage your “Product Management” skills into your next product job.
Meetings should be collaborative experiences that help teams get things done. But in reality, the average meeting is delayed by more than 10 minutes due to technology glitches. We’ve listed the tell-tale warning signs of lackluster meetings along with smart tips to simplify collaboration with video so your team can keep moving forward.
A presentation on Agile Methodology for Project ManagersAdeolu Adeleye
A Presentation on Solutions for Project Managers such as useful tools that can help you in the process of human resource allocation, as well as an example of Scrum framework to the rescue.
La Unión Europea ha acordado un embargo petrolero contra Rusia en respuesta a la invasión de Ucrania. El embargo prohibirá la mayoría de las importaciones de petróleo ruso a la UE y se implementará de manera gradual durante los próximos seis meses. Algunos países de la UE aún dependen en gran medida del petróleo ruso y buscarán exenciones al embargo.
El BMX es una modalidad acrobática del ciclismo cuyo origen está en California, donde los niños usaban bicicletas para imitar carreras de motocross. Los corredores de BMX realizan trucos y acrobacias aéreas en pistas diseñadas especialmente para esta disciplina.
Kite Hill Senior Design Final Presentation Fall 2015Ashleigh Hough
This document provides a summary of a stormwater management design project for Kite Hill at Clemson University. It introduces the problem of stormwater runoff from Kite Hill damaging Hunnicutt Creek. It then outlines the project goals to treat stormwater pollutants and reduce peak flows. Several design elements are proposed including hillside terracing, vegetative cover, parking lot medians and flow diversion techniques. Budgets are provided for the different design elements and comparisons are made between options. The document aims to address the stormwater issues while considering constraints, sustainability and aesthetics.
Public relations professionals work to portray their artist clients in a positive light to the media to appeal to investors and make more money for the artist and record company. They must maintain a good reputation by performing well for clients in order to continue receiving business. Researching background information on clients allows PRs insight into target markets and trends to best promote their clients.
Hoe verdeel je je marketing budget optimaal over alle kanalen heen? (on- &offline).
En hoeveel additionele omzet/orders levert dit op? Bepaal je ultimate sweetspot aan de hand van conversie attributie en predictive modeling met Media OptimiSR van Searchresult!
El documento describe las lesiones del aparato locomotor, incluyendo lesiones óseas, musculares y de articulaciones. Explica tipos comunes de lesiones como roturas, esguinces y luxaciones. También ofrece consejos para prevenir lesiones como calentar antes del ejercicio y tratar lesiones leves con estiramientos.
Dream Big and Aim High in the Face of FearEmilie Aries
This document provides information about the #FierceFall Challenge, a free 10-week goal achievement program running through Thanksgiving, and shares tips for how to "Rock Your Life" in 5 key areas: knowing your brand, values, purpose, goals, and yourself. It encourages the reader to join the challenge at www.bossedup.org/fiercefall and provides contact information for further support.
Un selector de velocidades es una región del espacio donde un campo magnético y eléctrico ortogonales contrarrestan sus fuerzas sobre partículas, permitiendo que solo aquellas con una velocidad determinada crucen sin desviarse mientras que otras se desvían. Afecta a protones y electrones de forma similar pero con fuerzas eléctricas y magnéticas de sentido opuesto.
Kite Hill Senior Design Final Presentation Fall 2015Ashleigh Hough
This document provides a summary of a stormwater management design project for Kite Hill at Clemson University. It introduces the problem of stormwater runoff from Kite Hill damaging Hunnicutt Creek. It then discusses the project goals of reducing erosion, runoff volume, and peak flows. Several design elements are proposed including terracing Kite Hill, adding vegetative cover, and parking lot BMPs. Budget estimates and comparisons of the different design options are provided. The document aims to develop a stormwater management system for Kite Hill that meets regulatory requirements and project constraints in a sustainable and cost-effective manner.
The document describes the narrator's daily routine. They wake up early to exercise, have breakfast, and do chores around their flat like tidying, ironing, and helping others. After free time, they go to university, do homework, walk their dog, have supper, finish more homework, brush their teeth, and go to bed. On holidays they still do housework but focus on getting enough sleep. They cook meals alone since their grandmother shops during dinner. Their schedule keeps them busy throughout the day.
La uncinariasis es una infestación causada por los nematodos Ancylostoma duodenale o Necator americanus. Se caracteriza por producir anemia debido a la pérdida de sangre causada por los gusanos adultos que se anclan en el intestino delgado. Los síntomas incluyen dolor abdominal, diarrea y anemia. El diagnóstico se realiza mediante el examen de huevos en las heces y el tratamiento consiste en medicamentos antiparasitarios como albendazol.
El documento resume la anatomía y fisiología del sistema cardiopulmonar y el aparato fonador, así como las patologías más comunes de ambos sistemas y hábitos saludables recomendados. Incluye secciones sobre la anatomía y fisiología del aparato respiratorio y cardiovascular, las enfermedades más frecuentes de dichos sistemas y sus causas y formas de prevención, y consejos sobre el cuidado de la voz.
El documento describe la importancia de la epidemiología para la salud pública y las ciencias clínicas. La epidemiología estudia la distribución y los determinantes de las enfermedades en las poblaciones y aplica estos estudios para controlar problemas de salud. La epidemiología provee información valiosa para medir el estado de salud de las poblaciones, identificar factores de riesgo, desarrollar estrategias de prevención y control, y evaluar la efectividad de los programas de salud.
The document discusses the process of developing a work breakdown structure (WBS) for a housing construction project. It begins by establishing the levels of the WBS from Level 1 (the overall project) down to Level 4 (individual tasks). It then shows how to develop a WBS dictionary to define the work for each WBS element. Next, it covers creating an organizational breakdown structure (OBS) to assign responsibilities to organizational departments. Finally, it explains how to merge the WBS and OBS into a responsibility assignment matrix (RAM) to allocate specific tasks to responsible parties.
Suresh Kumar is the AGM and Group IT Head of Chemmanur International Group. He has over 20 years of experience in IT management roles. He is responsible for managing the IT requirements of the group which has interests in non-banking finance, microfinance, gold/diamonds, and real estate. Some of his responsibilities include implementing VPN, developing software, implementing security systems, managing servers and websites, and leading a team of 35 IT professionals. He has received several awards for his work in the IT field.
The document discusses Work Breakdown Structure (WBS), which is a deliverable-oriented decomposition of a project into smaller, more manageable components. A WBS breaks down the project scope into smaller parts for estimating, scheduling, and monitoring and control. It helps define the total scope of work, assign responsibilities, and track costs, schedule, and deliverables. The key steps to develop a WBS are to identify the main project deliverables and break them down into successively smaller work packages or tasks in a hierarchical manner. This allows estimating time and costs for each component and monitoring project progress.
Agile development methodology focuses on iterative development where requirements and solutions evolve through collaboration between cross-functional teams. Some key aspects of agile include short development cycles, working software over documentation, customer collaboration, and responding to change. Scrum is a popular agile framework used at W3i that utilizes user stories, estimating, planning meetings, daily stand-ups, burndown charts, sprints, reviews and retrospectives to deliver working software frequently.
The document provides information on performance management in an agile environment. It discusses that performance management should focus on setting goals at the beginning of the year and reviewing progress, providing feedback throughout the year. It also notes that performance is a shared responsibility between management and individuals, and that the system and environment set by management impacts performance more than individual responsibility alone. Regular feedback and discussions help individuals improve and align their goals with team and organizational goals.
This document discusses an upcoming webinar on adopting Agile practices. It provides an overview of Agile concepts like iterative development, working software, and responding to change. It then discusses Scrum roles, ceremonies, and artifacts. The webinar aims to explain what's in it for stakeholders like customers, project managers, and team members in making the transition to Agile. Attendees are prompted to consider action items they can implement. Upcoming related trainings in Boston are also advertised.
Presentation with some examples to start running an agile process to implement a marketing structure with product and marketing teams. The example is based in a specific organization but can be used to new insights for others firms and market segments.
Open Source Software Development Practices that WorksChoong Ping Teo
The document discusses open source software development practices that focus on being agile and iterative. Some key practices include using user stories instead of heavy documentation, delivering working software in short iterations, estimating tasks by breaking work down, respecting teammates, having daily standups, keeping to-do lists short, writing tests, holding retrospectives, and continuously improving through learning and adjustments. The overall message is that these agile practices work because they are simple, allow flexibility to adapt to changes, and focus on delivering working software.
From four to forty in four years - lessons from growing a teamRich Allen
Between 2016 and 2020, the PureGym IT Team grew from 4 to 40 people. During that time Rich worked closely with them to navigate the tricky process of scaling. This talk is a journey through that growth period and discusses the variety of processes and practices that were applied in order to stay "Agile".
We'll touch on the various approaches taken including topics such as Scrum, Lean, Kanban, GIST planning, Lean Startup, DevOps, IaC, Azure, Story Mapping, BDD, TDD, Project vs Product and we'll be looking at the successes, failures and lessons learned.
We'll also look at how concepts from Team Topologies were applied, what team structures and interaction models were chosen and how that shifted the team dynamic. We will discuss what, in Rich's opinion, has worked well and what hasn't worked well during that time.
At very least you will walk away from this session with a long list of books to read and hopefully some insights into whether you might want to try some of the approaches discussed during the talk.
SketchFlow allows users to quickly prototype and iterate on user interface designs without extensive time or resource investments. It provides an informal way to explore ideas and evolve rough concepts into living prototypes. This rapid and cost-effective approach focuses on being creative and building the best solution.
Effective prototyping with SketchFlow allows experimenting with application flow, screen layouts, and state transitions. The interactive player engages clients by displaying working prototypes and collecting feedback directly in Expression Blend.
Agile practices like iterative development and user-centered design help teams collaborate effectively and respond quickly to change.
The document provides an overview of Agile and Scrum frameworks. It describes the key challenges with traditional software development approaches and how Agile and Scrum address these challenges through incremental delivery, frequent feedback, and transparency. It outlines the core components of Scrum including roles, ceremonies, and artifacts like product backlog, sprint backlog and burn down charts. Scrum uses short iterative cycles called sprints to incrementally develop working software and gather feedback to continuously improve.
Agile software development methodology is sweeping the IT Industry. Many organizations are experimenting with Agility and there are many “brands” of Agile including Scrum, XP, Lean, Crystal Clear and DSDM. Adoption of one of these methodologies could be wholesale in the case of a small well defined project that has no dependencies on other projects and can be completely delivered by a trained and motivated team. As these types of adoptions are rare organizations are looking for ways to ease into Agile practices without losing productivity.
This session is designed to discuss and identify ways that agile enablers can facilitate the transition to Agile practices. Participants learn basic Agile practices as well as techniques for introducing them to the software delivery team. This session will present common software delivery problems and the Agile path to solutions.
Agile Lessons Learned From the TrenchesBrendan Flynn
Brendan Flynn presented on lessons learned from implementing Agile practices at Pointroll. Key lessons included: creating visibility into development processes and metrics; gaining executive support; making data-driven decisions; focusing on business value over features; ensuring proper training; optimizing across teams; and rigorously inspecting and adapting practices over time. While hard work, adopting Agile frameworks improved delivery, quality, and alignment between business and technology teams at Pointroll.
Delivering beautiful software & web products efficiently 2022_Sep.pdfLaSoft
LaSoft is Web & Mobile Development Agency.
We have been a trusted technology partner for businesses, consulting companies, and startups since 2014. We work with partners worldwide from the USA, Canada, Netherlands, Israel, Germany, Switzerland, and the UK to Saudi Arabia and Nigeria.
Our main expertise lies in data analytics & visualization, business optimization and digitalization, real estate, marketplaces, HR management, and education tech projects.
Our teams successfully delivered more than 85 big web projects and continue to support them; all our projects solve global business tasks. Top Silicon Valley Companies use the product we build.
LaSoft is excellent in web, and mobile development, product design, cloud deployment, business analysis, project specification, project management, and technical partner support.
For more information about us, visit www.lasoft.org
Meetings in the Life of an Agile PM by Microsoft Product LeaderProduct School
-Understand how recurring activities create clarity in an otherwise complicated role
-Learn what these recurring meetings look like with real-life examples
-Understand how to use each meeting effectively to drive your product forward
You keep using the word agile, i do not think it means what you think it meansNathan Gloyn
Slides for the talk about what people think agile is, what agile is about and how you can get back to the idea of agile.
A recording of the talk from NDC London 2016 should be available here https://vimeo.com/158164783
Meetings in the Life of an Agile PM by Microsoft Product LeaderProduct School
-Understand how recurring activities create clarity in an otherwise complicated role
-Learn what these recurring meetings look like with real-life examples
-Understand how to use each meeting effectively to drive your product forward
Execution and Accountability - UBT New ZealandRESULTS.com
This document discusses the importance of execution and accountability in business. It notes that 90% of strategies and health club memberships fail due to poor execution. Few employees understand their company's strategy or priorities. The document recommends setting big audacious goals, making performance visible using tools like traffic lights, celebrating small wins, confronting poor performance, and praising good performance. Setting goals, tracking metrics, assigning tasks, and holding people accountable are key to effective execution.
Execution and Accountability - UBT Nth America presentationRESULTS.com
In this presentation, Stephen Lynch from RESULTS.com takes UBT members through an introduction to some key concepts to help drive execution and accountability
Using Query Store in Azure PostgreSQL to Understand Query PerformanceGrant Fritchey
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
Project Management: The Role of Project Dashboards.pdfKarya Keeper
Project management is a crucial aspect of any organization, ensuring that projects are completed efficiently and effectively. One of the key tools used in project management is the project dashboard, which provides a comprehensive view of project progress and performance. In this article, we will explore the role of project dashboards in project management, highlighting their key features and benefits.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdfVALiNTRY360
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
11. Agile Manifesto
Individuals and interactions Processes and tools
Working software Comprehensive documentation
Customer collaboration Contract negotiation
Responding to change Following a plan
36. Product Owner
Defines the feature set and roadmap
Prioritizes the features to be developed
Represents the customer
Reviews delivered features at the end of the
sprint
37. ScrumMaster
Facilitates the scrum process
Protect the team from outside interference
Keeps the team focused on the sprint goals
Removes obstacles
39. As a Site Director, I would
like to look up a child so
that I can view their
registered programs
User Stories
40. As a Association Director, I
would like to create a child
care site so that I can
schedule programs
As a Association Director, I
would like to create a child
care site so that I can
schedule programs
As a Association Director, I
would like to manage fee
charts so that I can charge
members different rates
for different programs
As a Site Director, I would
like to register a child for a
program so that I can
schedule programs
As a Site Director, I would
like to look up a child so
that I can view their
registered programs
Product Backlog
44. Daily Standup
3 Questions...
What did you accomplish since the last meeting?
What are you going to do before the next meeting?
What obstacles are in your way?
66. How has this helped us create better
software?
We deliver value more quickly
Transparency & visibility
Team ownership
Shared understanding across the team
Collaboration & communication improved
More fun!
67. Applications outside of software?
Academia
Movie/TV
Marketing
Sales
Wedding Planning
Vacation Planning
78. Output
As a Association Director, I
would like to create a child
care site so that I can
schedule programs
As a Association Director, I
would like to create a child
care site so that I can
schedule programs
As a Association Director, I
would like to manage fee
charts so that I can charge
members different rates for
different programs
As a Site Director, I would
like to register a child for a
program so that I can
schedule programs
As a Site Director, I would
like to look up a child so
that I can view their
registered programs
A lot of people only focus on the big visible parts of agile. Daily standups and post-it notes. There’s a lot more beneath the surface!
Agile should be thought of as more of a mindset or culture than a process. A lot of people get lost in the process aspects of transitioning to agile and they lose sight of the goal. Moving to agile requires a major shift in thinking for most people.
The goal isn’t to follow an agile process, but to consistently deliver value to your customers and users.
Agile is hard. Agile will not solve all of your problems. If anything, it only makes them more visible and obvious.
We are not perfect at Agile. The beauty is that there is great value without being perfect at it.
Need to understand everything before starting. No feedback from customers beyond initial research.
Information flows one way. No easy mechanism for changes. They are expensive.
Software systems tend to evolve.
We used to think that we had to specify everything up front before we even wrote the first line of code.
Traditional software was built by teams working in silos. They only really care about getting the work in their “silo” completed and passing it on the the next team. Some teams actually work in separate locations.
Releases were big, only happened once or twice a year, and someone usually got hurt.
That works well if you are manufacturing parts.
It assumes that you understand the customer’s needs and know the exact solution.
Studies in the late 90’s early 2000’s show that anywhere from 70% - 80% of projects fail under waterfall.Canceled, Delayed, Over budget...
In February 2001, 17 software developers met at a ski resort in Snowbird, Utah, to discuss lightweight development methods.
2 things came out of that weekend:
Agile Manifesto
12 principles
We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value the things on the left over the things on the right.
That is, while there is value in the items on the right, we value the items on the left more. When there is conflict, the values on the left win.
Agile methods prefer to define themselves in terms of &quot;values, principles and best practices,&quot; rather than as &quot;processes and procedures.&quot;
The following are some of the most important principles
The most important principle of Agile Software Development.
Customer satisfaction by rapid, continuous delivery of useful software
Working software is delivered frequently (think weeks rather than months)
We embrace the notion that requirements change, unexpected requirements appear, priorities shift and development practices must enable quick, accurate adaptation to these changes.
How many times have you heard someone say, “That is cool - but... what if it also did X?”
Agile methods attempt to establish a high level of collaboration among developers and project stakeholders.
We need to understand what we are building, who we are building it for, and why?
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Those doing the work make decisions about how to do it. Drive tactical decisions down to the team.
Dan Pink - Drive (Autonomy, Mastery, and Purpose)
Never tell people how to do things. Tell them what to do, and they will surprise you with their ingenuity. -Patton
Collaboration amongst team members is vital.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Builds a shared understanding!
The “working software” should be demonstrated regularly to team members and stakeholders.
Collect feedback “early and often”.
Be suspect of teams that are not willing to demonstrate their progress.
If you aren’t building software then, you should deliver something of value to customers.
Teams should work at a pace that they can sustain indefinitely
Teams are more effective and productive if they work at a sustainable pace.
Many studies done around teams that work more than 50 hours a week.
Continuous attention to technical excellence and good design enhances agility.
Promote solid design principles, developer testing (TDD), peer review, refactoring, etc.
Work to reduce technical debt.
Simplicity--the art of maximizing the amount of work not done--is essential.
Ask the question of whether or not you really need something? Do we need big up-front design?
Work to optimize the teams workflow and eliminate unnecessary activities and deliverables.
Foster a culture where it is OK to question the value of a particular process or activity.
Teams should be empowered to focus on doing whatever is necessary to deliver the features. Encourage teams to swarm on tasks that need to be completed even if it puts them out of their comfort zone.
Break things down into small pieces that can be worked on iteratively. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Iteration length is fixed. Every Iteration is a mini increment of the functionality and is build on top of previous iteration.
Always strive to improve. Constantly look at how we are doing and ask “What could we do to be better?”
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Agile is not a destination - you have to keep working at it.
This is often referred to as the “waterfall” software development process.
The new way is iterative.
We build “potentially shippable” features every iteration.
We work in iterations called “Sprints”. We have a prioritized backlog that we pull from to build new features each sprint.
Instead of silos, team members work closely together
Releases are smaller and more frequent
Customers are happy and no one gets hurt!
How common is agile? Are big companies using it? YES
75% of all agile teams are using Scrum or a Scrum hybrid process
Word cloud based on the Version One “State of Agile” survey for 2013.
The name comes from the sport of rugby, where a scrum is the mechanism for getting the ball moving after it has gone out of play.
Rather than a full process or methodology, Scrum is a framework. Scrum is not very prescriptive.
Scrum, in a nutshell, is a very light framework for delivering real products early, often and consistently. The products can be anything: new processes, software, physical products, or running an operation (like a business). It’s a “thing” that teams within corporations “do” — a new and better way of working. And it’s a great environment for helping teams move toward high performance, for real. Scrum actually calls teams forth into high performance and it calls the organization around teams to get aligned around the most important, highest business value items to create — one after the other. And those items get created within a short period of time and with high quality. It’s a way of aligning expectations with outcomes. In short, it helps teams deliver to a delighted customer. Every time.
The Product Owner Team represents the business, customers or users and guides the team toward building the right product. Maximizing the value of the work the scrum team does
The ScrumMaster can be thought of as a coach for the team, helping team members use the Scrum framework to perform at their highest level.
Responsible for ensuring that the process is understood and followed. Watches for stress points!
Designed to optimize flexibility and productivity. Typically 5-9 people. Team picks picks the work to do each sprint. Decides on what and how much.
Agile requirements. User Stories are high level descriptions of what the user would like to do with the system.
Just enough info to estimate the relative size; Drives conversation around the feature at dev time. Shifts focus from writing to talking.
Often captured on index cards or sticky notes to emphasize their “placeholder for conversation” nature.
Product owner creates a backlog of features and captures them as “User Stories”
User Stories are high level descriptions of what the user would like to do with the system.
Just enough info to estimate the relative size; Drives conversation around the feature at dev time. Shifts focus from writing to talking. Epic, Theme, User Story
Often captured on index cards or sticky notes to emphasize their “placeholder for conversation” nature.
Work in short iterations called “sprints” Most common is 2 weeks
Sprint PlanningBreak things down into smaller pieces
Definition of “Done”
Stories completed are “potentially shippable”.
Ceremonies of Scrum: ~15 minutes - same time every day. Synchronization meeting. Not for solving problemsNot a status for Scrummaster! Commitment to peers. This is so each person has a clear understanding of what is going on. A stand up meeting every morning is used to communicate problems, solutions, and promote team focus.
Ceremonies of Scrum: ~15 minutes - same time every day. Synchronization meeting. Not for solving problemsNot a status for Scrummaster! Commitment to peers.This is so each person has a clear understanding of what is going on. A stand up meeting every morning is used to communicate problems, solutions, and promote team focus.
Look at real software. The purpose is to demonstrate progress and gather feedback
Look at real software. The purpose is to demonstrate progress and gather feedback
Anyone can attend.
Used to review the past Sprint and determine what adaptations will make the next Sprint more productive, fulfilling, and enjoyable. Look at both what is and is not working. 30-60 minutes.
Whole team participates (ScrumMaster, Product Owner, Team)
Used to review the past Sprint and determine what adaptations will make the next Sprint more productive, fulfilling, and enjoyable. Look at both what is and is not working. 30-60 minutes.
Whole team participates (ScrumMaster, Product Owner, Team)
Start, Stop, Continue
Sailboat Retrospective Exercise
Winds= Propel us forward
Anchors= Hold us back
Icebergs= Obstacles to look out for and avoid
Humans are horrible at estimating how long it will take to do something. Ask my wife!
How tall is the Empire State building? Most people can agree that it is twice as tall as the building next to it, but I bet their estimates in feet would be all over the place.
Story points are a form of relative sizing. Scale is different for each team
Only used for planning purposes.
We measure the velocity (avg. points completed each sprint) as an empirical tool to help us plan for how much we can accomplish in the future. Should NEVER be used as a measure of productivity. Teams will game it and it will become useless.
This is how we do release planning for a team with a velocity of 14 story points.
Some charts for measuring progress during the sprint.
Velocity is 13 points for this team.
This is the rate they need to close stories in order to hit their goal of 13 points.
Points are tracked for each work day. Completed 3 story points on 2/20
0 points completed for the next two days
6 points were completed on 2/25
Above the line is good
Below the line means the team is behind. It’s not uncommon to be below the line early in the sprint.
Cycle time is used to track the average number of days to complete a story. Lower numbers are better. This is useful for many reasons. One is that is encourages you to break stories down into smaller chunks and deliver value more frequently.
We use a Product Owner Team board to track user story discovery, planning, and estimation activities.
We survey the team periodically to gauge their satisfaction with how the team is functioning.
Agile is being used in a lot of different industries outside of software. The following are all articles on how it is being used in different companies.
Agile as a parenting tool
Eric Nuzum from NPR says programs using Agile have been developed for 1/3 of the usual costs.
Jonathon Colman from REI is using it for marketing
Agile as a tool for families
I use it at home myself. Here are my two oldest helping me with our weekly retrospective. We talk about what went well the past week, what didn’t go as well, and what we want to try next week. They feel more engaged and invested in these things if we let them participate.
The People Team at my company is using Agile to help them plan and track projects.
Big tasks are intimidating. It’s also harder to show progress when you are working on a huge project or task.
Focus on doing the things that matter.
Delivering a feature is output. Delighting a customer is outcome.
We naturally tend think of our work mostly in terms of effort or output. How many new features are in the release? How many story points did we complete in the sprint? We talk about our work in the ways that are easy to quantify and measure.
The outcome of our work isn&apos;t as easy to measure, but it&apos;s what really matters. We all intuitively know that our goal isn&apos;t to release 10 new features this year, but to improve the lives of our customers and their members as best we possibly can. To do that, we must always focus on the outcome or impact our work will have on the users of our products.
We should try and maximize outcomes while at the same time, minimizing output. This applies to everything you do. Always think about what action you can take to have the biggest impact to our customers.
Task board: The key benefits are that the work can be seen at any moment, the work that people are doing is not hidden behind some &apos;long-range&apos; goal, and what features/items get worked on can change drastically and very quickly in response to changing needs.
There are a LOT of visual indicators on this task board. The stickies colors have significance, the columns indicate progress, check marks on stories show acceptance, lego avatars show who is working on which tasks, the tasks are prioritized top-down, remaining hours are written on the stickies, magnetic darts indicate a review is needed, wavy blue line shows the team’s commitment goal. You can’t easily get that level of info from a tool such as Excel. You can walk up to the board and within seconds know how things are going.
Track the team’s progress so that everyone knows how they are doing. Set goals, make them visible, and track your progress.
Plans are useless, but planning is essential. Don’t get too committed to your plan. A lot of times we make plans, then we need to change our plans when we learn new info. Don’t be afraid to act on what you learn.
These meetings are to coordinate efforts, communicate progress, and raise obstacles or issues.
Ask the question of whether or not you really need something?
Work to optimize the teams workflow and eliminate unnecessary activities and deliverables.
Outcomes over Output!
Get out of your comfort zone!
Teams should be empowered to focus on doing whatever is necessary to deliver results.
Encourage teams to swarm on tasks that need to be completed even if it puts them out of their comfort zone.
Inspect & Adapt! Constantly look at how we are doing and ask “What could we do to be better?”
Sailboat Retrospective Exercise
Winds= Propel us forward
Anchors= Hold us back
Icebergs= Obstacles to look out for and avoid
Make sure you are having fun. There’s no right or wrong way to do these things. Make them work for you and your team.