Marty dives into the complex process of business transformation, highlighting both its anti-patterns and valuable lessons from successes.
The talk underscores the shift from mere ‘Agile’ labels to profound changes in building, problem-solving, and decision-making. He emphasizes transitioning from big releases to consistent cadences, evolving from stakeholder-driven roadmaps to empowered product teams, and redefining how companies prioritize threats and opportunities.
At its core, the transformation journey seeks to tap into the talent of your people to provide a machine for consistent innovation. This talk promises to provide a holistic view of company transformation, guiding product leaders on where they stand and where they need to head.
The document summarizes the outcomes of Facile.it Partner's 2023 hackathon. Some key points:
- The hackathon aimed to break down silos, foster collaboration, and promote a culture of sharing, creativity, and innovation.
- Activities included shadowing, brainstorming sessions, coding, prototyping, and team building. These resulted in ideas generated, issues solved, and code deployed.
- A rubber duck was used as the hackathon mascot to represent debugging techniques. Homemade gadgets with the company logo were also produced.
- The hackathon scope was expanded to ensure knowledge sharing and collaboration by involving sales accounts throughout the process.
- The
Marty dives into the complex process of business transformation, highlighting both its anti-patterns and valuable lessons from successes.
The talk underscores the shift from mere ‘Agile’ labels to profound changes in building, problem-solving, and decision-making. He emphasizes transitioning from big releases to consistent cadences, evolving from stakeholder-driven roadmaps to empowered product teams, and redefining how companies prioritize threats and opportunities.
At its core, the transformation journey seeks to tap into the talent of your people to provide a machine for consistent innovation. This talk promises to provide a holistic view of company transformation, guiding product leaders on where they stand and where they need to head.
The document summarizes the outcomes of Facile.it Partner's 2023 hackathon. Some key points:
- The hackathon aimed to break down silos, foster collaboration, and promote a culture of sharing, creativity, and innovation.
- Activities included shadowing, brainstorming sessions, coding, prototyping, and team building. These resulted in ideas generated, issues solved, and code deployed.
- A rubber duck was used as the hackathon mascot to represent debugging techniques. Homemade gadgets with the company logo were also produced.
- The hackathon scope was expanded to ensure knowledge sharing and collaboration by involving sales accounts throughout the process.
- The
This document provides guidance on delivering effective feedback in 3 sentences or less:
The document defines feedback as helpful information or criticism given to improve performance and outlines key components of effective feedback, including asking permission, being specific, kind, empathetic, and timely. It also recommends using a feedback equation of observing a behavior, describing its impact, and asking a question to make feedback actionable. The overall message is that feedback should be a two-way dialogue to understand different perspectives and help the recipient improve.
No Silver Bullet - Essence and Accident in Software EngineeringSalvatore Cordiano
Frederick P. Brooks, Jr.
University of North Carolina at Chapel Hill
There is no single development, in either technology or management
technique, which by itself promises even one order-of-magnitude
improvement within a decade in productivity, in reliability, in simplicity.
The document summarizes a recent hackathon held by Facile.it Partner from May 9-12, 2022. It discusses the vision for the hackathon as an opportunity for cross-functional teams to solve problems in a new way. The hackathon utilized a new format of separating the problem and solution spaces. It involved 30 participants across 5 cross-functional teams who worked to identify issues, present solutions, and code implementations. The "Doctor Shark" team won the competition with 61 points by identifying issues, giving pitches, participating in team-building, and implementing the most story points worth of solutions. The hackathon aimed to foster a mindset of continuous problem solving across teams.
The document summarizes an FP Hackathon that took place from 9-12 May 2022. It discusses improvements from the 2021 to 2022 event, including an increase in participants from 30 to 55 and the use of a Miro board instead of a wall board. The top three winning teams were announced, with Doctor Shark taking first place. The hackathon aimed to develop solutions to reduce inbound calls, increase autonomy, and improve user experience for collaborators.
Today we started our 2nd internal #hackathon, introducing new approaches to complexity dealing. We propose to adopt the "Manifesto for Slow Thinking", even if we are in a time-bound competition.
According to my perspective, a #SlowThinking mindset enables empathy, critical thinking, humbleness, feedback, and emotional intelligence.
Ownership is about taking the initiative to do the right thing. It’s about taking the bull by the horns, driving the process and not assuming it is someone else’s responsibility.
The Eisenhower Matrix is a time management tool based on strategies used by Dwight D. Eisenhower to prioritize tasks. It divides tasks into four quadrants based on their urgency and importance: tasks that are both urgent and important should be completed immediately; important non-urgent tasks can be scheduled; unimportant tasks should be avoided or delegated; and urgent but unimportant tasks can be delegated to others. The matrix provides a simple framework to evaluate tasks and determine the best way to manage workload and priorities.
The Blake Mouton Managerial Grid assesses leadership styles based on two dimensions: concern for people and concern for results. The grid defines five styles ranging from low concern in both areas ("Nightmare") to high concern in both ("Heaven"). Leaders are evaluated based on how they balance accomplishing tasks while considering employees' needs, interests, and development.
The document announces a hackathon being held by Facile.it on June 7th. It lists the company's core values such as easiness, courage, concreteness, passion, and relationship. It also lists shared principles for the hackathon such as being against standardization, connecting people, and ensuring programs meet user expectations rather than creator expectations. The document defines empathy and its four key attributes. It wishes attendees a happy hackathon.
The document discusses the importance of culture for a development team. It defines culture as the habits, traditions, and beliefs shared by a group. A team culture is made up of the values, beliefs, attitudes, and behaviors shared by team members. It is generally unspoken and describes how people work together towards common goals and treat each other. The document outlines principles for an inspiring culture, including putting people first, disagreeing openly but constructively, sharing and helping others, providing continuous feedback, collaborating effectively, and setting goals and context.
The document discusses engineering delivery metrics for a Shark Dev Team. It summarizes metrics like lead time, cycle time, throughput, and work in progress (WIP) that can be extracted from Jira. The document finds that cycle time decreased from June-July 2020 to June-November 2020 while throughput increased. Little's Law is used to show the relationship between WIP, throughput, and cycle time. The document proposes next steps like improving metrics with Jira plugins and defining goals for team metrics.
This document provides an overview of search functionality in Kibana, including the Discover UI, search types (free text, field level, filters), the Kibana Query Language (KQL) and Lucene Query Language, advanced search types (wildcard, proximity, boosting, ranges, regex), and examples of queries. It also demonstrates how to perform a basic search in Kibana by choosing an index, setting a time range, using free text search, refining with fields and filters, and inspecting surrounding documents.
This document compares the memory usage of new and old versions of RabbitMQ consumers. The new version 2.2.0 of the rabbitmq-cli-consumer GitHub project uses significantly less memory than the previous private fork, with memory reductions of up to 505 MB for batch sizes of 3.
This document provides an overview of Git workflows including branching, merging, Gitflow, GitHub Flow, and pull requests. It describes what branches are used for in Gitflow (feature, release, hotfix, master, develop) and how they are managed. GitHub Flow is also summarized as having descriptive branches off master that are reviewed via pull requests before being merged back to trigger deployment. Pull requests allow for code review and discussion before merging changes.
Git is a version control system that tracks changes to files. It refers to commits using their SHA-1 hash or user-friendly refs. Refs represent branches and tags and are stored in .git/refs. Special refs like HEAD track the current branch. Commands like git reset, checkout, and revert can undo changes, with reset moving branches, checkout switching branches, and revert creating new commits to undo changes. Rebasing moves commits to a new base, rewriting history, while merging uses merge commits. The document contrasts operations that alter history like reset versus those that don't, like revert, and advises not rewriting public history.
This document provides guidance on delivering effective feedback in 3 sentences or less:
The document defines feedback as helpful information or criticism given to improve performance and outlines key components of effective feedback, including asking permission, being specific, kind, empathetic, and timely. It also recommends using a feedback equation of observing a behavior, describing its impact, and asking a question to make feedback actionable. The overall message is that feedback should be a two-way dialogue to understand different perspectives and help the recipient improve.
No Silver Bullet - Essence and Accident in Software EngineeringSalvatore Cordiano
Frederick P. Brooks, Jr.
University of North Carolina at Chapel Hill
There is no single development, in either technology or management
technique, which by itself promises even one order-of-magnitude
improvement within a decade in productivity, in reliability, in simplicity.
The document summarizes a recent hackathon held by Facile.it Partner from May 9-12, 2022. It discusses the vision for the hackathon as an opportunity for cross-functional teams to solve problems in a new way. The hackathon utilized a new format of separating the problem and solution spaces. It involved 30 participants across 5 cross-functional teams who worked to identify issues, present solutions, and code implementations. The "Doctor Shark" team won the competition with 61 points by identifying issues, giving pitches, participating in team-building, and implementing the most story points worth of solutions. The hackathon aimed to foster a mindset of continuous problem solving across teams.
The document summarizes an FP Hackathon that took place from 9-12 May 2022. It discusses improvements from the 2021 to 2022 event, including an increase in participants from 30 to 55 and the use of a Miro board instead of a wall board. The top three winning teams were announced, with Doctor Shark taking first place. The hackathon aimed to develop solutions to reduce inbound calls, increase autonomy, and improve user experience for collaborators.
Today we started our 2nd internal #hackathon, introducing new approaches to complexity dealing. We propose to adopt the "Manifesto for Slow Thinking", even if we are in a time-bound competition.
According to my perspective, a #SlowThinking mindset enables empathy, critical thinking, humbleness, feedback, and emotional intelligence.
Ownership is about taking the initiative to do the right thing. It’s about taking the bull by the horns, driving the process and not assuming it is someone else’s responsibility.
The Eisenhower Matrix is a time management tool based on strategies used by Dwight D. Eisenhower to prioritize tasks. It divides tasks into four quadrants based on their urgency and importance: tasks that are both urgent and important should be completed immediately; important non-urgent tasks can be scheduled; unimportant tasks should be avoided or delegated; and urgent but unimportant tasks can be delegated to others. The matrix provides a simple framework to evaluate tasks and determine the best way to manage workload and priorities.
The Blake Mouton Managerial Grid assesses leadership styles based on two dimensions: concern for people and concern for results. The grid defines five styles ranging from low concern in both areas ("Nightmare") to high concern in both ("Heaven"). Leaders are evaluated based on how they balance accomplishing tasks while considering employees' needs, interests, and development.
The document announces a hackathon being held by Facile.it on June 7th. It lists the company's core values such as easiness, courage, concreteness, passion, and relationship. It also lists shared principles for the hackathon such as being against standardization, connecting people, and ensuring programs meet user expectations rather than creator expectations. The document defines empathy and its four key attributes. It wishes attendees a happy hackathon.
The document discusses the importance of culture for a development team. It defines culture as the habits, traditions, and beliefs shared by a group. A team culture is made up of the values, beliefs, attitudes, and behaviors shared by team members. It is generally unspoken and describes how people work together towards common goals and treat each other. The document outlines principles for an inspiring culture, including putting people first, disagreeing openly but constructively, sharing and helping others, providing continuous feedback, collaborating effectively, and setting goals and context.
The document discusses engineering delivery metrics for a Shark Dev Team. It summarizes metrics like lead time, cycle time, throughput, and work in progress (WIP) that can be extracted from Jira. The document finds that cycle time decreased from June-July 2020 to June-November 2020 while throughput increased. Little's Law is used to show the relationship between WIP, throughput, and cycle time. The document proposes next steps like improving metrics with Jira plugins and defining goals for team metrics.
This document provides an overview of search functionality in Kibana, including the Discover UI, search types (free text, field level, filters), the Kibana Query Language (KQL) and Lucene Query Language, advanced search types (wildcard, proximity, boosting, ranges, regex), and examples of queries. It also demonstrates how to perform a basic search in Kibana by choosing an index, setting a time range, using free text search, refining with fields and filters, and inspecting surrounding documents.
This document compares the memory usage of new and old versions of RabbitMQ consumers. The new version 2.2.0 of the rabbitmq-cli-consumer GitHub project uses significantly less memory than the previous private fork, with memory reductions of up to 505 MB for batch sizes of 3.
This document provides an overview of Git workflows including branching, merging, Gitflow, GitHub Flow, and pull requests. It describes what branches are used for in Gitflow (feature, release, hotfix, master, develop) and how they are managed. GitHub Flow is also summarized as having descriptive branches off master that are reviewed via pull requests before being merged back to trigger deployment. Pull requests allow for code review and discussion before merging changes.
Git is a version control system that tracks changes to files. It refers to commits using their SHA-1 hash or user-friendly refs. Refs represent branches and tags and are stored in .git/refs. Special refs like HEAD track the current branch. Commands like git reset, checkout, and revert can undo changes, with reset moving branches, checkout switching branches, and revert creating new commits to undo changes. Rebasing moves commits to a new base, rewriting history, while merging uses merge commits. The document contrasts operations that alter history like reset versus those that don't, like revert, and advises not rewriting public history.
Accrescere la motivazione per raggiungere gli obiettivi
1. Attestato di frequenza
SALVATORE CORDIANO
ha frequentato con successo il corso e-learning
Accrescere la motivazione per raggiungere gli obiettivi
Imparare a impiegare le leve della motivazione
30/09/2018 Il docente
Arduino Mancini