The document discusses some unintended consequences of adopting agile practices, including generalizing specialists, extroverting introverts, and suppressing excellence. It provides remedies for each, such as code reviews to break down silos and having technical stories in sprints to prevent suppressing excellence. It also advocates for gradually introducing Scrum practices like starting with product backlog and retrospectives before daily standups and sprints.
Computing Performance: On the Horizon (2021)Brendan Gregg
Talk by Brendan Gregg for USENIX LISA 2021. https://www.youtube.com/watch?v=5nN1wjA_S30 . "The future of computer performance involves clouds with hardware hypervisors and custom processors, servers running a new type of BPF software to allow high-speed applications and kernel customizations, observability of everything in production, new Linux kernel technologies, and more. This talk covers interesting developments in systems and computing performance, their challenges, and where things are headed."
How To Do Kick-Ass Software DevelopmentSven Peters
With Kick-Ass Software Development you actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Less mangers managing, less testers testing and less IT-operators operating. The developers take the power back, making them much happier. Sound like paradise? It is! This session will show you how we do Kick-Ass Software Development at Atlassian.
I talk about how we: use pull requests for better code quality; collaborate fast to develop ideas; avoid meetings to get more stuff done; tighten our feedback loops to fail faster; shorten our release cycles; and work together happily on different continents. It's a great way to develop software and we think it can work in your company, too.
Watch the video if this talk: http://vimeo.com/70102926
Computing Performance: On the Horizon (2021)Brendan Gregg
Talk by Brendan Gregg for USENIX LISA 2021. https://www.youtube.com/watch?v=5nN1wjA_S30 . "The future of computer performance involves clouds with hardware hypervisors and custom processors, servers running a new type of BPF software to allow high-speed applications and kernel customizations, observability of everything in production, new Linux kernel technologies, and more. This talk covers interesting developments in systems and computing performance, their challenges, and where things are headed."
How To Do Kick-Ass Software DevelopmentSven Peters
With Kick-Ass Software Development you actually get stuff done. Feedback cycles are short, code quality is awesome and customers get the features they lust after. Less mangers managing, less testers testing and less IT-operators operating. The developers take the power back, making them much happier. Sound like paradise? It is! This session will show you how we do Kick-Ass Software Development at Atlassian.
I talk about how we: use pull requests for better code quality; collaborate fast to develop ideas; avoid meetings to get more stuff done; tighten our feedback loops to fail faster; shorten our release cycles; and work together happily on different continents. It's a great way to develop software and we think it can work in your company, too.
Watch the video if this talk: http://vimeo.com/70102926
Technology-Driven Development: Using Automation and Development Techniques to...Hiroyuki Ito
This is the report presented at Agile2014 on "Experience Report" track.
「Agile2014」の「Experience Report」トラックで発表したスライドです。
Agile2014
http://agile2014.agilealliance.org/
Track information
http://agile2014.sched.org/event/356d50c44035cafe4c27c33da03c2b80#
Automation and development techniques such as Continuous Integration/Continuous Delivery, TDD (Test-Driven Development) and BDD (Behavior-Driven Development) are useful for not only efficiency but also learning and collaboration.
I explained these practices as "Technology-Driven Development".
CI/CD・TDD・BDD といった自動化技術・技術プラクティスは、業務効率化だけではなく、メンバーの成長およびコラボレーションの促進にも効果があります。
これらのプラクティスを "Technology-Driven Development" と命名・整理した資料になります。
Life Has Not Been That Rosy With Agile : Rahul SudameoGuild .
In my experience, Agile adoption started in some of the organizations with lot of hype and inflated expectations. And in such cases, if Agile transformation is not handled properly, it can result in multiple challenges rather than providing the expected benefits.
This practical experience sharing session would cover some such problems I faced while applying Agile in different environments. The audience practicing Agile can relate some of these challenges with their own environment as well. The attendees who are on their path to Agile transformation can learn from the lessons and mistakes shared by the speaker.
The session would cover challenges observed due to nature of the project, customer-vendor engagement model, application of processes, attitude of people rolling out agile, unrealistic expectations, conflict in roles and responsibilities. It would also highlight challenges introduced to some of the roles (like Project/QA Manager/Manual Tester etc.) in Agile environment and impact on billing / project contracts / SOW etc.
Technology-Driven Development: Using Automation and Development Techniques to...Rakuten Group, Inc.
This is the report presented at Agile2014 on "Experience Report" track.
「Agile2014」の「Experience Report」トラックで発表したスライドです。
Agile2014
http://agile2014.agilealliance.org/
Track information
http://agile2014.sched.org/event/356d50c44035cafe4c27c33da03c2b80#
Automation and development techniques such as Continuous Integration/Continuous Delivery, TDD (Test-Driven Development) and BDD (Behavior-Driven Development) are useful for not only efficiency but also learning and collaboration.
I explained these practices as "Technology-Driven Development".
CI/CD・TDD・BDD といった自動化技術・技術プラクティスは、業務効率化だけではなく、メンバーの成長およびコラボレーションの促進にも効果があります。
これらのプラクティスを "Technology-Driven Development" と命名・整理した資料になります。
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...John Carter
Applying Agile methods in a waterfall world seemed impossible until we discovered the 10 essential skills and tools. Five of these skills are organizational, while others translate the short intervals characteristic of Agile to the world outside of Software. User Stories becomes Boundary Conditions; Burn-down charts becomes Deliverable Hit Rate charts; Sprints become HW intervals; Sprint Retrospectives become Event Timeline Retrospectives, while the project as a whole is managed using Boundary Conditions. This presentation shows examples of these tools and shows examples of how they are applied.
How to Plan for Hyper Growth Success by Slack Software EngineerProduct School
Every company is different. Every team is different. Every Product Manager is different. In Carly's two years working at Slack as a Software Engineer building features for Enterprise Grid, she's had the opportunity to work with several Product Managers with distinct styles and varying levels of experience. Her talk explored challenges her team encountered working on high impact, cross functional projects in a hyper growth startup environment.
Let the Elephants Leave the Room: Tips for Making Development Life Leaner by ...Agile ME
As developers, we often complain about the efficiency problems we face while working. We work hard but produce so little that our whole development life turns into a hamster wheel at some point. One of the biggest reason of such a common problem is working in waste. Waste is in everywhere, in our source code, in the office, in our processes and even in management. In this session, I will talk about the wastes and how we can remove to make our development life leaner.
DevOps Days Toronto: From 6 Months Waterfall to 1 hour Code DeploysAndreas Grabner
Slides used for https://www.devopsdays.org/events/2017-toronto/program/andreas-grabner/
In 2011 we delivered 2 major releases of our on premise enterprise software. Market, technology and customer requirements forced us to change that in order to remain competitive.
Now – in 2017 - we are deploying and providing feature releases every 2 weeks for both our on premise and SaaS-based offering. We deploy 170 SaaS production changes per day and have a DevOps pipeline that allows us to deploy a code change within 1h if necessary.
To increase quality, we built and provide a DevOps pipeline that currently executes 31000 Unit & Integration Tests per Hour as well as 60h UI Tests per Build. Our application teams are responsible end-to-end for their features and use production monitoring to validate their deployments which allows them to find 93% of bugs in production before it impacts our end users.
In this session I explain how this transformation worked from both “Top Down” as well as “Bottom Up” in our organization. A key component was the 4 people strong DevOps Team who developed and “sell” their DevOps Pipeline to the globally distributed application teams. I will give insights into how our pipeline enables application teams to design, code, test and run a new feature for our user base.
I will also talk about the “dark moments” as change is never without friction. Both internally as well as with our customers who also had to get used to more rapid changes.
The process of software development for reasonably small team (less that 9 people) is pretty straitforward. Usually it is based on Scrum or Kanban with some variations and simplifications.
For huge team with more then 30 people it is not that obvious. For sure teams have interdependencies both in coding and requirements management that can really slow down development.
For people and teams it looks like constant interruptions caused by other teams and management. The problem is that “classic” Agile doesn’t help.
In this session we will consider methods of scaling Agile in huge teams.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Technology-Driven Development: Using Automation and Development Techniques to...Hiroyuki Ito
This is the report presented at Agile2014 on "Experience Report" track.
「Agile2014」の「Experience Report」トラックで発表したスライドです。
Agile2014
http://agile2014.agilealliance.org/
Track information
http://agile2014.sched.org/event/356d50c44035cafe4c27c33da03c2b80#
Automation and development techniques such as Continuous Integration/Continuous Delivery, TDD (Test-Driven Development) and BDD (Behavior-Driven Development) are useful for not only efficiency but also learning and collaboration.
I explained these practices as "Technology-Driven Development".
CI/CD・TDD・BDD といった自動化技術・技術プラクティスは、業務効率化だけではなく、メンバーの成長およびコラボレーションの促進にも効果があります。
これらのプラクティスを "Technology-Driven Development" と命名・整理した資料になります。
Life Has Not Been That Rosy With Agile : Rahul SudameoGuild .
In my experience, Agile adoption started in some of the organizations with lot of hype and inflated expectations. And in such cases, if Agile transformation is not handled properly, it can result in multiple challenges rather than providing the expected benefits.
This practical experience sharing session would cover some such problems I faced while applying Agile in different environments. The audience practicing Agile can relate some of these challenges with their own environment as well. The attendees who are on their path to Agile transformation can learn from the lessons and mistakes shared by the speaker.
The session would cover challenges observed due to nature of the project, customer-vendor engagement model, application of processes, attitude of people rolling out agile, unrealistic expectations, conflict in roles and responsibilities. It would also highlight challenges introduced to some of the roles (like Project/QA Manager/Manual Tester etc.) in Agile environment and impact on billing / project contracts / SOW etc.
Technology-Driven Development: Using Automation and Development Techniques to...Rakuten Group, Inc.
This is the report presented at Agile2014 on "Experience Report" track.
「Agile2014」の「Experience Report」トラックで発表したスライドです。
Agile2014
http://agile2014.agilealliance.org/
Track information
http://agile2014.sched.org/event/356d50c44035cafe4c27c33da03c2b80#
Automation and development techniques such as Continuous Integration/Continuous Delivery, TDD (Test-Driven Development) and BDD (Behavior-Driven Development) are useful for not only efficiency but also learning and collaboration.
I explained these practices as "Technology-Driven Development".
CI/CD・TDD・BDD といった自動化技術・技術プラクティスは、業務効率化だけではなく、メンバーの成長およびコラボレーションの促進にも効果があります。
これらのプラクティスを "Technology-Driven Development" と命名・整理した資料になります。
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...John Carter
Applying Agile methods in a waterfall world seemed impossible until we discovered the 10 essential skills and tools. Five of these skills are organizational, while others translate the short intervals characteristic of Agile to the world outside of Software. User Stories becomes Boundary Conditions; Burn-down charts becomes Deliverable Hit Rate charts; Sprints become HW intervals; Sprint Retrospectives become Event Timeline Retrospectives, while the project as a whole is managed using Boundary Conditions. This presentation shows examples of these tools and shows examples of how they are applied.
How to Plan for Hyper Growth Success by Slack Software EngineerProduct School
Every company is different. Every team is different. Every Product Manager is different. In Carly's two years working at Slack as a Software Engineer building features for Enterprise Grid, she's had the opportunity to work with several Product Managers with distinct styles and varying levels of experience. Her talk explored challenges her team encountered working on high impact, cross functional projects in a hyper growth startup environment.
Let the Elephants Leave the Room: Tips for Making Development Life Leaner by ...Agile ME
As developers, we often complain about the efficiency problems we face while working. We work hard but produce so little that our whole development life turns into a hamster wheel at some point. One of the biggest reason of such a common problem is working in waste. Waste is in everywhere, in our source code, in the office, in our processes and even in management. In this session, I will talk about the wastes and how we can remove to make our development life leaner.
DevOps Days Toronto: From 6 Months Waterfall to 1 hour Code DeploysAndreas Grabner
Slides used for https://www.devopsdays.org/events/2017-toronto/program/andreas-grabner/
In 2011 we delivered 2 major releases of our on premise enterprise software. Market, technology and customer requirements forced us to change that in order to remain competitive.
Now – in 2017 - we are deploying and providing feature releases every 2 weeks for both our on premise and SaaS-based offering. We deploy 170 SaaS production changes per day and have a DevOps pipeline that allows us to deploy a code change within 1h if necessary.
To increase quality, we built and provide a DevOps pipeline that currently executes 31000 Unit & Integration Tests per Hour as well as 60h UI Tests per Build. Our application teams are responsible end-to-end for their features and use production monitoring to validate their deployments which allows them to find 93% of bugs in production before it impacts our end users.
In this session I explain how this transformation worked from both “Top Down” as well as “Bottom Up” in our organization. A key component was the 4 people strong DevOps Team who developed and “sell” their DevOps Pipeline to the globally distributed application teams. I will give insights into how our pipeline enables application teams to design, code, test and run a new feature for our user base.
I will also talk about the “dark moments” as change is never without friction. Both internally as well as with our customers who also had to get used to more rapid changes.
The process of software development for reasonably small team (less that 9 people) is pretty straitforward. Usually it is based on Scrum or Kanban with some variations and simplifications.
For huge team with more then 30 people it is not that obvious. For sure teams have interdependencies both in coding and requirements management that can really slow down development.
For people and teams it looks like constant interruptions caused by other teams and management. The problem is that “classic” Agile doesn’t help.
In this session we will consider methods of scaling Agile in huge teams.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
2. Of the Programmers, by the Programmers
(signatories of agile manifesto)
Kent Beck Ron Jeffries
Mike Beedle Jon Kern
Arie van Bennekum Brian Marick
Alistair Cockburn Robert C. Martin
Ward Cunningham Steve Mellor
Martin Fowler Ken Schwaber
James Grenning Jeff Sutherland
Jim Highsmith Dave Thomas
Andrew Hunt
160 years of programming experience!
3. The Unattended
Side Effects of Agile
Generalization of the Specialist
Extrovertion of the Introvert
Productivization of the Engineer
Suppression of Excellence
5. Generalizing the Specialist
Remedies:
1. Fix product development before introducing
agile! Defined product owner, prioritized
backlog and product roadmap are
prerequisite for successful agile adoption.
2. Make sure the team internalizes company
and product strategy!
3. Give additional responsibilities first!
16. Further reading:
• Why I’m done with Scrum
http://lostechies.com/jimmybogard/2012/09/12/why-im-done-with-scrum/
• “Dilbert” on Extreme and Agile Programming
http://www.globalnerdy.com/2007/11/28/dilbert-on-extreme-and-agile-
programming/
• Project Management 101
http://rodp.wordpress.com/2012/09/07/project-management-101/
• Relaxing Scrum
http://restreaming.wordpress.com/2012/09/17/relaxing-scrum/
Editor's Notes
Youare all familiar with agile manifesto. But recently Zed Shaw presented anti-agile manifesto.We are programmers who have been humiliated by software development methodologies for years.We are tired of XP, Scrum, Kanban, Waterfall, and anything else getting in the way of...Programming.We are tired of being told we're autistic idiots without anytime to be creative because none of the 10 managers on the project can do... Programming.We must destroy these methodologies that get in the way of...Programming.Zed Shaw is not some teenage programmer. He's author of popular book series Learn Code The Hard Way.
Kent Beck has been programming for 35 years! He's currently at Facebook developing a thrift server to handle all messaging traffic.What went wrong? Why are some programmers rejecting agile?- were they wrong in the first place?- has environment changed so much in the last 10 years?- agile does not scale to average programmersProblem => Solution
- On the surface scrum looks trivial. But in reality it causes enormous changes. Nobody is helping people cope with the changes. This should be the main role of scrum master/coach- Hire "Agile Developers" in the first place. (a) don't hire one trick ponies, (b) check for team work capabilities, (c) check for the cultural fit- Firing people is neither the the right thing nor easy.- There's no silver bullet: Don't try to change people. Help people overcome small barriers, but don't waste time on people who just don't fit
Introduction of agile changes development priorities.I've been here myself.Typical situation: You are building a recommendation engine for months or even years. A scrum is introduced and development priorities change.Programmers are expect to do also planning, designing, interviewing users, and making decisions outside of their technical expertizeProgrammers are forced out of their comfort zonesPeople who build their identify and self-esteem upon their expertize, lose groundsProgrammers consider only coding as creative.
Ad 1) Building the right product is more important than building the product right!Ad 2) There's no such thing as too much communicationAd 3) - Don't expect people to be responsible as a team, if they don't know how to be responsible as individuals.- But don't make them responsible to the managers, but to the customers.
- Around an introvert programmer a silo always forms. The silo took years to be built and it's quite often the critical piece of the system. Opening up the silo should be done very carefully.- Scrum forces introverts to communicate. This usually results in violent crashes.- Usually the introvert wants out of the silo himself (but only to build another silo)
- Don't push the introvert too hard: - pair programming - shared code - collective planning - product demosAd 1) Instead of pair programming and shared codeAd 2) Instead of collective planning (he'll hear anyway)Ad 3) Instead of product demos
- Engineers adore solving problems that nobody has.- We love solving problems with technology, even if non-technological solutions would be much more effective.
Ad 1) There's no more humbling experience for an engineer than seeing his work being used by a real user. We recently showed to engineers a user interview that exposed naked technical problems of our service. The result was profound.Ad 2) Be on the look out for such cases at user interviews.Engineers feel omniscient and superior to the users. These two things break this notion and make them interested in actually listening to the user.
- These days they say in Silicon Valley: "If you're not embarrassed of the first version of your product, you've shipped too late"- Engineers are proud people.- There are ways how to start learning fast while still keeping excellence in engineering.
-Scrum won't fix your product development process. - separate product from people/process management.- Put people in the driver seat of changes.- You can delegate more responsibilities already today. - Cross-functional teams always make sense. One full expert is better than two halves. - Increase or decrease team size as required by the project/process at hand.- Every team needs a coach to help the team jell.- Iterations introduces pressure cooking. That's why things explode. Do this after fundamentals are in place.