Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo?
•
2 likes•590 views
The document discusses whether Agile needs to die or has already died. It covers the evolution of software development approaches from Waterfall to newer methods like Scrum, XP, Kanban, and DevOps. It argues that principles are more important than practices and that Agile needs to adapt to new economic and technological realities like mobile, startups, and complexity of modern software.
Report
Share
Report
Share
Download to read offline
Recommended
DOES15 - Ramona Jackson and Aji Rajappan - Continuous Delivery at Cisco IT
Cisco IT implemented a large-scale continuous delivery transformation to improve software quality, optimize costs, and accelerate time to capability. Their approach included establishing a core team, adopting agile methodologies, automating testing, embedding subject matter experts, and grouping applications into adoption waves. Key results were increased agile adoption rates, productivity savings, and measurable business value. The transformation required addressing needs like environment refreshes and concurrent code versions, as well as focusing on areas like tools, training, processes, and culture change.
Architecting Atlassian for Healthcare and FDA Compliance
The US medical device, pharmaceutical, and healthcare industries have stringent regulatory norms to protect patients' safety and privacy. They are under constant pressure to provide innovative solutions for improved personal care while staying compliant with the ever-evolving regulatory landscape.
But how do you bridge the gap between agile development for innovation and audit readiness for compliance? In this session, Sundar Selvatharasu and Andy Spoone of Sierra Labs will share how they use Jira both for engineering innovation and as a quality management system for compliance with GXP, GDPR, and HIPAA.
Agile Service Management: An introduction - Bas Blanken
With the speed of technological development and the growing dependence on technology, it is increasingly important for organisations to be able to change rapidly. More and more organisations are opting for agile transitions, scrum and kanban boards. But what does it actually mean to be ‘agile’ as an organisation? And how does this fit in with the world of service management? In this presentation you will get to know the agile mindset, and you will learn what you can already start with the next day.
DevOps vs. ITIL Epic Struggle or Slamdunk
This document discusses DevOps vs ITIL and how their goals differ. DevOps focuses on resilience, mean time to recovery, pulling work, risk taking and flow, while ITIL emphasizes strength, mean time between failures, pushing work, safety and queuing work. It notes the business perspective is that IT moves too slowly, is unresponsive and projects are behind schedule. Release management is discussed as an ITIL process to help avoid introducing problems during new releases. The document advocates managing various lifecycles together to better deliver value and addresses relationships between processes and products.
Bring Your Own People Centric Business Processes
Workflow is getting more important in an internet connected world. Employees become consumers and they just take the best tool for the job. Learn how Effektif enables anyone to build their own workflows.
DevOps feedback loops
This document discusses DevOps feedback loops and the importance of closing the loop between development and operations. It provides examples of where feedback comes from in operations, including from people and machines, and where feedback needs to go in development, such as to developers and development systems. The key message is that closing the feedback loop through continuous feedback is critical for DevOps in order to optimize software development and address issues quickly before they become bigger problems.
DOES16 London - Scott Potter - DevOps: To Autonomy and Beyond
Scott Potter, (former) Head of Digital Engineering, News UK
Transitioning to an organisational structure, a set of skills and capabilities and the desired motivation & behaviours is just the start. Once you start reaping the benefits, your job isn't done.
Scott shares some of his own experiences from the journey that he and his teams took through a DevOps transition, and the role that management took to support the creation of independent teams.
Enterprise feature streams
From Value Stream Management to Feature Stream Enablement
- The tech and tools don't matter (Use the in-place toolchain...Jira, Jenkins & Github...)
- The process and methodology that work best for you (Agile, Scrum, Kanban, Lean, XP, Waterfall...)
- Teams can finally see work with full transparency (full-stream, full-stack, full-flow...all tied to KPIs and OKRs)
Recommended
DOES15 - Ramona Jackson and Aji Rajappan - Continuous Delivery at Cisco IT
Cisco IT implemented a large-scale continuous delivery transformation to improve software quality, optimize costs, and accelerate time to capability. Their approach included establishing a core team, adopting agile methodologies, automating testing, embedding subject matter experts, and grouping applications into adoption waves. Key results were increased agile adoption rates, productivity savings, and measurable business value. The transformation required addressing needs like environment refreshes and concurrent code versions, as well as focusing on areas like tools, training, processes, and culture change.
Architecting Atlassian for Healthcare and FDA Compliance
The US medical device, pharmaceutical, and healthcare industries have stringent regulatory norms to protect patients' safety and privacy. They are under constant pressure to provide innovative solutions for improved personal care while staying compliant with the ever-evolving regulatory landscape.
But how do you bridge the gap between agile development for innovation and audit readiness for compliance? In this session, Sundar Selvatharasu and Andy Spoone of Sierra Labs will share how they use Jira both for engineering innovation and as a quality management system for compliance with GXP, GDPR, and HIPAA.
Agile Service Management: An introduction - Bas Blanken
With the speed of technological development and the growing dependence on technology, it is increasingly important for organisations to be able to change rapidly. More and more organisations are opting for agile transitions, scrum and kanban boards. But what does it actually mean to be ‘agile’ as an organisation? And how does this fit in with the world of service management? In this presentation you will get to know the agile mindset, and you will learn what you can already start with the next day.
DevOps vs. ITIL Epic Struggle or Slamdunk
This document discusses DevOps vs ITIL and how their goals differ. DevOps focuses on resilience, mean time to recovery, pulling work, risk taking and flow, while ITIL emphasizes strength, mean time between failures, pushing work, safety and queuing work. It notes the business perspective is that IT moves too slowly, is unresponsive and projects are behind schedule. Release management is discussed as an ITIL process to help avoid introducing problems during new releases. The document advocates managing various lifecycles together to better deliver value and addresses relationships between processes and products.
Bring Your Own People Centric Business Processes
Workflow is getting more important in an internet connected world. Employees become consumers and they just take the best tool for the job. Learn how Effektif enables anyone to build their own workflows.
DevOps feedback loops
This document discusses DevOps feedback loops and the importance of closing the loop between development and operations. It provides examples of where feedback comes from in operations, including from people and machines, and where feedback needs to go in development, such as to developers and development systems. The key message is that closing the feedback loop through continuous feedback is critical for DevOps in order to optimize software development and address issues quickly before they become bigger problems.
DOES16 London - Scott Potter - DevOps: To Autonomy and Beyond
Scott Potter, (former) Head of Digital Engineering, News UK
Transitioning to an organisational structure, a set of skills and capabilities and the desired motivation & behaviours is just the start. Once you start reaping the benefits, your job isn't done.
Scott shares some of his own experiences from the journey that he and his teams took through a DevOps transition, and the role that management took to support the creation of independent teams.
Enterprise feature streams
From Value Stream Management to Feature Stream Enablement
- The tech and tools don't matter (Use the in-place toolchain...Jira, Jenkins & Github...)
- The process and methodology that work best for you (Agile, Scrum, Kanban, Lean, XP, Waterfall...)
- Teams can finally see work with full transparency (full-stream, full-stack, full-flow...all tied to KPIs and OKRs)
How to become a DevOps
What this term means exactly? Is it a movement? A new process or technology? A job title? Or just a way of thinking? Let's find out!
Scaling Agile to the Enterprise: 5 Secrets to Unlocking the Strategic Value o...
The document discusses the challenges that large organizations face in achieving enterprise agility. It outlines 5 secrets to unlocking enterprise agility: 1) take a systems approach to optimization rather than just optimizing teams locally, 2) know when to commit to transformations and when to abandon them, 3) successful transformations require both top-down and bottom-up approaches, 4) teams may resist scaling so the right metrics need to be used, and 5) knowledge must flow seamlessly across the organization for large-scale transformations to succeed. Achieving enterprise agility can provide benefits like stronger innovation, increased profits, and faster delivery, but few organizations have achieved it due to the complex challenges involved.
Waterfall-ITIL vs Agile-DevOps
Why DevOps is perfect for Modern IT organizations leveraging Agile and Why Waterfall is perfect for Legacy IT ITIL organizations
DevOps Swim Lanes - Silo Org Change Challenges
The document compares the traditional waterfall model and siloed approach to development (IT) with the DevOps approach. With waterfall and silos, components were developed and managed in isolation by specialist teams, which led to quality issues, delays, and lack of collaboration between teams. DevOps embraces a collaborative culture with shared goals and optimized system flows between development, operations, and other functions. This approach leverages practices like automation, cloud technologies, and continuous integration/delivery to allow for faster innovation and higher quality through greater transparency, accountability, and opportunities for feedback and improvement.
Agile and DevOps revealed
Agile focuses on mindset, culture, and stability while responding quickly to market changes. DevOps extends Agile by adding automation. DevOps is characterized as CALMS - Culture from Agile, Automation from DevOps, Lean from Agile, Measurement from DevOps, and Sharing from Agile. Key principles include continuous delivery, continuous integration, deploying in small batches frequently, and automating to enable continuous delivery.
Inside Atlassian: Focusing on Customer Outcomes in Spite of Complexity
How familiar does this scenario sound?
Despite their best efforts, product managers are micro-managing too many features in development, meanwhile developers are waiting on designers. Support engineers aren't sure what shipped this week, and new features can't be released because tech writers weren't aware of them until they were nearly completed. The exec team is eager to learn how the last features are affecting new user uptake, but it's not up to expectations because marketing never understood who it was for, or why it was built.
Join us for a peek behind-the-scenes at Atlassian. And learn how we juggle all of these efforts across the DevOps cycle, and validate features early and often—all while focusing on delivering real customer value.
After Agile, DevOps, and Lean IT: Modern Methodology in the Age of Disruption
In an age of disruption, increasingly complex and chaotic problems demand emergent or completely novel practices. Decades-old practices no longer work, raising difficult questions about the role of management in a world being disrupted by technology:
How do we embrace diversity and inclusion for resilience without sacrificing efficiency or create psychological safety?
Navigate external market forces and internal cultural changes?
This session will go beyond Agile, DevOps, and Lean IT to share a novel perspective on your roles in in a rapidly changing technological landscape to help you build a future-proof organization.
Feedback loops - the second way towards the world of DevOps
The three ways define a philosophical journey to an unfinished world of IT development. Amplifying feedback loops, the second way, is about shortening and amplifying any bottlenecks preventing feedback to close a full circuit of continual improvement.
Open Source BPM in Java
An overview of Java tools for Business Process Management. Presented at the Pasadena JUG on June 28, 2010.
Blending ITIL, Agile, DevOps and LeanUX at Auto Trader UK
Presentation on how we work at Auto Trader UK from #PINK16 IT Service Management conference in Las Vegas.
Blending ITIL, Agile, DevOps and LeanUX at Auto Trader UK
A Brave Journey in Merge Waters: How Paysafe Consolidated Their Atlassian Tools
After a large merger in mid-2015, Paysafe, a fintech company providing payment solutions worldwide, had several instances of Atlassian products spread across the globe. With 4 JIRA Software, 3 Confluence, 2 Bitbucket, 2 Bamboo and 2 HipChat server instances, our team made the bold decision to unify them into a single instance for each product. Further complicating the already daunting task were 6 active directories of users, a diverse set of admins, and different levels of organizational maturity across our development, product, and business teams. A year after we set sail, Paysafe now has a single production instance of the majority of these products, with little impact to users, no data loss, and improved performance. In this session, we will outline our journey into the uncharted waters of consolidation focusing on our 4 JIRA instances, as this was the most critical and challenging mission in our quest. Together with our Atlassian Solution Partner, Nemetschek Bulgaria, we will share tips and best practices on limiting downtime, eliminating the risk for loss of vital data, and the unification of user management.
Radostina Kavrakova, IT Product Support Manager, Paysafe Group plc
George Stoyanov, Senior Software Engineer & Project Leader, Nemetschek Bulgaria
Jira Service Desk for Internal Developer Support: It’s Not Just for IT Anymore!
IT isn’t the only service organization that struggles to keep pace with growing development teams—Build and Release, Tools, and other development operations teams face the same challenges.
Learn how Karen Clark, DevOps Lead for Splunk's Internal Engineering Effectiveness team leveraged the power of Jira Service Desk to support internal customers and helped scale a growing organization. From gaining access to code repositories, to handling "on fire" blocking issues with production CI/CD environments, see which problems Jira Service Desk helped solve (and what it didn't), and the challenges they faced along the way.
Experiences joining Agile and ITIL for DevOps
To many people ITIL seems like the antithesis of Agile, with process-heavy, manual checks and approval gates a blocker to rapid delivery. However, at its core ITIL recommends iterative and continual improvement of software services based on the ‘Plan, Do, Check, Act’ (PDCA) cycle of Deming, an approach also central to DevOps. In this talk we’ll explore how – if implemented appropriately – ITIL and Agile can complement each other for a DevOps approach to iterative evolution of successful software systems.
From our talk at Unicom DevOps Summit on 26th March 2015 in London.
Kathleen Wilson - Evolve Cloud Operations and Enable Agile with Modern Servic...
Hybrid cloud disrupts IT with not so obvious roles, responsibilities, and activities. Legacy ITSM practices and siloed IT teams are challenged to adopt and gain immediate value of Cloud. Organizations must evolve conventional thinking and transition to modern service management practices, inclusive of Agile and DevOps, aimed at accelerating digital transformation. Microsoft Modern Service Management was conceived with this is mind, taking leading-edge value based approach to service management that helps organizations unlock the value of their Microsoft Cloud investment. This session shares how Microsoft’s Customers have benefitted from adopting MSM Principles and how you modernize your IT practices.
A Product Manager's Place in a DevOps World
Today's world is a DevOps one, and as a Product Manager that means you're part of the dev team. As teams transition from building products to running services, you must adapt your role as teams embrace DevOps and create dedicated Site Reliability Engineering (SRE) teams.
Consider these questions:
What's your role during an incident?
How do you communicate to customers?
Are you incorporating reliability metrics into your product roadmap?
The good news is, you can contribute to running services just as much as building products. In this talk, learn how Product Managers on the JIRA team contribute to incident management and review, support a green build culture, plan for reliability, and roll out features and experiments in a services-first world.
Dave Meyer, Senior Product Manager, Atlassian
Dan Greening, Шаблоны лидерства в Agile: The Agile Way of Doing
В Agile у нас большие амбиции, но не хватает дисциплины. Мы часто говорим об Agile командах, людях, департаментах, организациях, политических компаниях, как если бы определения Agile было бы очевидным. Да, ещё в Agile манифесте и его принципах оно описано для команд разработки программного обеспечения. Кроме того, многие CEO определяют насколько они Agile, потому что «мы можем переключать работу команд по щелчку» или потому что «мы можем делать недельные спринты», но их команды всё также не могут поставлять работающий продукт быстро и постоянно увеличивают технический долг или полностью измотаны. Некоторые аджайлисты говорят «сущности» Agile, вроде 5 ценностей Scrum: уважение, ответственность, фокусировка, смелость и открытость. Но эти ценности не говорят нам, что делать.
Они задают границы Agile, как хорошая экономическая наука с небольшим набором концепций: способности быстро разбираться, адаптироваться и создавать в экономическом хаосе. Вы увидите, что Agile – это определённо «делать» до того, как «быть». Вы узнаете несколько простых способов проверить насколько Agile люди, команды и компании. Все Agile методологии (Scrum, XP, SAFe, Lean/Kanban, GTD, PDSA/PDCA, Quantified Self и Pomodoro) включают практики, которые входят в «Базовые Agile шаблоны», в то время как водопадные методологии противоречат этим шаблонам:
• Измерение экономического результата,
• Адаптивные эксперименты для совершенствования,
• Ограничение задач в работе (WIP),
• Коллективная ответственность,
• Систематическое решение проблем.
Мы изучим эти базовые шаблоны и некоторые интересные под-шаблоны, такие как цикл обратной связи, Backlog, Chunking, картирование корневых причин и информационные радиаторы. Мы поговорим о значении о практике часто забываемой в Lean/Kanban – о ретроспективе. Лидеры всех уровней должны хорошо понимать Agile, чтобы проводить эффективный командный коучинг и ограждать процесс и команду от тлетворных влияний. Лидеры могут с лёгкостью применить эти просто масштабируемые шаблоны в любой творческой отрасли: маркетинг, стратегические проекты, личные проекты и, вы догадались, в разработке программного обеспечения.
Ultimate Dogfooding: Behind the Scenes of Building the New Jira
At Atlassian, we’ve been dog-fooding Jira since the beginning of time. This means we get to use every feature and improvement firsthand before it gets delivered to you. Building the new Jira, this posed an interesting challenge – we had to get everyone moving to the new experience.
In this talk, we’ll take you through our journey of getting everyone on-board onto new Jira. There will be a guided tour on how to best use the new Jira for the full cycle of product development. By the end of this session, you’ll know how to make new Jira work for your team and not the other way round.
Agile and Continuous Delivery for Audits and Exams - DC Continuous Delivery M...
The document provides tips for auditors and examiners to better prepare for audits when using agile and continuous delivery practices. It recommends socializing plans for process changes to avoid surprises. It also suggests demonstrating expertise in agile and continuous delivery through training and certifications. Continuous delivery practices like infrastructure as code, static code analysis, automated testing, and repository management make the development process more auditable. The tips emphasize digitizing documentation, logging pipeline activity, and capturing metrics to demonstrate maturity. Ensuring quality practices like keeping QA involved, logging deployments, and code reviews with pull requests can help pass audits. Finally, it recommends getting ahead of outstanding risks like access controls and separation of duties when using tools like Jenkins and Git
The Evolution of Agile Portfolio Management for Scaled Agile Success
With the right tools and mindset, scaling Agile throughout your IT organization can be a painless process. As the market evolves from post-it notes to whiteboards and beyond, the next frontier is finding the right tools that support Agile not only across teams, but also through various levels of hierarchy. The right tools will support not only team members in flowing work across their Kanban boards, but also will support the executive level as they look for at-a-glance updates on the progress and blockers of key initiatives.
From Dev to Ops, all teams within an IT organization should be working towards the same goal -- fast delivery of value to the customer -- and the benefits of Agile can help them get there. But this is not possible with a disconnected toolchain. Agile must impact the whole end-to-end workflow.
This webinar discusses how your organization can enable scaled Agile success by:
- Aligning team priorities around the common goals of an Agile transformation
- Increasing visibility of project status and compliance with cross tool traceability and reporting
- Creating and managing an integrated value stream that can scale to hundreds of projects in minutes
Harnessing Your Product Manager Superpowers with Trello, Confluence, and Jira
Whether you're a product manager, product owner, or a cat herder, creating a stellar product takes skill. The list is endless—from aligning stakeholders to creating a clear vision and specifications, planning sprints, measuring success and everything in-between.
In this session, we'll share how to extend the power and flexibility of Atlassian tools for your team. From inception, to planning, to building, learn the battle-tested tips from our own Atlassian teams to ensure that you not only build the product right, but also build the right product.
Stream Patterns
The document discusses streaming data architectures and technologies. It mentions using Kafka and Spark with Cassandra for streaming analytics. Some key applications are client side joins, analytics, machine learning, and notifications/alerts. It also discusses stream processing engines, client side joins, stream aggregation, technology evolution, and data pipelines. The principal software architect thanks the audience at the end of the presentation.
Team tools
O documento discute brevemente ferramentas ágeis para equipes, incluindo kanban, melhoria contínua, métricas, grandes gráficos visíveis e retrospectivas.
More Related Content
What's hot
How to become a DevOps
What this term means exactly? Is it a movement? A new process or technology? A job title? Or just a way of thinking? Let's find out!
Scaling Agile to the Enterprise: 5 Secrets to Unlocking the Strategic Value o...
The document discusses the challenges that large organizations face in achieving enterprise agility. It outlines 5 secrets to unlocking enterprise agility: 1) take a systems approach to optimization rather than just optimizing teams locally, 2) know when to commit to transformations and when to abandon them, 3) successful transformations require both top-down and bottom-up approaches, 4) teams may resist scaling so the right metrics need to be used, and 5) knowledge must flow seamlessly across the organization for large-scale transformations to succeed. Achieving enterprise agility can provide benefits like stronger innovation, increased profits, and faster delivery, but few organizations have achieved it due to the complex challenges involved.
Waterfall-ITIL vs Agile-DevOps
Why DevOps is perfect for Modern IT organizations leveraging Agile and Why Waterfall is perfect for Legacy IT ITIL organizations
DevOps Swim Lanes - Silo Org Change Challenges
The document compares the traditional waterfall model and siloed approach to development (IT) with the DevOps approach. With waterfall and silos, components were developed and managed in isolation by specialist teams, which led to quality issues, delays, and lack of collaboration between teams. DevOps embraces a collaborative culture with shared goals and optimized system flows between development, operations, and other functions. This approach leverages practices like automation, cloud technologies, and continuous integration/delivery to allow for faster innovation and higher quality through greater transparency, accountability, and opportunities for feedback and improvement.
Agile and DevOps revealed
Agile focuses on mindset, culture, and stability while responding quickly to market changes. DevOps extends Agile by adding automation. DevOps is characterized as CALMS - Culture from Agile, Automation from DevOps, Lean from Agile, Measurement from DevOps, and Sharing from Agile. Key principles include continuous delivery, continuous integration, deploying in small batches frequently, and automating to enable continuous delivery.
Inside Atlassian: Focusing on Customer Outcomes in Spite of Complexity
How familiar does this scenario sound?
Despite their best efforts, product managers are micro-managing too many features in development, meanwhile developers are waiting on designers. Support engineers aren't sure what shipped this week, and new features can't be released because tech writers weren't aware of them until they were nearly completed. The exec team is eager to learn how the last features are affecting new user uptake, but it's not up to expectations because marketing never understood who it was for, or why it was built.
Join us for a peek behind-the-scenes at Atlassian. And learn how we juggle all of these efforts across the DevOps cycle, and validate features early and often—all while focusing on delivering real customer value.
After Agile, DevOps, and Lean IT: Modern Methodology in the Age of Disruption
In an age of disruption, increasingly complex and chaotic problems demand emergent or completely novel practices. Decades-old practices no longer work, raising difficult questions about the role of management in a world being disrupted by technology:
How do we embrace diversity and inclusion for resilience without sacrificing efficiency or create psychological safety?
Navigate external market forces and internal cultural changes?
This session will go beyond Agile, DevOps, and Lean IT to share a novel perspective on your roles in in a rapidly changing technological landscape to help you build a future-proof organization.
Feedback loops - the second way towards the world of DevOps
The three ways define a philosophical journey to an unfinished world of IT development. Amplifying feedback loops, the second way, is about shortening and amplifying any bottlenecks preventing feedback to close a full circuit of continual improvement.
Open Source BPM in Java
An overview of Java tools for Business Process Management. Presented at the Pasadena JUG on June 28, 2010.
Blending ITIL, Agile, DevOps and LeanUX at Auto Trader UK
Presentation on how we work at Auto Trader UK from #PINK16 IT Service Management conference in Las Vegas.
Blending ITIL, Agile, DevOps and LeanUX at Auto Trader UK
A Brave Journey in Merge Waters: How Paysafe Consolidated Their Atlassian Tools
After a large merger in mid-2015, Paysafe, a fintech company providing payment solutions worldwide, had several instances of Atlassian products spread across the globe. With 4 JIRA Software, 3 Confluence, 2 Bitbucket, 2 Bamboo and 2 HipChat server instances, our team made the bold decision to unify them into a single instance for each product. Further complicating the already daunting task were 6 active directories of users, a diverse set of admins, and different levels of organizational maturity across our development, product, and business teams. A year after we set sail, Paysafe now has a single production instance of the majority of these products, with little impact to users, no data loss, and improved performance. In this session, we will outline our journey into the uncharted waters of consolidation focusing on our 4 JIRA instances, as this was the most critical and challenging mission in our quest. Together with our Atlassian Solution Partner, Nemetschek Bulgaria, we will share tips and best practices on limiting downtime, eliminating the risk for loss of vital data, and the unification of user management.
Radostina Kavrakova, IT Product Support Manager, Paysafe Group plc
George Stoyanov, Senior Software Engineer & Project Leader, Nemetschek Bulgaria
Jira Service Desk for Internal Developer Support: It’s Not Just for IT Anymore!
IT isn’t the only service organization that struggles to keep pace with growing development teams—Build and Release, Tools, and other development operations teams face the same challenges.
Learn how Karen Clark, DevOps Lead for Splunk's Internal Engineering Effectiveness team leveraged the power of Jira Service Desk to support internal customers and helped scale a growing organization. From gaining access to code repositories, to handling "on fire" blocking issues with production CI/CD environments, see which problems Jira Service Desk helped solve (and what it didn't), and the challenges they faced along the way.
Experiences joining Agile and ITIL for DevOps
To many people ITIL seems like the antithesis of Agile, with process-heavy, manual checks and approval gates a blocker to rapid delivery. However, at its core ITIL recommends iterative and continual improvement of software services based on the ‘Plan, Do, Check, Act’ (PDCA) cycle of Deming, an approach also central to DevOps. In this talk we’ll explore how – if implemented appropriately – ITIL and Agile can complement each other for a DevOps approach to iterative evolution of successful software systems.
From our talk at Unicom DevOps Summit on 26th March 2015 in London.
Kathleen Wilson - Evolve Cloud Operations and Enable Agile with Modern Servic...
Hybrid cloud disrupts IT with not so obvious roles, responsibilities, and activities. Legacy ITSM practices and siloed IT teams are challenged to adopt and gain immediate value of Cloud. Organizations must evolve conventional thinking and transition to modern service management practices, inclusive of Agile and DevOps, aimed at accelerating digital transformation. Microsoft Modern Service Management was conceived with this is mind, taking leading-edge value based approach to service management that helps organizations unlock the value of their Microsoft Cloud investment. This session shares how Microsoft’s Customers have benefitted from adopting MSM Principles and how you modernize your IT practices.
A Product Manager's Place in a DevOps World
Today's world is a DevOps one, and as a Product Manager that means you're part of the dev team. As teams transition from building products to running services, you must adapt your role as teams embrace DevOps and create dedicated Site Reliability Engineering (SRE) teams.
Consider these questions:
What's your role during an incident?
How do you communicate to customers?
Are you incorporating reliability metrics into your product roadmap?
The good news is, you can contribute to running services just as much as building products. In this talk, learn how Product Managers on the JIRA team contribute to incident management and review, support a green build culture, plan for reliability, and roll out features and experiments in a services-first world.
Dave Meyer, Senior Product Manager, Atlassian
Dan Greening, Шаблоны лидерства в Agile: The Agile Way of Doing
В Agile у нас большие амбиции, но не хватает дисциплины. Мы часто говорим об Agile командах, людях, департаментах, организациях, политических компаниях, как если бы определения Agile было бы очевидным. Да, ещё в Agile манифесте и его принципах оно описано для команд разработки программного обеспечения. Кроме того, многие CEO определяют насколько они Agile, потому что «мы можем переключать работу команд по щелчку» или потому что «мы можем делать недельные спринты», но их команды всё также не могут поставлять работающий продукт быстро и постоянно увеличивают технический долг или полностью измотаны. Некоторые аджайлисты говорят «сущности» Agile, вроде 5 ценностей Scrum: уважение, ответственность, фокусировка, смелость и открытость. Но эти ценности не говорят нам, что делать.
Они задают границы Agile, как хорошая экономическая наука с небольшим набором концепций: способности быстро разбираться, адаптироваться и создавать в экономическом хаосе. Вы увидите, что Agile – это определённо «делать» до того, как «быть». Вы узнаете несколько простых способов проверить насколько Agile люди, команды и компании. Все Agile методологии (Scrum, XP, SAFe, Lean/Kanban, GTD, PDSA/PDCA, Quantified Self и Pomodoro) включают практики, которые входят в «Базовые Agile шаблоны», в то время как водопадные методологии противоречат этим шаблонам:
• Измерение экономического результата,
• Адаптивные эксперименты для совершенствования,
• Ограничение задач в работе (WIP),
• Коллективная ответственность,
• Систематическое решение проблем.
Мы изучим эти базовые шаблоны и некоторые интересные под-шаблоны, такие как цикл обратной связи, Backlog, Chunking, картирование корневых причин и информационные радиаторы. Мы поговорим о значении о практике часто забываемой в Lean/Kanban – о ретроспективе. Лидеры всех уровней должны хорошо понимать Agile, чтобы проводить эффективный командный коучинг и ограждать процесс и команду от тлетворных влияний. Лидеры могут с лёгкостью применить эти просто масштабируемые шаблоны в любой творческой отрасли: маркетинг, стратегические проекты, личные проекты и, вы догадались, в разработке программного обеспечения.
Ultimate Dogfooding: Behind the Scenes of Building the New Jira
At Atlassian, we’ve been dog-fooding Jira since the beginning of time. This means we get to use every feature and improvement firsthand before it gets delivered to you. Building the new Jira, this posed an interesting challenge – we had to get everyone moving to the new experience.
In this talk, we’ll take you through our journey of getting everyone on-board onto new Jira. There will be a guided tour on how to best use the new Jira for the full cycle of product development. By the end of this session, you’ll know how to make new Jira work for your team and not the other way round.
Agile and Continuous Delivery for Audits and Exams - DC Continuous Delivery M...
The document provides tips for auditors and examiners to better prepare for audits when using agile and continuous delivery practices. It recommends socializing plans for process changes to avoid surprises. It also suggests demonstrating expertise in agile and continuous delivery through training and certifications. Continuous delivery practices like infrastructure as code, static code analysis, automated testing, and repository management make the development process more auditable. The tips emphasize digitizing documentation, logging pipeline activity, and capturing metrics to demonstrate maturity. Ensuring quality practices like keeping QA involved, logging deployments, and code reviews with pull requests can help pass audits. Finally, it recommends getting ahead of outstanding risks like access controls and separation of duties when using tools like Jenkins and Git
The Evolution of Agile Portfolio Management for Scaled Agile Success
With the right tools and mindset, scaling Agile throughout your IT organization can be a painless process. As the market evolves from post-it notes to whiteboards and beyond, the next frontier is finding the right tools that support Agile not only across teams, but also through various levels of hierarchy. The right tools will support not only team members in flowing work across their Kanban boards, but also will support the executive level as they look for at-a-glance updates on the progress and blockers of key initiatives.
From Dev to Ops, all teams within an IT organization should be working towards the same goal -- fast delivery of value to the customer -- and the benefits of Agile can help them get there. But this is not possible with a disconnected toolchain. Agile must impact the whole end-to-end workflow.
This webinar discusses how your organization can enable scaled Agile success by:
- Aligning team priorities around the common goals of an Agile transformation
- Increasing visibility of project status and compliance with cross tool traceability and reporting
- Creating and managing an integrated value stream that can scale to hundreds of projects in minutes
Harnessing Your Product Manager Superpowers with Trello, Confluence, and Jira
Whether you're a product manager, product owner, or a cat herder, creating a stellar product takes skill. The list is endless—from aligning stakeholders to creating a clear vision and specifications, planning sprints, measuring success and everything in-between.
In this session, we'll share how to extend the power and flexibility of Atlassian tools for your team. From inception, to planning, to building, learn the battle-tested tips from our own Atlassian teams to ensure that you not only build the product right, but also build the right product.
What's hot (20)
Scaling Agile to the Enterprise: 5 Secrets to Unlocking the Strategic Value o...
Scaling Agile to the Enterprise: 5 Secrets to Unlocking the Strategic Value o...
Inside Atlassian: Focusing on Customer Outcomes in Spite of Complexity
Inside Atlassian: Focusing on Customer Outcomes in Spite of Complexity
After Agile, DevOps, and Lean IT: Modern Methodology in the Age of Disruption
After Agile, DevOps, and Lean IT: Modern Methodology in the Age of Disruption
Feedback loops - the second way towards the world of DevOps
Feedback loops - the second way towards the world of DevOps
Blending ITIL, Agile, DevOps and LeanUX at Auto Trader UK
Blending ITIL, Agile, DevOps and LeanUX at Auto Trader UK
A Brave Journey in Merge Waters: How Paysafe Consolidated Their Atlassian Tools
A Brave Journey in Merge Waters: How Paysafe Consolidated Their Atlassian Tools
Jira Service Desk for Internal Developer Support: It’s Not Just for IT Anymore!
Jira Service Desk for Internal Developer Support: It’s Not Just for IT Anymore!
Kathleen Wilson - Evolve Cloud Operations and Enable Agile with Modern Servic...
Kathleen Wilson - Evolve Cloud Operations and Enable Agile with Modern Servic...
Dan Greening, Шаблоны лидерства в Agile: The Agile Way of Doing
Dan Greening, Шаблоны лидерства в Agile: The Agile Way of Doing
Ultimate Dogfooding: Behind the Scenes of Building the New Jira
Ultimate Dogfooding: Behind the Scenes of Building the New Jira
Agile and Continuous Delivery for Audits and Exams - DC Continuous Delivery M...
Agile and Continuous Delivery for Audits and Exams - DC Continuous Delivery M...
The Evolution of Agile Portfolio Management for Scaled Agile Success
The Evolution of Agile Portfolio Management for Scaled Agile Success
Harnessing Your Product Manager Superpowers with Trello, Confluence, and Jira
Harnessing Your Product Manager Superpowers with Trello, Confluence, and Jira
Viewers also liked
Stream Patterns
The document discusses streaming data architectures and technologies. It mentions using Kafka and Spark with Cassandra for streaming analytics. Some key applications are client side joins, analytics, machine learning, and notifications/alerts. It also discusses stream processing engines, client side joins, stream aggregation, technology evolution, and data pipelines. The principal software architect thanks the audience at the end of the presentation.
Team tools
O documento discute brevemente ferramentas ágeis para equipes, incluindo kanban, melhoria contínua, métricas, grandes gráficos visíveis e retrospectivas.
Tech Evaluation
The document provides guidance on evaluating new technologies for a business. It recommends pursuing easy wins that make things faster, better, cheaper and sexier, while being aware of potential tradeoffs. A thorough evaluation of requirements and proofs-of-concept should be conducted to understand impacts on the core business, time, costs, quality, and future issues before deciding whether to build or buy a new technology solution. Community input may also be part of the evaluation process.
Akka Streams
This document discusses Akka Streams, which is a library for building reactive stream processing applications. It defines key concepts like streams, processing stages, back pressure, and flow control. It also covers topics like stream composition, materialization, using actors in streams, and includes code examples. The document is presented by Diego Pacheco, a principal software architect at Akka Streams.
Microservices
Este documento discute os principais conceitos e benefícios da arquitetura de microserviços, incluindo isolamento de times e recursos para permitir entregas independentes, e eventual consistência para lidar com transações distribuídas.
Apache Cassandra - part 2
This document summarizes Diego Pacheco's presentation on Cassandra. It covers the Cassandra write path, tombstones, compaction strategies, row and bloom filters, SASI indexes, materialized views, counter families, and anti-patterns. It also discusses Cassandra's implementation at Uber using Mesos. The presentation addresses how data is written to disk in immutable SSTables and compacted over time to remove tombstones, and different compaction strategies for various workloads. It explains techniques like row caching, bloom filters, secondary indexes, materialized views and counters.
Viewers also liked (6)
Similar to Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo?
Agile intro stldodn2009
Basic introduction to Agile Methodology from the 2009 Saint Louis Day of Dot Net. Supplement to 2010 STLDODN Presentation for newcomers to the agile methodology
AgileDC15 I'm Using Chef So I'm DevOps Right?
This document provides an overview of DevOps principles and practices. It discusses the rise of DevOps as a movement to improve collaboration between development and operations teams. Common DevOps misconceptions are addressed. The CALMS framework of culture, automation, lean, measurement, and sharing is introduced as guiding principles. A roadmap for DevOps adoption is presented, along with take-home activities. The document aims to educate about DevOps in 3 sentences or less.
DevOps and Agile in an ITSM world
Slides from the workshop run by Claire Agutter and Dave van Herpen from Sogeti at the IT500 conference, Edinburgh, in May 2016
Agile Intro - Saint Louis Day of Dot Net
Introduction to Agility from Saint Louis Day of Dot Net session:
History, Definition, Comparison to Waterfall, Agile methodologies, Myths & Misconceptions, Common failure, & Advanced discussion points.
DevOps-driving-blind
The document discusses how DevOps can help transform enterprises from traditional slow and siloed software development processes to more agile and collaborative processes. It introduces a "Sonar model" to visualize how DevOps establishes feedback loops between development, testing, operations, and business users to continuously improve products and give businesses a competitive advantage. The model shows how Agile development, DevOps practices like continuous integration and delivery, and incorporating long-term business feedback can work together to achieve project, product, and business goals.
Finding The Agile Sweet Spot
Despite increased adoption across industries, many people still have trouble defining and distinguishing between Agile, DevOps and product management. What’s the difference between these practices? Are they competing or complementary?
In this on-demand Agile Leadership Series webinar, we’ll explore what the Agile mindset is and how to develop it, taking a deep dive into the technical practices needed to build in quality at every step of the development process. Learn how, together, these approaches can improve quality and dramatically decrease time to market. We’ll also discuss how product management can help to ensure teams are building the right features for the right users.
What we’ll cover:
Defining Agile, DevOps and product management
The combined value of these approaches (and what happens when one is left out)
How to identify and prevent feature factories, technical debt and feature debt
Strategies for bringing these approaches to your organization
Enterprise Architecture: Part II - Actualizing the Practice
The document discusses actualizing an enterprise architecture (EA) practice at an organization. It describes taking EA from low maturity to high maturity through a three phase journey. The phases include socializing the need for EA, gaining executive sponsorship, and establishing the EA program. It also discusses rethinking the IT department as proactive rather than reactive. Building an EA team with core and extended members is recommended. Quick wins should be shown to gain buy-in and adoption should be driven from top-down and bottom-up.
Agile IT Operatinos - Getting to Daily Releases
Getting to Daily Releases with Agile IT Operations. Devin Hedge, Enterprise Transformation Consultant talks to a group at Triagile about the Six Key Areas to focus on when attempting to transform IT Operations with Lean and Agile principles. The talk covers Service Engineering, IT Operations, and the Tier 1 Support/NOC organizations. Kanban, Service Management (ITSM), and what it means to have a DevOps orientation.
Agile for developers
Scrum and agile frameworks provide several benefits for developers:
1) Success - Studies show agile projects have higher success rates than traditional waterfall methods.
2) Improved skills - Working across disciplines through practices like pair programming and code reviews helps developers gain new skills and become more well-rounded.
3) Autonomy - Self-organizing teams are accountable for delivering working software and make their own technical decisions, giving developers more autonomy over their work.
Agile Science
Presentation about the basics of Agile Methodologies and how they can be applied to Scientific Research. This presentation later evolved into the Agile Research method. June 2008
An accessible IT Strategy at CM L2+
Resending a small update on an "accessible IT Strategy for Software Development" (People, Process, Technology, Execution, Delivery with Governance). I.e. No more playing games with fragile (or aino - agile in name only) fit for use for Capability Maturity Level 1 only. Rather this presentation pins down Agile and Scrum method with DevOps and underpinned by ITIL 4 operated at CM Level 2+!
Digital transformation impacts on EA - Sep 2018
This document discusses how digital transformation impacts enterprise architecture and whether enterprise architecture is still relevant. It provides definitions of digital transformation and notes that digital transformation brings about new roles and competencies, a new digital culture, ecosystem disruptors, and breaking down of silos. It discusses how digital transformation may displace the enterprise architecture function or create challenges around existing technology standards, dynamics, methodology, and competencies. The document proposes ways for enterprise architects to stay relevant, such as helping the new digital organization navigate, leading early transformation initiatives, accommodating changes, getting hands-on experience, and finding a "sweet spot" as an enterprise change agent.
Why Agile Fail. *Hint* -it's more than just process
Presented by Zubin Irani, CEO, cPrime & Scot Garrison, Director of Professional Services, Tasktop
A successful Agile transformation requires a combination of people, process and technology, but too often these aspects are treated separately. Agile Coaches insist on remaining tool agnostic, and the agile management software experts often do not know the Agile process. Organizations with successful Agile teams often fail to replicate this success when they attempt to scale these practices throughout the software delivery organization.
To succeed in transforming to Agile, organizations must replace this fragmented approach with one that connects the entire application lifecycle with tools that are tightly integrated and automated to support processes. Join us as we demonstrate how this unified approach allows companies to
speed delivery through real-time collaboration
increase visibility of project status and compliance with cross tool traceability and reporting
encourage the use of specialized tools that support practitioners’ process.
Digital transformation in practice
1) Digital transformation has become imperative for businesses both large and small as customers, suppliers, and competitors increasingly operate in the digital world.
2) Digital technologies enable businesses to extend service delivery, lower operational costs, and enhance customer experiences. Digital transformation changes not just operations but organizational structure, culture, and ways of thinking.
3) The digital transformation program lifecycle involves discovery, alpha, beta, and go-live phases with an agile approach and transparency across processes. Discovery identifies pain points and business needs while alpha explores solutions and develops business cases. Beta implements small pilots for feedback before full go-live rollout.
State of Agile 2017
The document provides an overview of agile software development principles and practices. It discusses benefits of agility such as faster time to market and better responsiveness. Common agile frameworks like Scrum and Kanban are summarized. Extreme programming practices for engineering are outlined. The document also discusses scaling agile through frameworks like SAFe and applying lean principles to software development. Overall it serves as a high-level introduction to agile concepts, methods and roles.
Dev ops of die (
DevOps is a cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals. It focuses on practices like continuous integration, continuous delivery, and continuous deployment to accelerate the development and delivery of desired functionality and fixes. DevOps is not a replacement for frameworks like ITIL and COBIT but rather focuses on how work gets done. It promotes concepts like multi-disciplinary teams, automation, and measuring outcomes.
DevOps or Die. DevOps and ITSM/ITIL
DevOps is a cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals. It focuses on practices like continuous integration, continuous delivery, and continuous deployment to rapidly deliver changes to end users. DevOps helps organizations accelerate lead times, deploy code changes more frequently, and reduce failure rates. It is not a replacement for frameworks like ITIL and COBIT but rather focuses on how work gets done. High-performing companies using DevOps practices see benefits like deploying code 30 times more frequently and reducing failures by 60 times.
DevOps Challenges and Mitigation
This document discusses challenges organizations may face when implementing DevOps and proposes mitigations. The key challenges covered are: 1) Having separate DevOps and SRE teams instead of integrating roles, 2) Prioritizing feature development over DevOps responsibilities like quality and responsiveness, and 3) Collecting too many meaningless metrics and logs without proper use cases. The document recommends rotating team members, empowering SRE, maintaining a DevOps backlog, evaluating metrics per feature, and designing metrics and data retention with proper use cases and regulations in mind. In conclusion, the document emphasizes focusing on DevOps principles and engineering rigor over specific tools.
Visual Studio 2010 Agile Tools (overview)
This document discusses the agile tools available in Visual Studio 2010. It provides an overview of Visual Studio 2010's capabilities for managing the entire software development lifecycle using agile methodologies like Scrum. Key features highlighted include improved support for agile processes like Scrum through templates and work item tracking, reporting and planning tools, and tight integration across the development lifecycle from requirements through deployment. The document argues that Visual Studio 2010's agile tools can help teams overcome complexity, improve quality, increase transparency, facilitate collaboration, and reduce risk through a lightweight and customizable approach.
DevOps: The IT Revolution Era
This document discusses the transition from traditional IT to DevOps. Traditional IT focuses on costs and short-term goals, uses cheap contractors, and lacks innovation. Industry forces like new technologies are driving changes. DevOps aims to transform IT by focusing on business value, reducing lead times, automating processes, and encouraging a culture of collaboration between development and operations teams. DevOps is not a role, team or department but a way of thinking and operating to achieve high performance through a long term vision.
Similar to Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo? (20)
Enterprise Architecture: Part II - Actualizing the Practice
Enterprise Architecture: Part II - Actualizing the Practice
Why Agile Fail. *Hint* -it's more than just process
Why Agile Fail. *Hint* -it's more than just process
More from Diego Pacheco
Naming Things Book : Simple Book Review!
The document discusses principles for naming identifiers in code such as variables, classes, and functions. It notes that naming is important because identifiers make up 70% of code and influence comprehension, recall, and bug fixing time. Good naming follows principles like understandability, using names that describe concepts, and consistency. It provides specific rules for naming classes, variables, functions for conciseness, consistency, and distinguishability. The goal is to use names that are understandable to both current and future engineers working on the code.
Continuous Discovery Habits Book Review.pdf
This document summarizes key points from the book "Continuous Discovery Habits" by Diego Pacheco. It advocates for continuous discovery through an outcome-oriented and customer-centric mindset. Discovery requires the collaboration of product managers, designers, and engineers to iteratively test assumptions and validate ideas with customers. The goal is to ensure teams are creating value for users and addressing their needs, pain points, and desires on an ongoing basis through experimental and visual approaches.
Thoughts about Shape Up
This document discusses the Shape Up methodology for agile software development projects. It introduces Shape Up as similar to Dual Track Agile, with an initial 6-week discovery process. Key aspects of how shaping works include setting boundaries, roughing out elements, addressing risks, writing a pitch, and creating simple breadboarding prototypes. Other topics covered are cutting scope, how the pitch works, using betting tables instead of backlogs, dealing with bugs, and making progress on the whole stack through scope mapping and discovery charts.
Holacracy
This document discusses Holacracy, an alternative organizational structure to traditional hierarchies. It notes that current management structures were designed for factories, while Holacracy is designed for humans. Holacracy eliminates hierarchies and instead focuses on clearly defined roles and circles within an organization. It aims to embrace autonomy through separating people from roles and having roles, not managers, make decisions. While challenging to implement due to issues of power, some companies have adopted aspects of Holacracy.
AWS IAM
This document discusses AWS Identity and Access Management (IAM). It provides an overview of IAM including its ability to provide fine-grained access control and integrate with SAML 2.0 and LDAP. It notes issues with passwords and credentials like entropy and rainbow table attacks. The document outlines IAM roles and policies and recommends making credentials temporary to improve security.
CDKs
This document is a profile for Diego Pacheco, who is a cat's father, head of software architecture, agile coach, SOA/microservices expert, DevOps practitioner, speaker, and author. He has expertise in topics such as Terraform, CDKs, and CDKs code generation and maintains GitHub repositories on these subjects.
Encryption Deep Dive
Encryption Deep Dive: Randomness, Entropy, RNG, PRNG, AES, AES Operational Modes, Data Rotations, Java Encryption APIs, Tradeoffs, challenges, Envelope Encryption, KMS, and much more on all things encryption.
Sec 101
This document profiles Diego Pacheco and provides an overview of key software security principles including defense in depth, the least privilege principle, encryption, TLS and mTLS, misconfiguration and error handling, input sanitization, cross-site scripting (XSS), insecure serialization/deserialization, known vulnerabilities, logging and audit trails, threat analysis, and engineering friction. The document emphasizes applying security best practices to protect customer experience, brand integrity, and compliance while avoiding friction for engineering teams.
Reflections on SCM
Reflections on SCM: DevOps, CI/CD, Branches, Architecture, PRs, and many more considerations and thoughts.
Management: Doing the non-obvious! III
This document discusses various management concepts and techniques, including:
- Biases that can negatively impact decision-making like planning fallacy and availability bias.
- How work is becoming indistinguishable from sabotage due to bureaucracy and predictability.
- The importance of having "skin in the game" and being willing to be wrong to drive change and learning.
- Dealing with scarcity by identifying high and low performance areas and reallocating resources accordingly.
Design is not Subjective
Design is Not Subjective! Software design and Lean UX, Ux, Design Thinking are not that different after all. UML was in the right direction the problem was where we applied. In this video, I will explain why Design is not subjective. Video https://www.youtube.com/watch?v=ijGR6Tbhr54
Architecture & Engineering : Doing the non-obvious!
Diego Pacheco is a software architect, agile coach, and speaker who focuses on non-traditional approaches. Some of his views include that requirements can change and duplication is okay, tests don't always improve design or find bugs, and complexity sometimes needs abstractions but other times they add unnecessary complexity. He also believes teams will always have technical debt so it's important to prioritize fixing quick wins over deep technical issues, and that architecture is about people and enabling teams.
Management doing the non-obvious II
This document discusses various management concepts and principles:
- You cannot regulate failure in complex systems and it is better to focus on recovering from failures rather than trying to predict and prevent them.
- Product teams are more effective than feature teams because they are focused on discovering customer needs rather than having predefined solutions.
- Sharing a vision rather than a detailed roadmap allows for more flexibility and ability to change tactics.
- Psychological safety and an environment where people feel included, safe to learn and contribute, and safe to challenge the status quo is important for teams.
- Discipline is needed to successfully execute digital transformations but often lacks longevity and focus shifts to short term goals.
Testing in production
The document discusses testing in production environments using "dark canaries". Dark canaries involve deploying code changes to a small percentage of real users without their knowledge to test for issues before broad deployment. The key benefits are that it allows testing with real users and traffic in the actual production environment and catching problems early before they affect everyone. Some challenges are potential privacy issues if users are not informed and ensuring changes don't negatively impact the small group of unaware users.
Nine lies about work
The document outlines 9 common lies about work and proposes alternative truths. The lies discussed include that people care most about the company they work for rather than their team, that the best plan wins rather than intelligence in real-time, and that feedback and performance reviews can reliably rate people. The author argues that people primarily care about their team, intelligence is needed to adapt to a dynamic world, and that reviews mostly reflect raters rather than ratees. The truths proposed emphasize caring for one's team, prioritizing real-time intelligence over static plans, and that people can best rate their own experiences.
Management: doing the nonobvious!
This document provides advice and perspectives on management and leadership from Diego Pacheco. Some of the key points discussed include:
- Ego can distort reality and inhibit innovation, so leaders should suppress ego with humility.
- Not all communication needs to happen between all people; structured teams are better models than rigid organization charts.
- Feedback is difficult to give and receive but is important for growth if approached without emotion or defensiveness.
- Scenario modeling and role playing exercises can help train leaders by anticipating problems before they occur.
AI and the Future
The document discusses several topics related to artificial intelligence and the future, including:
1) Whether AI-generated music has soul or not.
2) The possibility of AI judges making faster parallel decisions.
3) Elon Musk's view that we are all already cyborgs.
4) Musk's proposal that augmented humans could regenerate organs and tissues by 2100 through technologies like neuralink.
5) The potential to reengineer humans and expand lifespans to 120-150 years through these technologies.
Dealing with dependencies
This document discusses dealing with dependencies between teams when developing software. It acknowledges that fixed release schedules and monolithic codebases can create issues. Some potential solutions proposed include using contracts and mocks between teams, restructuring code using domain-driven design principles, and creating lean shared libraries to reduce duplication while allowing independence. The document advocates for moderate approaches between extremes rather than ignoring problems with dependencies.
Dealing with dependencies in tests
This document discusses different types of test doubles (fakes, stubs, mocks, spies, and dummies) that can be used to deal with dependencies in tests. It explains what each type is and provides examples of when each might be used. It also discusses how to design code for better test isolation by reducing coupling and avoiding tightly binding components together, though this can sometimes make the code harder to test. Cross-cutting concerns like authentication are discussed as things that may be difficult to fully isolate or mock at a component level.
Kanban 2020
This document discusses issues that can arise with Scrum implementations and introduces Kanban as an alternative. It notes problems with a focus on dates in Scrum and retaining the process rather than changing it. Kanban is presented as a lean approach that emphasizes continuous learning and improvement rather than utilization. The document outlines Kanban concepts like value stream mapping, cost of delay, Kanban boards, and metrics that can be used to test if a Kanban approach is being implemented.
More from Diego Pacheco (20)
Architecture & Engineering : Doing the non-obvious!
Architecture & Engineering : Doing the non-obvious!
Recently uploaded
Complete Self-write Restaurant Business Plan Guide for Entrepreneurs
A guide for making the Best Restaurant Advertising Campaigns with demographics, data analytics, and digital advertising for measurable results.
快速办理(McGill毕业证书)麦吉尔大学毕业证Offer一模一样
学校原件一模一样【微信：741003700 】《(McGill毕业证书)麦吉尔大学毕业证》【微信：741003700 】学位证，留信认证（真实可查，永久存档）原件一模一样纸张工艺/offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原。
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
【主营项目】
一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！
二.真实使馆公证(即留学回国人员证明,不成功不收费)
三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）
四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度)
如果您处于以下几种情况：
◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】
◇面对父母的压力，希望尽快拿到；
◇不清楚认证流程以及材料该如何准备；
◇回国时间很长，忘记办理；
◇回国马上就要找工作，办给用人单位看；
◇企事业单位必须要求办理的
◇需要报考公务员、购买免税车、落转户口
◇申请留学生创业基金
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
1比1定做(aub毕业证书）伯恩茅斯艺术大学毕业证硕士学历证书原版一模一样
原版一模一样【微信：741003700 】【(aub毕业证书）伯恩茅斯艺术大学毕业证硕士学历证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Exploring the Contrast Silicone Sponge Rubber Versus Foam Rubber.pptx
Explore the key differences between silicone sponge rubber and foam rubber in this comprehensive presentation. Learn about their unique properties, manufacturing processes, and applications across various industries. Discover how each material performs in terms of temperature resistance, chemical resistance, and cost-effectiveness. Gain insights from real-world case studies and make informed decisions for your projects.
在线办理(加拿大Concordia毕业证书)康考迪亚大学毕业证学历证书一模一样
学校原件一模一样【微信：741003700 】《(加拿大Concordia毕业证书)康考迪亚大学毕业证》【微信：741003700 】学位证，留信认证（真实可查，永久存档）原件一模一样纸张工艺/offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原。
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
【主营项目】
一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！
二.真实使馆公证(即留学回国人员证明,不成功不收费)
三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）
四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度)
如果您处于以下几种情况：
◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】
◇面对父母的压力，希望尽快拿到；
◇不清楚认证流程以及材料该如何准备；
◇回国时间很长，忘记办理；
◇回国马上就要找工作，办给用人单位看；
◇企事业单位必须要求办理的
◇需要报考公务员、购买免税车、落转户口
◇申请留学生创业基金
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
在线办理(uofc毕业证书)芝加哥大学毕业证学历学位证书原版一模一样
原版纸张【微信：741003700 】【(uofc毕业证书)芝加哥大学毕业证学历学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
1：1制作英国伦敦大学毕业证（london毕业证书）学历学位证书原版一模一样
原版一模一样【微信：741003700 】【英国伦敦大学毕业证（london毕业证书）学历学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Recently uploaded (7)
Complete Self-write Restaurant Business Plan Guide for Entrepreneurs
Complete Self-write Restaurant Business Plan Guide for Entrepreneurs
Exploring the Contrast Silicone Sponge Rubber Versus Foam Rubber.pptx
Exploring the Contrast Silicone Sponge Rubber Versus Foam Rubber.pptx
Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo?
- 1. Agile tem que morrer? Já morreu? Hacker Way, BS ou mais do mesmo? @diego_pacheco Software Architect | Agile Coach
- 2. Waterfall
- 5. Principles
- 8. XP
- 10. Scrum - Process
- 11. Agile Practices – Scrum/XP
- 13. Issues/Mistakes Too much importance into Tools – i.e.:Jira. FollowingPracticesdon’t add value or justloosingthe point– i.e.:User Stories. Don`t understandthe role of the principlesandchange. I.e.: Effective Learning.
- 14. System
- 15. Mindset…
- 17. In the end of the day…
- 18. Effort X Benefit
- 21. What are we missing?
- 22. Services Economy
- 23. Facts
- 24. New Economy: Quality + Innovation + COST
- 26. Entrepreneur/Startup: The new Gold Rush
- 27. Lean Startup
- 28. Lean
- 29. Data
- 30. Solutions
- 33. DEV
- 34. Problem: Complexity, Scale, Speed, Delivery, Innovation?
- 35. The need for DEVOPS: Not Only Complexity
- 36. Evolution
- 37. Shift Happens
- 38. DevOps
- 39. SOA
- 40. SOA
- 41. Architecture
- 42. Isolation
- 43. New: DoD / Tests
- 47. Agile tem que morrer? Já morreu? Hacker Way, BS ou mais do mesmo? @diego_pacheco Software Architect | Agile Coach Obrigado!