This presentation was delivered by me in Agile Tour 2011 in total of 4 cities' events. It is on the topic of "Simplicity" and related Agile mindset and practices.
The Business Analysts Role in Agile Software Developmentallan kelly
The document discusses the role of business analysts in agile software development. It argues that the product owner role is often filled by a business analyst. While business analysts take a backseat in early agile adoption, their role becomes more important as teams become more effective in delivering business needs. Specifically, business analysts are key to reducing unnecessary work through improved analysis and requirements. The document recommends a ratio of one business analyst for every 3-7 developers, depending on how stable the product is and how rapidly requirements change.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
Have you ever been to a Formula One race and watched the pit crews in action? While most of the glory goes to the drivers, it is really the high-performance of the entire team and their processes that make the difference between winning and losing. Lean & Agile practices are well known in product development. But how do leaders of complex people systems practice Lean? This talk will share some proven techniques that help you create high performing teams, amplify learning, uncover waste, continually improve your standard work, manage your backlog, improve accountability, make decisions faster, uncover difficult issues.
Personal customer experiences are and will be more and more vital. People to people, but also people to machine. Today, there are several providers of the same services, and the new ones are faster, more flexible, and more personalized in their communications with their customers & users. How do we ensure that we provide the right information to our employees as well as to our customers so they can better serve and increase customer satisfaction?
This webinar will focus on how you as an organization will have to restructure, rethink and redesign your technological platform to support increasing employee- and customer demands.
Key takeaways:
Holistic understanding of how to make a successful cloud transition
Learn why modern organizations excel in customer treatment, productivity, flexibility, and agility
High-level architecture and how and why DevOps changes organizations
Overview of Agile for Business AnalystsSally Elatta
This seminar was presented to the IIBA Omaha group. My goal was to provide a quick overview of Agile and then dive into the role and skills needed for a BA on an Agile team. Let me know if you would like me to present this or a similar topic at your organization. sally@agiletransformation.com
Razorfish Scrum for Teams and Organizations Software Architect Conference 2013Razorfish
Razorfish Scrum for Teams and Organizations Software Architect Conference 2013. If you’ve ever worked on a software project, this question should sound familiar. You’ve spent time rewriting schedules, cutting features and explaining The Mythical; Man-Month, the widely cited 1975 software bible. Its central principle is the slightly counterintuitive idea that adding manpower to a software project slows delivery. This may make you wonder what will speed up projects. Consider examining your tools and processes to see if there’s a faster way of getting things done. In this talk I will propose a cross-disciplinary process of applying scrum on your projects.
This document discusses successful Agile teams at scale. It begins by explaining why organizations want to adopt Agile practices like shorter time-to-market and improved quality. However, true Agile adoption requires changes to business, culture and ways of working. The document then discusses scaling Agile through frameworks like SAFe and DAD which provide structure for large, distributed teams. Supporting practices for Agile at scale include risk management, delivery assurance and governance. Finally, the document states that successful Agile teams at scale provide benefits like reduced time-to-value and improved business relationships, but require investments in people, processes and tools to support collaboration.
The Business Analysts Role in Agile Software Developmentallan kelly
The document discusses the role of business analysts in agile software development. It argues that the product owner role is often filled by a business analyst. While business analysts take a backseat in early agile adoption, their role becomes more important as teams become more effective in delivering business needs. Specifically, business analysts are key to reducing unnecessary work through improved analysis and requirements. The document recommends a ratio of one business analyst for every 3-7 developers, depending on how stable the product is and how rapidly requirements change.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
Have you ever been to a Formula One race and watched the pit crews in action? While most of the glory goes to the drivers, it is really the high-performance of the entire team and their processes that make the difference between winning and losing. Lean & Agile practices are well known in product development. But how do leaders of complex people systems practice Lean? This talk will share some proven techniques that help you create high performing teams, amplify learning, uncover waste, continually improve your standard work, manage your backlog, improve accountability, make decisions faster, uncover difficult issues.
Personal customer experiences are and will be more and more vital. People to people, but also people to machine. Today, there are several providers of the same services, and the new ones are faster, more flexible, and more personalized in their communications with their customers & users. How do we ensure that we provide the right information to our employees as well as to our customers so they can better serve and increase customer satisfaction?
This webinar will focus on how you as an organization will have to restructure, rethink and redesign your technological platform to support increasing employee- and customer demands.
Key takeaways:
Holistic understanding of how to make a successful cloud transition
Learn why modern organizations excel in customer treatment, productivity, flexibility, and agility
High-level architecture and how and why DevOps changes organizations
Overview of Agile for Business AnalystsSally Elatta
This seminar was presented to the IIBA Omaha group. My goal was to provide a quick overview of Agile and then dive into the role and skills needed for a BA on an Agile team. Let me know if you would like me to present this or a similar topic at your organization. sally@agiletransformation.com
Razorfish Scrum for Teams and Organizations Software Architect Conference 2013Razorfish
Razorfish Scrum for Teams and Organizations Software Architect Conference 2013. If you’ve ever worked on a software project, this question should sound familiar. You’ve spent time rewriting schedules, cutting features and explaining The Mythical; Man-Month, the widely cited 1975 software bible. Its central principle is the slightly counterintuitive idea that adding manpower to a software project slows delivery. This may make you wonder what will speed up projects. Consider examining your tools and processes to see if there’s a faster way of getting things done. In this talk I will propose a cross-disciplinary process of applying scrum on your projects.
This document discusses successful Agile teams at scale. It begins by explaining why organizations want to adopt Agile practices like shorter time-to-market and improved quality. However, true Agile adoption requires changes to business, culture and ways of working. The document then discusses scaling Agile through frameworks like SAFe and DAD which provide structure for large, distributed teams. Supporting practices for Agile at scale include risk management, delivery assurance and governance. Finally, the document states that successful Agile teams at scale provide benefits like reduced time-to-value and improved business relationships, but require investments in people, processes and tools to support collaboration.
In Agile/Scrum the skills of a BA are still needed, especially in more complex efforts. This describes BA skills applied in Agile. Should the BA be a Product Owner? On the scrum team?
The document provides an overview of keys to success for getting the most out of a Chinese engineering team. It discusses the importance of having the right key associates with skin in the game who are committed, accountable, and culturally skilled. It also emphasizes the need for functional partnerships between US and Chinese teams to build and transfer knowledge. Finally, it outlines the importance of tools like communication tools, computer tools, and project management processes to ensure successful collaboration.
This is a presentation made to Surge Accelerator in Houston in March 2013. This serves as a Guide to Early Stage Technology Companies, building enterprise class software.
This covers the typical lifecycle of a software start-up, fundamentals of Agile software development, and some do's and don't for how to build successful software companies.
The document discusses how to clean up Agile and ensure it remains clean. It begins by examining why Agile has become a "dirty word" in some places due to failures when not properly implemented. Some signs that Agile is "dirty" include standardized tools that don't work for all cases, developers unable to get work done, and a cycle of declining trust. The document then provides techniques for cleaning up Agile, such as focusing on outcomes over processes, empowering teams, and eliminating waste. It suggests metrics for knowing if changes have worked, like autonomous cross-functional teams and a learning culture. Finally, it recommends staying ahead by continually learning and improving, measuring the right things, and understanding that Agile is about
This document provides an introduction to lean principles and kanban. It discusses two pillars of lean thinking: don't trouble the customer and develop people. Lean principles include continuous improvement, respect for people, eliminating waste, and problem solving. Kanban is introduced as a change management methodology that utilizes lean tools like visualizing workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to recognize improvement opportunities. Similarities and differences between scrum and kanban are also outlined.
Design Thinking, Agile, DevOps - fuel the innovation deliveryYi Xu
This document discusses approaches to fuel innovation delivery through design thinking, agile, and DevOps. It provides an overview of each approach and how they can work together. Specifically:
- Design thinking focuses on understanding user needs and designing solutions to meet those needs. When paired with agile, it can increase and accelerate innovation.
- Agile provides benefits like visibility, adaptability, and risk reduction through practices like iterative development and continuous feedback. However, agile alone is not enough to sustain growth - design thinking is also needed.
- DevOps applies lean principles to software delivery to create continuous feedback loops with customers. It aims to get ideas into production fast, get users, and get feedback to continuously improve
Scaling Product Thinking with SAFe - The Secret Sauce for Meaningful Product ...Cprime
The Scaled Agile Framework (SAFe) is the agile methodology of choice for many large enterprises. It promises predictable and frequent delivery in complex environments.
Our experience with organizations that adopt SAFe shows that an organization’s willingness to blend product-thinking, technical agility and a culture of learning is the secret sauce for catapulting the organization from “process excellence” into meaningful product impacts.
In this webinar, we’ll share tried and tested ways of introducing product thinking and engineering practices into SAFe organizations, covering organizational, product, and technical ground.
You'll learn:
- How to establish products as value streams and gently reorganize ARTs over time without sacrificing product community or continuity.
- How to use product stories to engage your teams before and during PI planning in a way that invites collaboration on a healthy blend of continuous discovery and delivery.
- How customer, architectural, and operational learning pave the way for scaling to teams of teams from a DevOps perspective, including patterns and anti-patterns.
Delivering value early and often, giving ourselves the best opportunity to beat the competition to market, realize revenue and discover insights that we can use to help us improve.
Key lean principles for organizational changeLeanDog
The document discusses key lean principles for organizational change, including amplifying learning through retrospectives and experiments, deciding work late in the process to reduce waste, and building integrity through servant leadership, transparency, and collaborative decision making. It also describes how lean principles can be applied to software development through techniques like Scrum, Kanban, and continuous delivery.
Lessons learned from managing a distributed agile teamAgileDenver
The document discusses lessons learned from managing a distributed agile team. It summarizes that distributed agile teams face additional complications like different time zones and a lack of in-person collaboration, but these challenges can be overcome. Key lessons are that everyone must follow the same processes, artifacts must be accessible remotely, strong scrum masters and business analysts are needed, and in-person meetings are still valuable when possible. Remote agile is difficult but not impossible with the right team and practices.
In his book, The Lean Startup, Eric Ries highlights the value of the iterative & incremental approach to technology development AKA agile( & scrum;) he also elaborates on his lean startup model by publicizing MVP & “The Build, Measure, Learn” loop. All this in mind, almost at all levels and growth phases of businesses, tech teams are continuously being bombarded by difficult yet crucial prioritization questions resulting in decision fatigue, and inaction.
We will introduce “OKRs” Objectives & Key Results. A simple yet effective goal-setting tool that guarantees visibility & alignment across the whole organization; Business, Tech, Design, Finance, Operation, etc.
This will extend your “lean startup” knowledge with OKRs a model pioneered by Andy Grove; Former Intel CEO & John Doerr; VC & Author of Measure What Matters. John introduced the model to Google back in the early days & they adopted it on-the-spot & have been publicizing it ever-since.
Whether you are a company of one, A small startup, A growing one or a big enterprise, OKRs along with Agile & Lean Startup models will definitely be an invaluable addition to your toolbox.
Yes, both of them are buzz words, but when you peel back the buzz, what is the true value that lies behind both of these methods? How do they compare and how do they differ? Most importantly, how can we bring about Agility to SOA projects and how can better architecture be applied to Agile projects? Me and Kyle also discussed some of the challenges with attempting iterative development on SOA projects and provided some ways both can leverage each other's strengths.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
www.AgileTransformation.com
Доклад: “Secrets of Selling Your Global Software Development Services”
Многие из вас наверняка являются экспертами в области программного обеспечения, может быть даже считают себя гениями. Но технические гении не отличаются хорошими навыками в области продаж.
Этот доклад будет посвящен секретам успешных продаж услуг по разработке программного обеспечения, в частности клиентам из Северной Америки. Важно правильно оценить ваши шансы и перспективы и суметь убедить покупателя в том, что именно вы будете для него лучшим разработчиком. Из доклада вы узнаете, как использовать современные маркетинговые технологии для демонстрации ваших возможностей и убеждения клиентов.
Конечно, хорошо быть гением. Но кроме ваших родных и близких кто нибудь об этом знает?
Multi-team Release Planning, as it is often executed, fails to bring alignment beyond one-time inter-team coordination. This hands-on session teaches the techniques and exercises for a Product Wall Release Planning Workshop. The Product Wall Release Planning Workshop brings together all the elements of business needs, user experience, value proposition, dependency resolution, risk mitigation and user story planning. By combining various Agile collaboration techniques in a guided sequence, your multi-team Release Planning can create alignment through learning together and building together a clear path to success, from the release vision all the way to Sprint Backlogs.
Alan Dayley brings more than 25 years of software engineering experience to his Agile Coaching practice. Agile Coach, CSM, CSPO, CSP. Alan works to strengthen the people side of creative work. Alan loves to help people learn and create innovation in their life. Besides Agile coaching, he spreads this passion as a founding member of the Phoenix Scrum User Group and speaker coach for the Ignite Phoenix series of events.
The document discusses various frameworks for scaling agile development in large organizations. It introduces Disciplined Agile Delivery (DAD), the Scaling Agile Framework (SAFe), Agility Path, Continuous Improvement Framework (CIF), and Large Scale Scrum. DAD is described as a decision-oriented framework, while SAFe is presented as more prescriptive. The document emphasizes that principles are more important than practices and that adopting an agile mindset is key to successful scaling.
Real World Effective/Agile Requirements - IBM Innovate 2010 -sally elattaSally Elatta
This is the presentation I offered at the IBM 2010 conference around real world techniques and best practices for effective requirements gathering and release planning. Enjoy!
This document provides an overview of Agile software development. It begins by defining Agile as a project management process that encourages frequent inspection and adaptation. It then discusses some common Agile practices like Scrum and eXtreme Programming. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Finally, it provides advice for different roles on how Agile can benefit them and their work.
This document discusses Design Operations (DesignOps) and its goals of amplifying the value of design investments and scaling design teams. It describes key aspects of DesignOps including human resources, community, communications, tools, infrastructure, workflow, governance, and culture. Elements like organizational structure, hiring processes, onboarding, and developing a design system are examined. The roles and qualifications for a DesignOps leader are also outlined. Overall, the document provides an overview of DesignOps and its various components for setting teams up for success and increasing an organization's design investment.
MTBiz is for you if you are looking for contemporary information on business, economy and especially on banking industry of Bangladesh. You would also find periodical information on Global Economy and Commodity Markets.
Signature content of MTBiz is its Article of the Month (AoM), as depicted on Cover Page of each issue, with featured focus on different issues that fall into the wide definition of Market, Business, Organization and Leadership. The AoM also covers areas on Innovation, Central Banking, Monetary Policy, National Budget, Economic Depression or Growth and Capital Market. Scale of coverage of the AoM both, global and local subject to each issue.
MTBiz is a monthly Market Review produced and distributed by Group R&D, MTB since 2009.
Affiliates And Internal Search Recipe For DisasterAffiliate Summit
Google's rules are often misunderstood, causing turf wars between the affiliate channel & search teams. Learn through real world examples how to maximize affiliate search & internal search programs.
In Agile/Scrum the skills of a BA are still needed, especially in more complex efforts. This describes BA skills applied in Agile. Should the BA be a Product Owner? On the scrum team?
The document provides an overview of keys to success for getting the most out of a Chinese engineering team. It discusses the importance of having the right key associates with skin in the game who are committed, accountable, and culturally skilled. It also emphasizes the need for functional partnerships between US and Chinese teams to build and transfer knowledge. Finally, it outlines the importance of tools like communication tools, computer tools, and project management processes to ensure successful collaboration.
This is a presentation made to Surge Accelerator in Houston in March 2013. This serves as a Guide to Early Stage Technology Companies, building enterprise class software.
This covers the typical lifecycle of a software start-up, fundamentals of Agile software development, and some do's and don't for how to build successful software companies.
The document discusses how to clean up Agile and ensure it remains clean. It begins by examining why Agile has become a "dirty word" in some places due to failures when not properly implemented. Some signs that Agile is "dirty" include standardized tools that don't work for all cases, developers unable to get work done, and a cycle of declining trust. The document then provides techniques for cleaning up Agile, such as focusing on outcomes over processes, empowering teams, and eliminating waste. It suggests metrics for knowing if changes have worked, like autonomous cross-functional teams and a learning culture. Finally, it recommends staying ahead by continually learning and improving, measuring the right things, and understanding that Agile is about
This document provides an introduction to lean principles and kanban. It discusses two pillars of lean thinking: don't trouble the customer and develop people. Lean principles include continuous improvement, respect for people, eliminating waste, and problem solving. Kanban is introduced as a change management methodology that utilizes lean tools like visualizing workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to recognize improvement opportunities. Similarities and differences between scrum and kanban are also outlined.
Design Thinking, Agile, DevOps - fuel the innovation deliveryYi Xu
This document discusses approaches to fuel innovation delivery through design thinking, agile, and DevOps. It provides an overview of each approach and how they can work together. Specifically:
- Design thinking focuses on understanding user needs and designing solutions to meet those needs. When paired with agile, it can increase and accelerate innovation.
- Agile provides benefits like visibility, adaptability, and risk reduction through practices like iterative development and continuous feedback. However, agile alone is not enough to sustain growth - design thinking is also needed.
- DevOps applies lean principles to software delivery to create continuous feedback loops with customers. It aims to get ideas into production fast, get users, and get feedback to continuously improve
Scaling Product Thinking with SAFe - The Secret Sauce for Meaningful Product ...Cprime
The Scaled Agile Framework (SAFe) is the agile methodology of choice for many large enterprises. It promises predictable and frequent delivery in complex environments.
Our experience with organizations that adopt SAFe shows that an organization’s willingness to blend product-thinking, technical agility and a culture of learning is the secret sauce for catapulting the organization from “process excellence” into meaningful product impacts.
In this webinar, we’ll share tried and tested ways of introducing product thinking and engineering practices into SAFe organizations, covering organizational, product, and technical ground.
You'll learn:
- How to establish products as value streams and gently reorganize ARTs over time without sacrificing product community or continuity.
- How to use product stories to engage your teams before and during PI planning in a way that invites collaboration on a healthy blend of continuous discovery and delivery.
- How customer, architectural, and operational learning pave the way for scaling to teams of teams from a DevOps perspective, including patterns and anti-patterns.
Delivering value early and often, giving ourselves the best opportunity to beat the competition to market, realize revenue and discover insights that we can use to help us improve.
Key lean principles for organizational changeLeanDog
The document discusses key lean principles for organizational change, including amplifying learning through retrospectives and experiments, deciding work late in the process to reduce waste, and building integrity through servant leadership, transparency, and collaborative decision making. It also describes how lean principles can be applied to software development through techniques like Scrum, Kanban, and continuous delivery.
Lessons learned from managing a distributed agile teamAgileDenver
The document discusses lessons learned from managing a distributed agile team. It summarizes that distributed agile teams face additional complications like different time zones and a lack of in-person collaboration, but these challenges can be overcome. Key lessons are that everyone must follow the same processes, artifacts must be accessible remotely, strong scrum masters and business analysts are needed, and in-person meetings are still valuable when possible. Remote agile is difficult but not impossible with the right team and practices.
In his book, The Lean Startup, Eric Ries highlights the value of the iterative & incremental approach to technology development AKA agile( & scrum;) he also elaborates on his lean startup model by publicizing MVP & “The Build, Measure, Learn” loop. All this in mind, almost at all levels and growth phases of businesses, tech teams are continuously being bombarded by difficult yet crucial prioritization questions resulting in decision fatigue, and inaction.
We will introduce “OKRs” Objectives & Key Results. A simple yet effective goal-setting tool that guarantees visibility & alignment across the whole organization; Business, Tech, Design, Finance, Operation, etc.
This will extend your “lean startup” knowledge with OKRs a model pioneered by Andy Grove; Former Intel CEO & John Doerr; VC & Author of Measure What Matters. John introduced the model to Google back in the early days & they adopted it on-the-spot & have been publicizing it ever-since.
Whether you are a company of one, A small startup, A growing one or a big enterprise, OKRs along with Agile & Lean Startup models will definitely be an invaluable addition to your toolbox.
Yes, both of them are buzz words, but when you peel back the buzz, what is the true value that lies behind both of these methods? How do they compare and how do they differ? Most importantly, how can we bring about Agility to SOA projects and how can better architecture be applied to Agile projects? Me and Kyle also discussed some of the challenges with attempting iterative development on SOA projects and provided some ways both can leverage each other's strengths.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
www.AgileTransformation.com
Доклад: “Secrets of Selling Your Global Software Development Services”
Многие из вас наверняка являются экспертами в области программного обеспечения, может быть даже считают себя гениями. Но технические гении не отличаются хорошими навыками в области продаж.
Этот доклад будет посвящен секретам успешных продаж услуг по разработке программного обеспечения, в частности клиентам из Северной Америки. Важно правильно оценить ваши шансы и перспективы и суметь убедить покупателя в том, что именно вы будете для него лучшим разработчиком. Из доклада вы узнаете, как использовать современные маркетинговые технологии для демонстрации ваших возможностей и убеждения клиентов.
Конечно, хорошо быть гением. Но кроме ваших родных и близких кто нибудь об этом знает?
Multi-team Release Planning, as it is often executed, fails to bring alignment beyond one-time inter-team coordination. This hands-on session teaches the techniques and exercises for a Product Wall Release Planning Workshop. The Product Wall Release Planning Workshop brings together all the elements of business needs, user experience, value proposition, dependency resolution, risk mitigation and user story planning. By combining various Agile collaboration techniques in a guided sequence, your multi-team Release Planning can create alignment through learning together and building together a clear path to success, from the release vision all the way to Sprint Backlogs.
Alan Dayley brings more than 25 years of software engineering experience to his Agile Coaching practice. Agile Coach, CSM, CSPO, CSP. Alan works to strengthen the people side of creative work. Alan loves to help people learn and create innovation in their life. Besides Agile coaching, he spreads this passion as a founding member of the Phoenix Scrum User Group and speaker coach for the Ignite Phoenix series of events.
The document discusses various frameworks for scaling agile development in large organizations. It introduces Disciplined Agile Delivery (DAD), the Scaling Agile Framework (SAFe), Agility Path, Continuous Improvement Framework (CIF), and Large Scale Scrum. DAD is described as a decision-oriented framework, while SAFe is presented as more prescriptive. The document emphasizes that principles are more important than practices and that adopting an agile mindset is key to successful scaling.
Real World Effective/Agile Requirements - IBM Innovate 2010 -sally elattaSally Elatta
This is the presentation I offered at the IBM 2010 conference around real world techniques and best practices for effective requirements gathering and release planning. Enjoy!
This document provides an overview of Agile software development. It begins by defining Agile as a project management process that encourages frequent inspection and adaptation. It then discusses some common Agile practices like Scrum and eXtreme Programming. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Finally, it provides advice for different roles on how Agile can benefit them and their work.
This document discusses Design Operations (DesignOps) and its goals of amplifying the value of design investments and scaling design teams. It describes key aspects of DesignOps including human resources, community, communications, tools, infrastructure, workflow, governance, and culture. Elements like organizational structure, hiring processes, onboarding, and developing a design system are examined. The roles and qualifications for a DesignOps leader are also outlined. Overall, the document provides an overview of DesignOps and its various components for setting teams up for success and increasing an organization's design investment.
MTBiz is for you if you are looking for contemporary information on business, economy and especially on banking industry of Bangladesh. You would also find periodical information on Global Economy and Commodity Markets.
Signature content of MTBiz is its Article of the Month (AoM), as depicted on Cover Page of each issue, with featured focus on different issues that fall into the wide definition of Market, Business, Organization and Leadership. The AoM also covers areas on Innovation, Central Banking, Monetary Policy, National Budget, Economic Depression or Growth and Capital Market. Scale of coverage of the AoM both, global and local subject to each issue.
MTBiz is a monthly Market Review produced and distributed by Group R&D, MTB since 2009.
Affiliates And Internal Search Recipe For DisasterAffiliate Summit
Google's rules are often misunderstood, causing turf wars between the affiliate channel & search teams. Learn through real world examples how to maximize affiliate search & internal search programs.
This presentation provides an overview of news in Odisha, India. It discusses the chief editor and mission to report truth and participate in government programs. It also summarizes key statistics about Odisha's population, economy, districts and their populations, forest coverage, agricultural production and an IT boom. The document encourages contacting the presenters for more details.
Este documento describe el impacto de las nuevas tecnologías en las empresas. Resume la evolución de las tecnologías desde 1950 y su influencia en los procesos empresariales. También analiza cómo Internet y las tecnologías móviles han revolucionado el marketing, especialmente para las pequeñas y medianas empresas.
Periodic weeding has been a major factor in increasing rice productivity under SRI methods. Weeding promotes healthy root growth and plant utilization of biomass, enhances soil aeration, and increases yields through more and larger tillers, panicles, and grains per panicle. The KB weeder design was improved by adding a U-shaped handle for better grip, decreasing the pipe length for ease of use, increasing the angle and adding supports for adaptability to different heights, and lengthening the spikes for better soil mulching. Manufacturers in West Bengal can produce up to 300 weeders total to provide SRI farmers with affordable and easy-to-use weeders. Quality control and a one-year warranty are used.
The Marler Clark Network: A complete Guide to Foodborne IllnessBill Marler
The Marler Clark foodborne illness network provides updated resources, news, discussion, and databases to answer all of your food safety or food poisioning questions.
Final Amendments to the Cook County Executive Budget Recommendationcookcountyblog
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
This document discusses the concept of simplicity through several examples from art, design, and business. It examines how artists like Pablo Picasso, Qi Baishi and Chinese potters achieved complexity with simplicity. Design philosophies of Muji, Apple, and GE emphasizing minimalism are presented. The value of simplicity in agile practices like Scrum and XP is discussed. Simplifying organizations, processes, tools and technical design are advocated to reduce waste and improve outcomes.
This document summarizes a panel discussion on success through agility. The panelists discussed how agility allows companies to adapt to changing demands and environments. They emphasized having a culture of collaboration, transparency, and empowerment. Continuous learning, thinking beyond rules, and leadership support of innovation at all levels also helps organizations act with agility. The panel concluded that most companies would benefit from cultivating a culture that enables flexibility and rapid adaptation.
Money, Process, and Culture- Tech 20/20 June, 2012Adrian Carr
A talk about Company Culture, Software, People, Lean Thinking, Agile Software.
This is the Powerpoint for a talk I gave at Tech2020, in Oak Ridge, Tennessee in June, 2012.
Agile From the Top Down: Executives & Leadership Living Agile by Jon StahlLeanDog
The document summarizes a presentation by Jon R. Stahl on getting executive leadership and organizations to practice agile principles from the top down. It discusses how most agile movements are not sustainable because they fail to change culture and establish a process. It advocates that leadership must live the values of agility, seek to understand their unique culture, and be transparent. It also provides examples of information radiators that can help visualize work, values, projects and assets to establish transparency and shared understanding.
The document discusses five things to do before implementing Agile practices: 1) Identify the reasons for adopting Agile, 2) Inform and educate teams and the organization about Agile ways of working, 3) Define engineering practices to use, 4) Define a product backlog, and 5) Set a definition of done. It emphasizes understanding why an organization wants to adopt Agile and how Agile will benefit the organization. It also discusses communicating changes to working styles and focusing on developing working software iteratively.
This document provides an introduction to Agile software development. It discusses the origins and evolution of Agile methods from the 1970s onwards. Key characteristics of Agile include iterative development, emphasis on individuals and interactions over processes, customer collaboration, and responding to change. Specific Agile methodologies like Scrum and Extreme Programming are described. The document also outlines 10 key principles of Agile development such as active user involvement, empowered self-organizing teams, frequent delivery of working software, and collaboration between all stakeholders.
This document provides an overview of practical scrum. It discusses the three scrum roles of product owner, scrum master, and team. It also describes the four scrum ceremonies and three artifacts. Key principles of scrum include self-organizing teams, empirical process, and delivering working software frequently. The document contrasts command-and-control with self-management and explains how the manager's role changes in an agile environment.
Having the Correct Context for an Agile TransformationDerek Huether
3 years, 5 business units, 20 lines of business, and over 100 teams. With so many interactions, having the correct context for Agile was (and still is) key to an ongoing transformation. Remember, we're not all Spotify!
Developing and Delivering Products in an Agile World (.75 PMI PDU)DCsteve
Customers expect delivery of your new products quicker and easier than ever before. Whether your customers are internal or external, they expect you to develop new products with increased frequency and to put those products in their hands seamlessly and automatically.
Learn how you can take advantage of Agile development methods to develop and ship quicker while maintaining the project and financial management your business requires. And, learn ways to automate your product delivery to get these products to your customers immediately upon completion. Bring automation and Agile development together to deliver new products to your customers more often and easier than ever before.
All attendees are eligible for .75 PDU Credit from the Project Management Institute (PMI).
Get the Transformational Story of Going Agile @ http://digitalcelerity.com/Pages.aspx/Agile-PPM
Agile Auckland agile 101 back to basicsEdwin Dando
This document provides an overview and introduction to agile concepts and Scrum. It begins with the objectives to provide a baseline understanding of agile and discusses why agile principles are needed in contrast to traditional predictive management. It then defines what agile and Scrum are, focusing on transparency, inspection and adaptation. Potential pitfalls of misapplying agile concepts are also covered. The document aims to educate practitioners on doing agile properly through mentored learning and finding the right approach for each situation.
Why agile is failing in large enterprisesLeadingAgile
Agile works. We get it. You don’t have to sell people on the underlying principles anymore. Even so, many large-scale agile transformations are struggling. Some have failed. Others can’t figure out why things aren't working after multiple attempts. It’s easy to blame the people, the process, and the culture. And it’s especially easy to blame management. However, the underlying problem is that most large organizations weren’t built to be agile. You need a way to safely and pragmatically refactor your company into an organization that can adopt agile and sustain the transformation. Mike Cottmeyer introduces a framework for understanding the type of company in which you work, its delivery constraints, and likely challenges you’ll face in your agile transformation. Mike shares a strategy for establishing an end-state vision and operational model to guide your transformation. Finally, he defines an approach for incrementally introducing change, measuring outcomes, and sustaining those changes.
Check out Mike giving this talk live https://www.leadingagile.com/why-agile-fails
This document discusses agile documentation practices based on a survey of 57 Symantec information developers. Some key findings include:
- Most information developers have less than one year of agile experience and see benefits of agile like improved schedules and delivering value.
- Frequent deployment and reviews have improved documentation quality by focusing on smaller chunks of work. Remote collaboration remains a challenge.
- Agile practices like daily stand-ups, estimating tasks, and transparent reporting increase motivation and accountability for documentation work.
- Strategies like cross-training, defining "done", tailoring stories to the organization, and using technology help information developers adapt to agile.
This document provides an overview of agile principles and methodologies. It defines agile as an iterative approach to incremental software development. The key aspects covered include:
- The Agile Manifesto which established 12 principles including customer satisfaction, welcoming changing requirements, frequent delivery, and business/development collaboration.
- Scrum, the most commonly used agile framework, which uses short sprints, daily stand-ups, sprint planning and retrospectives.
- Lean principles like continuous improvement, empowered teams, and visual controls.
- Scaling agile using frameworks like SAFe which coordinate multiple teams through program increment planning and scrums of scrums.
- Hybrid models that blend agile with other
The document discusses Agile software development methods. It defines Agile as an iterative and incremental framework that focuses on productivity, costs, quality, business flexibility, timely delivery, customer satisfaction, and transparency. The core values of Agile are outlined as focus, courage, openness, commitment, and respect. Agile works through short iterations with daily reviews and customer feedback to deliver working software incrementally.
User Stories Suck by David Hawks at North Dallas Product Owners MeetupAgile Velocity
The User Story concept was invented almost 20 years ago, it’s time for an update. This outdated process supports an old way of working focused on predictable requirements delivery instead of product discovery. Wouldn’t you like to know much earlier which features are not going to be valued by your market? We need techniques that shorten the feedback loop with customers, not stakeholders. We need to prioritize based on riskiest assumptions and iterate quickly through small experiments in order to (in)validate our ideas as fast as possible.
The document discusses adopting agile practices at an enterprise scale. It begins with an overview of agile principles and how Scrum is commonly used for teams. However, scaling agile to larger companies presents challenges related to management roles, technical specifications, and global collaboration. The Scaled Agile Framework addresses these challenges through features like program increment planning that synchronize work across many teams. Case studies show companies achieving benefits like increased productivity, faster issue resolution, and lower costs when using scaled agile frameworks.
The Agile Manifesto in the Star Wars UniverseAaron Griffith
The document adapts the principles of the Agile Manifesto to the Star Wars universe. It discusses concepts like self-organizing teams from the Empire and how Luke valued individuals and interactions. Throughout it draws parallels between Agile development practices and characters/events from Star Wars like how continuous attention to technical excellence enhances agility similar to Luke's Jedi training.
This document provides an overview of DevOps. It begins with definitions of DevOps, noting that it is a cultural and professional movement, not a new role or team. It discusses how DevOps aims to break down barriers between development and operations teams to improve collaboration. The document outlines some common DevOps practices like automating infrastructure, implementing continuous delivery, measuring metrics, and encouraging sharing of knowledge. It provides examples of how organizations have benefited from DevOps approaches like faster delivery and more stable systems. Overall, the summary emphasizes that DevOps is focused on changing culture and ways of working, not just tools or processes.
Similar to Simplicity (Agile Tour 2011 China) - Bill Li (20)
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Project Management Semester Long Project - Acuityjpupo2018
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
21. UPerform Your Agile and Project Performance Partner
Simplicity: GE 通用电气 Big & Simple
Simplicity is key to success
22. UPerform Your Agile and Project Performance Partner
Simplicity: GE 通用电气 Big & Simple
对Jack Welch的采访 1989年:
“Despite the complexity of GE’s global business, Welch
insists that Simplicity is key to success.
“Business isn’t complicated." he says. “The complications
arise when people are cut off from information they
need.”
Speed, Simplicity, Self-Confidence: An Interview with Jack Welch, by Noel Tichy and Ram Charan,
Harvard Business Review, 1989
23. UPerform Your Agile and Project Performance Partner
Simplicity: GE 特征及价值观
• Lean 精益
• Agile 敏捷
• Creative 创造性
• Ownership 主人翁精神
• Reward 回报
Speed, Simplicity, Self-Confidence: An Interview with Jack Welch, by Noel Tichy and Ram Charan, Harvard
Business Review, 1989
24. UPerform Your Agile and Project Performance Partner
Image from BN.com
31 Simplicity
7 Simplify/Simplified
75 Simple
25. UPerform Your Agile and Project Performance Partner
Image from: www.logoblog.org
26. UPerform Your Agile and Project Performance Partner
PPPTV - 敏捷领导力关注模型
Technical
Excellence
People
Development
Process
Op6miza6on
Product
Discovery
Value-‐Driven
Outcome
Copyright 2011 UPerform & 李国彪
27. UPerform Your Agile and Project Performance Partner
Simplicity: People Development
Image from Linda Rising’s Agile Mindset Presentation
Copyright 2011 UPerform & 李国彪
28. UPerform Your Agile and Project Performance Partner
Simplicity: People Development
• 聪明的“傻子”总愿意把事情搞大,弄复杂。我们需要一种
天分以及极大的勇气去把事情做简单。– 爱因斯坦
• 很容易就会有一个复杂的想法。但是有一个简单想法却十
分困难。 - Carver Mead
• To be really simple, you have to go really deep - 乔布斯
• 把简单的事情做好就是不简单。- 海尔张瑞敏
• 专注(Focus)
• “大”和“多”不能成为借口
• 自管理、自组织团队
• 从自身做起
• 初心 (Beginner’s Mind) (“Stay Hungry, Stay Foolish” -乔
布斯)
• 透明性 (Transparency)
Copyright 2011 UPerform & 李国彪
29. UPerform Your Agile and Project Performance Partner
Simplicity: Product Discovery
Copyright 2011 UPerform & 李国彪
Image from Apple.com
30. UPerform Your Agile and Project Performance Partner
Simplicity: Product Discovery
• Minimally Shippable Product 时刻追求最小的可发布
产品
• 产品Backlog排优先级/勇于舍弃(say “No”)/专注
• 使用用户故事 (放弃前期过度的需求分析)
• 尝试 Kano 模型
• 最好的最简洁的用户体验 (最自然的)
• Make it Simple, Really Simple – 乔布斯
• To be really simple, you have to go really deep - 乔
布斯
• Simplicity is the ultimate sophistication – 达芬奇
• 达致简单是创造性的艺术
Copyright 2011 UPerform & 李国彪
31. UPerform Your Agile and Project Performance Partner
Simplicity: Process Optimization
Copyright 2011 UPerform & 李国彪
34. UPerform Your Agile and Project Performance Partner
Simplicity: 简化你的组织
Copyright 2011 UPerform & 李国彪
35. UPerform Your Agile and Project Performance Partner
Simplicity: 轻装出行(Kent Beck)
Copyright 2011 UPerform & 李国彪
36. UPerform Your Agile and Project Performance Partner
Simplicity: 轻装出行(Kent Beck)
我们所维护的工件应该是:
• Few 少
• Simple 简单
• Valuable 有价值
Copyright 2011 UPerform & 李国彪
37. UPerform Your Agile and Project Performance Partner
Simplicity: Technical Excellence
“the hallmark of the professional
programmer is not in the complexity of
the code they produce, but rather in
the simplicity. When you can take a
complex problem, and solve it with
simple code, you are a professional
programmer”
Daryl Banttari webapper.net
Copyright 2011 UPerform & 李国彪
40. UPerform Your Agile and Project Performance Partner
Simplicity: XP-from Kent Beck
The 2nd XP value is simplicity:
“What is the simplest thing that could
possibly work?”
“XP is making a bet. It is betting that it is
better to do a simple thing today and pay a
little more tomorrow to change it if it needs
it, than to do a more complicated thing
today that may never be used anyway.”
41. UPerform Your Agile and Project Performance Partner
Welch’s 5 Keys
• Candor—Everybody should look for opportunities to make
change rather than issue rosy forecasts and hope for the best.
• Simplicity—You’ve got to have it if you want your organization
to be effective.
• Self-confidence— “Frightened, nervous managers use
thick, convoluted planning books and busy slides.” Welch notes.
• Two-way communication
• Evaluation and reward—We have to know if our
people are open and self-confident, if they believe in honest
communication and quick action.
Speed, Simplicity, Self-Confidence: An Interview with Jack Welch, by Noel Tichy and Ram Charan, Harvard Business
Review, 1989
42. UPerform Your Agile and Project Performance Partner
Simplicity: Technical Excellence
• 你永远不会需要它 You Aren't Gonna
Need It (YAGNI)
• 不要重复自己 DRY (Don’t Repeat
Yourself)
• 好的代码就是文档 Self-Documenting Code
– 在写代码注释之前,问一下你的伙伴怎样能够
把代码写的不言自明
– 注释好像不错,但是它是不是说明你的代码有
些复杂了
43. UPerform Your Agile and Project Performance Partner
PPPTV - 敏捷领导力关注模型
Technical
Excellence
People
Development
Process
Op6miza6on
Product
Discovery
Value-‐Driven
Outcome
Copyright 2011 UPerform & 李国彪
44. UPerform Your Agile and Project Performance Partner
Sense & Simplicity 精于心 简于形
---Philips
45. UPerform Your Agile and Project Performance Partner
完美,并不是不能再加,
而是不能再减。
(无名氏)
46. UPerform Your Agile and Project Performance Partner
新浪微博:@李国彪
Bill.Li@ScrumChina.com
(Twitter)