Agile And Web Projects (in 20 minutes)

•

5 likes•1,120 views

This document discusses agile methods for web projects and contrasts the traditional approach with an agile approach. Traditionally, projects followed a sequential process where requirements were defined up front, long development periods ensued, and clients were often unhappy with the final results. With an agile approach, small increments are developed in short cycles, requirements evolve iteratively based on frequent client feedback, and the project adapts to changes in priorities and needs. Key techniques that support the agile approach include using a story wall to visualize work, maintaining open communication, integrating changes continuously, and prioritizing feedback from clients.

agile methods
&
web projects
(in 20 minutes)
Phillip Calçado
Lead Consultant
http://fragmental.tw
pcalcado@thoughtworks.com

what usually happens...

a different way to work

supporting tools &
techniques

what usually happens...
before signing the contract

? ?

client agency

what usually happens...
after signing the contract

what usually happens...
after signing the contract
working
long hours

what usually happens...
still not happy after signing the contract
with the website working
long hours

what usually happens...
when the site is delivered

what usually happens...
when the site is delivered
“it’s not what i
thought but i can
live with that...”

what usually happens...
when the site is delivered
“it’s not what i
thought but i can resigned
live with that...”

a different way to work
old way:
ICN Mac OS X Window

Johnny

n-3 n+3
n-2 n+2
n-1 n+1
n

a different way to work
old way:
ICN Mac OS X Window

Johnny

months
n-3 n+3
n-2 n+2
n-1 n+1
n

a different way to work
old way:
ICN Mac OS X Window

Johnny

months
n-3 n+3
n-2 n+2
n-1 n+1
n

concept

a different way to work
old way:
ICN Mac OS X Window

Johnny

months
n-3 n+3
n-2 n+2
n-1 n+1
n

$$$
concept cash

a different way to work
new way:
ICN Mac OS X Window

Johnny

n-3 n+3
n-2 n+2
n-1 n+1
n

feedback cycle

old way months
new way days

supporting tools & techniques

#1 - Story Wall

supporting tools & techniques

#2 - Communication

supporting tools & techniques

#3 - Continuous Integration

supporting tools & techniques

#4 - Feedback

SoundCloud's web and mobile properties are all built on top of our Public API. While building the user-interface atop a RESTful layer has proven itself a sound decision, the one-size-fits-all nature of a Public API is not ideal. When it comes to data transfer and HTTP resource modelling, each client has their own needs, and in the end hacks and workarounds have to be implemented in both clients and servers. Feature development also becomes complicated, with coordination between multiple teams required for every single little feature. SoundCloud is now moving to a different model, where clients have their own façade APIs, modelled after their core characteristics and needs. We are also using the architecture to break away from Conway’s Law and building more cross-functional, end-to-end teams. From: http://gotocon.com/berlin-2013/presentation/APIs:%20The%20Problems%20with%20Eating%20your%20Own%20Dog%20food To implement this, a lot of change in our architecture, tech stack and development processes were required. In this talk we will explore the challenges we had, the options we investigated and how ultimately SoundCloud decided to move forward.

Lisp Macros in 20 Minutes (Featuring Clojure)

Phil Calçado

"We just started holding 20 minutes presentations during lunch time in the ThoughtWorks Sydney office. For the first session I gave a not-that-short talk on Lisp macros using Clojure. The slides are below. It turns out that 20 minutes is too little time to actually acquire content but I think at least we now have some people interested in how metaprogramming can be more than monkey patching." http://fragmental.tw/2009/01/20/presentation-slides-macros-in-20-minutes/

the afterparty: refactoring after 100x hypergrowth

Phil Calçado

PicPay is the largest digital wallet in Latin America. We offer peer-to-peer payments, BNPL, credit cards, personal loans, insurance, investing, trading, and other financial products to 60 million people and 5 million merchants, processing over $20 billion yearly. But just three years ago, in 2019, PicPay was 30 engineers in a small office working on a single product for a few million users. Growing our product portfolio, team size, and the number of transactions by several orders of magnitude so quickly was as chaotic as you might imagine—but we've done it! Our approach gave teams and engineers radical autonomy to choose the best tool, process, and technology for their area. This strategy was invaluable in handling hypergrowth, but as we stabilize as a business and product, we have realized that what took us here isn't what will keep us moving forward. In this talk, let's explore the consequences of how we dealt with our hypergrowth phase and what are the changes and initiatives we have put in place to make sure that we keep growing and pushing the envelope—but at a manageable pace this time around. Phil Calçado is the Global CTO at PicPay. Before PicPay, Phil was Senior Director of Engineering at SeatGeek, leading the team that built the live events platform used by 44 million people worldwide. He has also led the platform team at Meetup/WeWork, worked on Linkerd - the pioneering Service Mesh, and headed product engineering for DigitalOcean and SoundCloud, both pioneers in adopting Microservices architectures. https://plus.qconferences.com/plus2022/presentation/afterparty-refactoring-after-100x-hypergrowth

don't try this at home: self-improvement as a senior leader

Phil Calçado

Presented at LeadingEng New York 2022 (https://leaddev.com/leadingeng-new-york/video/dont-try-home-how-practice-self-improvement-senior-leader) -- Most of us have developed our expertise as engineers through a mix of literature and experimentation. The software industry moves at a higher speed than others because we can try and study complex, real-world systems in the comfort of our bedrooms and personal Github accounts. When you become a leader, especially one who leads other leaders, things get a little more complicated. There are books, but they tend to contain generic advice. There are patterns, but the nature of the job makes it harder to identify when and how to apply them. In this session, I want to walk through a few things that have worked for me when you don't have a lab to try things out. Let's explore processes, tools, and resources to continuously improve your skills and expertise when there is no StackOverflow and no coding dojos. Phil Calçado is Global CTO at PicPay, the largest digital wallet in Latin America. He leads a team of more than 1,500 engineers building financial products for 60 million users and processing over four billion dollars yearly. Before PicPay, Phil was Senior Director of Engineering at SeatGeek, where he led the team that built the live events platform used by 44 million people worldwide. He also has led the platform team at Meetup/WeWork, worked on Linkerd - the pioneering Service Mesh, and headed product engineering for DigitalOcean and SoundCloud, both pioneers in the adoption of Microservices architectures.

The Economics of Microservices (redux)

Phil Calçado

For the last ten years or so, many companies have focused on migrating from larger, monolithic systems and applications towards a specific style of Service-Oriented Architecture called Microservices. The promise was that these smaller, loosely-coupled, and independently developed components would increase productivity and safety for organizations, as large and complex business challenges can be broken down into smaller and simpler components. However, even before most organizations were able to fully migrate to this new architecture and enjoy its promised benefits, a new iteration of cloud computing has been made available in the shape of Serverless platforms such as AWS Lambda, and Google Cloud and Microsoft Azure Functions. Now lots of companies found themselves conflicted between abandoning their traditional microservices approach towards Serverless, often even before they have fully migrated to it from the legacy systems. After leading successful Microservices adoption at SoundCloud and DigitalOcean, recently at Meetup I have faced the challenge of pivoting from a traditional monolith-to-microservices migration to a cloud-native platform. In this talk, let's discuss the fundamental concepts, technologies, and practices behind Microservices and Serverless, and how a software architect used to distributed systems based on microservices needs to change their mindset and approach when adopting Serverless.

Ten Years of Failing Microservices

Phil Calçado

The Next Generation of Microservices

Phil Calçado

How are microservices in 2017 different from how we used to build them at the beginning of the decade? More traditional Service-Oriented Architectures were defined by protocols and standards published and curated by industry consortiums. Knowledge of the architectural style usually called "microservices", on the other hand, is often in the form of patterns, cautionary tales, and tools extracted from real-world reports and software made available by organisations that have adopted this style. Almost ten years since the first wave of such reports, the landscape has changed considerably. Many hard challenges from the past have been eased or completely solved, and a lot of the custom software created by the microservices pioneers have been made off-the-shelf open source software. In this talk, Phil Calçado will contrast what we first found in the first generation of microservices architectures against the current generation's landscape. Let's talk about which previous common knowledge and patterns are deprecated, which ones are still active, and introduce some of the ones that have been recently added to our toolbox.

The Next Generation of Microservices — YOW 2017 Brisbane

Phil Calçado

The Economics of Microservices (2017 CraftConf)

Phil Calçado

Microservices vs. The First Law of Distributed Objects - GOTO Nights Chicago ...

Phil Calçado

TALK #2: Microservices vs. The First Law of Object Design We've been breaking systems and application into smaller components for a long time now. From Component-Based Design to Distributed Objects to SOA to what is today's preferred golden hammer: microservices. One definition of microservices is that it is a flavor of SOA that emphasizes many specialize services versus a few more generalist ones. Often these microservices are so small that they take care of a single "object". Distributed objects aren't new to this industry, and in 2003, Martin Fowler wrote a classic article where he discusses several problems with this model, and proposes the First Law of Distributed Objects: "Objects have been around for a while, and sometimes it seems that ever since they were created, folks have wanted to distribute them. However, distribution of objects, or indeed of anything else, has a lot more pitfalls than many people realize, especially when they're under the influence of vendors' cozy brochures. This article is about some of these hard lessons-lessons I've seen many of my clients learn the hard way... my First Law of Distributed Object Design: Don’t distribute your objects!" Reinventing the wheel is nothing new in our field, but if microservices are meant to be small, how can we avoid the same problems from the past? What are the technologies, architectures, protocols, and practices we need in place to make sure that our microservices architecture isn't just the largest bowl of spaghetti this organization has ever cooked? SPEAKER: Phil Calçado, Director of Software Engineering at DigitalOcean Phil Calçado works at DigitalOcean, where he helps build the cloud for developers. Before that, he spent four years building the team and architecture behind SoundCloud's move from a monolith to microservices. He tweets at @pcalcado writes at http://philcalcado.com.

Finagle @ SoundCloud

Phil Calçado

A Brief Talk On High-Performing Organisations

Phil Calçado

Three Years of Microservices at SoundCloud - Distributed Matters Berlin 2015

Phil Calçado

SoundCloud is the largest repository of audio on the web, used by more than 200 million people every month, who upload more than 11 hours of audio every minute. Like so many others, we have migrated from a typical monolithic architecture to microservices. While the benefits brought by this style of SOA to our productivity and reliability are clear, the architecture required some non-obvious changes in the way we operate systems, and a way to tackle the overhead associated with having hundreds of small moving parts to serve every request. In this talk we’ll share the toolkit and strategy SoundCloud uses to keep its microservices explosion manageable. What do we do about the operations overhead? How to spread devops skills across teams to support the “you build it, you run it” vision? How to deal with breaking changes and asynchronous behaviours? How to deal with chatty interactions? Which protocol? How do I even get a diagram telling me how all this stuff is put together?

Rhein-Main Scala Enthusiasts — Your microservice as a Function

Phil Calçado

ScalaItaly 2015 - Your Microservice as a Function

Phil Calçado

SoundCloud's microservice architecture is built mostly in Scala, using Finagle as its distributed systems workhorse. Finagle is an RPC system for the JVM, and it is based on a pipes-and-filters architecture that maps very nicely to functional programming concepts of higher-order functions and combinators. Over the past few years we have found that it is extremely useful to go even a step further and think of microservices as functions themselves. In this talk let's explore how SoundCloud uses Scala and Finagle, and how we started thinking of a microservices architecture as a special case of a functional system.

Finagle-Based Microservices at SoundCloud

Phil Calçado

An example of Future composition in a real appPhil Calçado

Evolutionary Architecture at WorkPhil Calçado

Structuring apps in ScalaPhil Calçado

From a monolithic Ruby on Rails app to the JVMPhil Calçado

Applying Evolutionary Architecture on a Popular APIPhil Calçado

SoundCloud Masterclass on BrazilPhil Calçado

SpeakerConf: my findings in trying to use this functional programming busines...Phil Calçado

Encryption in Microsoft 365 - ExpertsLive Netherlands 2024

Albert Hoitingh

GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...

Sri Ambati

Recently uploaded

Encryption in Microsoft 365 - ExpertsLive Netherlands 2024

Albert Hoitingh

GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...

Sri Ambati

Assure Contact Center Experiences for Your Customers With ThousandEyes

ThousandEyes

GraphRAG is All You need? LLM & Knowledge Graph

Guy 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/

When stars align: studies in data quality, knowledge graphs, and machine lear...

Elena Simperl

Introduction to CHERI technology - Cybersecurity

mikeeftimakis1

PHP Frameworks: I want to break free (IPC Berlin 2024)

Ralf Eggert

In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development. This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.

Empowering NextGen Mobility via Large Action Model Infrastructure (LAMI): pav...

Thierry Lestable

Securing your Kubernetes cluster_ a step-by-step guide to success !

KatiaHIMEUR1

Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster. However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks. In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.

Assuring Contact Center Experiences for Your Customers With ThousandEyes

ThousandEyes

Quantum Computing: Current Landscape and the Future Role of APIs

Vlad Stirbu

Unsubscribed: Combat Subscription Fatigue With a Membership Mentality by Head...

Product School

Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf

Paige Cruz

Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack. While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack. I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:

FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf

FIDO Alliance

Secstrike : Reverse Engineering & Pwnable tools for CTF.pptx

nkrafacyberclub

Generative AI Deep Dive: Advancing from Proof of Concept to Production

Aggregage

How world-class product teams are winning in the AI era by CEO and Founder, P...

Product School

Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™

UiPathCommunity

In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni. 📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath: Autopilot per Studio Web Autopilot per Studio Autopilot per Apps Clipboard AI GenAI applicata alla Document Understanding 👨‍🏫👨‍💻 Speakers: Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath Andrei Tasca, RPA Solutions Team Lead @NTT Data

UiPath Test Automation using UiPath Test Suite series, part 3

DianaGray10

Free Complete Python - A step towards Data Science

RinaMondal9

Recently uploaded (20)

Encryption in Microsoft 365 - ExpertsLive Netherlands 2024

GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...

Assure Contact Center Experiences for Your Customers With ThousandEyes

GraphRAG is All You need? LLM & Knowledge Graph

When stars align: studies in data quality, knowledge graphs, and machine lear...

Introduction to CHERI technology - Cybersecurity

PHP Frameworks: I want to break free (IPC Berlin 2024)

Empowering NextGen Mobility via Large Action Model Infrastructure (LAMI): pav...

Securing your Kubernetes cluster_ a step-by-step guide to success !

Assuring Contact Center Experiences for Your Customers With ThousandEyes

Quantum Computing: Current Landscape and the Future Role of APIs

Unsubscribed: Combat Subscription Fatigue With a Membership Mentality by Head...

Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf

FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf

Secstrike : Reverse Engineering & Pwnable tools for CTF.pptx

Generative AI Deep Dive: Advancing from Proof of Concept to Production

How world-class product teams are winning in the AI era by CEO and Founder, P...

Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™

UiPath Test Automation using UiPath Test Suite series, part 3

Free Complete Python - A step towards Data Science

Agile And Web Projects (in 20 minutes)

1. agile methods & web projects (in 20 minutes) Phillip Calçado Lead Consultant http://fragmental.tw pcalcado@thoughtworks.com

2. what usually happens... a different way to work supporting tools & techniques

3. what usually happens... a different way to work supporting tools & techniques

4. what usually happens... before signing the contract ? ? client agency

5. what usually happens... before signing the contract ? ? client agency

6. what usually happens... + + before signing the contract ? ? client agency

7. what usually happens... after signing the contract

8. what usually happens... after signing the contract working long hours

9. what usually happens... still not happy after signing the contract with the website working long hours

10. what usually happens... when the site is delivered

11. what usually happens... when the site is delivered “it’s not what i thought but i can live with that...”

12. what usually happens... when the site is delivered “it’s not what i thought but i can resigned live with that...”

13. what usually happens... a different way to work supporting tools & techniques

14. old way

15. a different way to work old way: ICN Mac OS X Window Johnny n-3 n+3 n-2 n+2 n-1 n+1 n

16. a different way to work old way: ICN Mac OS X Window Johnny months n-3 n+3 n-2 n+2 n-1 n+1 n

17. a different way to work old way: ICN Mac OS X Window Johnny months n-3 n+3 n-2 n+2 n-1 n+1 n concept

18. a different way to work old way: ICN Mac OS X Window Johnny months n-3 n+3 n-2 n+2 n-1 n+1 n $$$ concept cash

19. new way

20. a different way to work new way: ICN Mac OS X Window Johnny n-3 n+3 n-2 n+2 n-1 n+1 n

21. a different way to work new way: ICN Mac OS X Window Johnny n-3 n+3 n-2 n+2 n-1 n+1 n $$$

22. a different way to work new way: ICN Mac OS X Window Johnny n-3 n+3 n-2 n+2 n-1 n+1 n $$$ $$$

23. a different way to work new way: ICN Mac OS X Window Johnny n-3 n+3 n-2 n+2 n-1 n+1 n $$$ $$$ $$$

24. old way $$$ new way $$$ $$$ $$$

25. feedback cycle old way months new way days

26. what usually happens... a different way to work supporting tools & techniques

27. supporting tools & techniques #1 - Story Wall

28. supporting tools & techniques #2 - Communication

29. supporting tools & techniques #3 - Continuous Integration

30. supporting tools & techniques #4 - Feedback

31. thank you http://www.thoughtworks.com

Agile And Web Projects (in 20 minutes)

Recommended

Recommended

More Related Content

More from Phil Calçado

More from Phil Calçado (20)

Recently uploaded

Recently uploaded (20)

Agile And Web Projects (in 20 minutes)