Pragmatic Architecture, Today.

Updated version of my talk on pragmatic architecture. Added a couple of slides (and other small adjustments) after receiving great feedback from people who attended the first version of the talk. Thanks a lot for these! Software development has evolved. Agile is now the de-facto standard. The role of an architect in an agile project is very different than the typical role in a more classic waterfall approach. Using an updated interpretation of ‘viewpoints and perspectives’, this talk will demonstrate how to make rapid, agile delivery sustainable. These viewpoints and perspectives will be linked to easy-to-produce models that can be used immediately in your projects. The talk will provide examples on how to determine which models are architecturally significant and worth the effort. Developers have always been very important stakeholders of an architectural description. A good agile architect needs to strive for consensus and buy-in.

Pragmatic Architecture (SATURN 2017)

Third iteration of my pragmatic architecture talk. This version is tailored for architects. I presented it at the SATURN 2017 conference in Denver, Colorado. Software development has evolved. Agile is now the de-facto standard. The role of an architect in an agile project is very different than the typical role in a more classic waterfall approach. Using an updated interpretation of ‘viewpoints and perspectives’, this talk will demonstrate how to make rapid, agile delivery sustainable. These viewpoints and perspectives will be linked to easy-to-produce models that can be used immediately in your projects. The talk will provide examples on how to determine which models are architecturally significant and worth the effort. Developers have always been very important stakeholders of an architectural description. A good agile architect needs to strive for consensus and buy-in.

Dip ppt

keekezu

The document discusses a design innovation project for TOG, a company that pioneered shared workspaces in Britain. TOG was founded in 2003 to reconfigure the modern British workplace in response to new technology and ideas radically reshaping the global economy. The company's vision was to create beautifully designed buildings with a variety of spaces and flexible leases to allow for growth and change. Each TOG building has its own identity but provides excellent facilities and communal areas to foster collaboration. The case brief examines opportunities and challenges for TOG's business model and service design to meet customer needs affordably while protecting privacy and improving competitiveness against growing competitors.

What is DevOps?

Matti Klasson

This document provides information about DevOps including: 1. Contact information for Matti Klasson, an Agile Management Coach and information about previous DevOpsDays conferences. 2. It discusses the key aspects of DevOps including culture and environment, processes like standardization and automation, and using common tools. 3. It includes quotes defining DevOps as a practitioner-led knowledge movement and emphasizing the importance of collaboration between developers and operations.

121203DO IT WITH DROOG

Yuichi Hirose

This document discusses downloadable design and how it aims to streamline the design process by eliminating transportation and stock needs. It proposes creating a platform for co-creation that allows end users to customize designs and designers to collaborate. The goal is to establish an alternative system to mass production that is locally-based and solves problems caused by globalization while fostering community.

DRIVE 2017 | 25 October - VALUE CREATION - Crossovers

CLICKNL

Creative professionals, independent of the context they work in, will face changes that are the result of their new tasks, role and responsibility. They will have to learn to deal with the digital transition, with thinking in systems while considering the human experience, and with the fact that their ‘products’ are to be permanently monitored and modified. Additionally, there is a growing collection of considerations and stakeholders that they have to involve in their design. These challenges are echoed in the demands we place on their competencies, the way they realize value and leverage (unconventional) resources to achieve their goals.

FROM DISTRO TO CUSTOM - HOW WE CREATE GREAT COMMUNITIES FOR EVERY ORGANIZATIO...

DrupalCamp Kyiv

GoalGorilla build with Open Social one of the biggest Distributions in Drupal. This distribution builds the foundation for over 1000 communities world wide. We build ourselfs some big communities for clients like the UN, Greenpeace, the Dutch Government and others. All of this clients have a very specific profile and very specific needs. All of them are from different sectors: From NGOs, to Goverment organizations, Voluntary platforms, learning platforms and much more. As well all of our clients have at core a community the goals of the community and the key features for them to reach those goals are different every time. As much as we can rely on the distribution to cover the basics and a even more, every client is different and most bigger communities needs customizations to make the step from a good to a great community. With every new client new challenges arise. With this talk I want to share some of the insights we gathered over the last 3 years, talk about how to navigate the pitfalls of customizing a Distribution and show how we fit different platforms to the specific requirements of different clients. This talk is for: - Developers who use or want to use Open Social (We will discuss some modules we use and technical choices, but it will not be primarily a technical talk) - Professionals working with online communities - Project managers or Designers that need to conceptualize projects that are based on a Distribution https://drupalcampkyiv.org/node/77

Cloud-first for fast innovation

Empfohlen

Pragmatic Architecture, Today (v2)

Pragmatic Architecture (SATURN 2017)

Dip ppt

keekezu

What is DevOps?

Matti Klasson

121203DO IT WITH DROOG

Yuichi Hirose

DRIVE 2017 | 25 October - VALUE CREATION - Crossovers

CLICKNL

FROM DISTRO TO CUSTOM - HOW WE CREATE GREAT COMMUNITIES FOR EVERY ORGANIZATIO...

DrupalCamp Kyiv

Cloud-first for fast innovation

The layperson's guide to software architecture

The document provides an overview of software architecture concepts for laypersons. It defines an architect as someone who investigates problems, partitions systems, makes plans while considering the big picture, decides tradeoffs, grows team skills, and manages technical debt. Software architecture is described as significant design decisions that shape a system based on cost of change. Key aspects of design thinking discussed are preserving ambiguity, recognizing that all design requires redesign, making designs tangible, and designing for humans. The document also covers who makes decisions, with architects accountable for quality attributes and risk, and discusses investing optimal time in architecture upfront to reduce long-term rework costs.

Infrastructure architecture

Omar Baqueiro Espinosa

The document discusses infrastructure architecture and is presented in an agenda format covering semantics, architecture, and engineering. It emphasizes that infrastructure is critical for success and availability should be prioritized over reliability. When architecting infrastructure, the document recommends decomposing components, anticipating failure, quantifying risks and needs, and ensuring redundancy and automation. The engineering section stresses leveraging the cloud, automating everything, implementing monitoring, and developing custom solutions when needed.

Closing the loop in the OpenStack development process, Thierry Carrez, OpenSt...

OW2

6+1 Technical Tips for Tech Startups (2023 Edition)

Ahmed Misbah

In 2019, the failure rate of startups was 90%. Technology Startups (aka. Tech Startups) had the highest rate of failures at 63%. One of the causes of this high rate in tech startups can be wrong technical decisions and practices. In this session, I describe 6 technical tips that can help tech startups truly become “Lean” to pave the way for success. The 6 technical tips will cover areas such as programming languages, development platforms, cloud-native architectures, testing, and big data. The session will conclude with BONUS technical tips for all startups and not just tech startups. These bonus tips will prove very useful for: 1- Startups wishing to launch new apps with very little experience in software development OR 2- Companies wishing to initiate startup projects as part of their digital transformation. I highly recommend this session for entrepreneurs who are about to start developing an innovative idea. It is also recommended for startups that have already started their journey and wish to improve.

The Cost of Microservices

Michael Nadel

Michael Nadel discusses Leadpages' journey from a monolithic architecture to microservices to Kubernetes. In 2016, Leadpages faced scaling challenges with their monolith and PaaS infrastructure, motivating a transition to microservices across 40 services. This introduced significant organizational, technical, and cultural challenges. By 2017, the operational complexity of microservices prompted a shift to Kubernetes which greatly simplified operations and reduced costs, realizing 60-75% compute savings through improved resource utilization. Key lessons included not underestimating cultural impacts, minimizing learning curves, and paying attention to cost models when changing architectures.

Distributed Agile: An Oxymoron?

The document discusses whether distributed agile development is an oxymoron. It notes that agile principles emphasize co-location and face-to-face communication. However, many organizations have distributed teams for cost or talent reasons. While distributed development seems easy in theory, in practice it is much harder as each physical boundary increases communication challenges. Successful distributed agile requires cross-functional teams, shared culture and environments, clear purpose and plans, frequent demos and visits, and continuous improvement of practices. With the right tools and emphasis on relationships, distributed agile can work but requires more effort than co-located development.

Strategic innovation

Pravin Asar

There are different Strategic Innovation methodologies, frameworks and models that aid organizations, particularly with technology driven, production companies. Most companies must innovate and continually improve to maintain a competitive advantage, but how they accomplish these process improvements differs significantly from Strategic Innovation. Traditional strategies rely on process improvements and product development through lessons learned, adoption of internal and external best practices, and improvements that are incremental and nature that are often found in Total Quality Management programs. Strategic Innovation requires a culture that can create breakthroughs within a company’s current market, and potentially enter a new market or segment. Strategic Innovation, and the implementation models that follow, are not for every organization, and a review of traditional strategies and risks associated with Strategic Innovation will be covered.

DevOps isn't something you buy - DevOpsDays Cape Town

How a Product Development Portal Can Help Turn Innovative Ideas Into Marketab...

rivetlogic

Excelling in a modern digital age is all about speed - speed of innovation, getting your products to market, and meeting your customer expectations. Bringing a new product to market involves multiple phases requiring participation from various teams across the organization, from idea conception to product development and launch. Without the right tools and processes in place, this could easily result in unnecessary miscommunications, delays, wasted efforts and costs, and could even sacrifice the quality of the outcome. This presentation discusses how an Ideation and Product Development Portal can help your business manage its end-to-end product development process, from ideation to product launch, with modern tools that help cultivate knowledge flow and innovation.

An Army of One? A Nation of Millions? Collaboration is not the key, it's the...

Christopher Cashdollar

The document discusses collaboration at Happy Cog, an experience design agency. It provides an overview of Happy Cog's process, which values collaboration, iteration, and flexibility. The process involves pairing collaborators from different roles to work together. Examples of collaborator pairings discussed include project managers working with information architects early in the process, and designers working with front-end developers. The document also discusses challenges in collaborating with clients from different industries and the need to adapt processes accordingly.

$The Cloud: CIO\'s Perspective$ $The Cloud: CIO\'s Perspective$

The Cloud: CIO\'s Perspective

Ivo Vachkov

This document discusses the CIO's perspective on cloud computing. It outlines some common misconceptions about public and private clouds. It also discusses challenges that CIOs face related to emerging cloud technologies, lack of control and standardization, and how the cloud tolerates the DevOps approach. The document concludes with lessons learned, emphasizing the importance of proper design for scaling, availability, growth and automation, as well as being proactive, testing assumptions, and embracing DevOps.

Integrated Project Delivery

Mike Purdy

The document discusses integrated delivery in construction projects. It defines integrated delivery as integrating owners, designers, and builders from the start to finish around mutual project outcomes. The presentation discusses the benefits of integrated delivery including reduced waste and costs, improved collaboration, earlier involvement of trades, and prefabrication opportunities. It provides perspectives from owners, architects, and builders and discusses contract structures and processes to support integrated project delivery. Examples of early adopters of integrated delivery models are also provided.

Overview of Modular Construction Triumph Modular 2017

This document discusses critical success factors for modular construction projects. Modular construction involves building components of a structure off-site in a controlled factory environment. Key considerations include committing to the modular concept early, ensuring close coordination between all project teams, and clearly defining roles and scopes of work. Modular construction can offer benefits like accelerated schedule, reduced disruptions on site, greater cost predictability and improved safety compared to traditional construction. However, it also requires addressing limitations related to module size and transport as well as changing perceptions about the technique.

Overview of Modular Construction

Architectural thinking - the Sucess Factor of Scaled Agile

Wolfgang Göbl

There is currently much debate about whether and how agility scales at the enterprise level. Many approaches exist, such as scaled Agile frameworks (SAFe, LeSS, DaD), Beta Codex, Beyond Budgeting, Sociocracy or Open Space, but success stories are rare.. Design thinking and Agile are the methods currently used to implement innovative point solutions at short notice. Companies rarely take enough time for long-term thinking. Fast innovation, sloppily integrated into the existing IT landscape, however, has lead to a complexity explosion that made IT tremendously expensive and increasingly sluggish for change. And this is not an IT problem but the result of bad funding decisions by business executives. Therefore it must be addressed at a business- and governance level, not by autonomous solution development teams. Many people of the Agile community perceive IT governance and architecture management as too rigid and heavyweight to be integrated with Agil. This is not surprising given the prevailing heavy and immature enterprise architecture frameworks and their ivory-tower use in practice. This presentation discusses why Agile will never scale without a consistent model of the business (=’business architecture’) that is understood, maintained an accepted by everybody, from CEO to software developer. It presents a lightweight, business-focused approach to architecture that should be integrated with common scaled agile frameworks (such as SAFe, LeSS, DaD) to really make them scale.

Product Development & Design for Additive Manufacturing (DfAM)

Katie Marzocchi

Product Development & DfAM in the Dawn of Digital Transformation Empire Group provides a glimpse into the future of product development and how an understanding of DfAM is critical to the success of PD professionals and manufacturers alike. You’ll learn some of the basic fundamentals of DfAM and see real-world design examples and optimizations from Empire Group’s Design & Engineering team. Website: www.empiregroupusa.com Phone: 508-222-3003 email: info@empirepd.com

Agile Architecture (MAE slides with speaker notes)

Richard Green

UX, Agile and product management

Phil Barrett

This document discusses user experience (UX), agile product management, and delivering software that meets user needs. It advocates for an iterative development process that incorporates UX research and testing. Product managers are advised to work closely with UX designers to validate assumptions through usability testing, measure outcomes, and prioritize addressing UX issues. An agile, lean approach that rapidly builds and learns from user feedback is presented as the best way to deliver innovative products that customers want and provide a competitive advantage.

You only have to change one thing to make DevOps work, Everything

The speaker discusses changes organizations can make to enable DevOps. They recommend: redefining terminology to fit the organization; structuring teams around products rather than functions; using modern architectures like microservices and containers; and implementing continuous delivery practices to deploy changes safely and frequently. The overarching message is that changing organizational culture and structure, not just processes or tools, is key to making DevOps work.

dradis Framework: Overview

etd

Dradis is a system designed for effectively sharing information among penetration testers. It uses a client-server architecture and multiple interfaces to allow information from tests to be organized, shared in real-time, and included in reports to save time and improve quality. The goals were to create an easy to use and flexible system that promotes effective knowledge sharing whether used by individuals or teams doing on-site testing.

Cloud-Native Architecture

Innovation Without Asking Permission

Are you working with an existing codebase? Do you want to use the cool libraries, tools or methodology you saw at this conference? This talk will show you how to combine legacy code with bleeding edge technology. Often the use of new technology and protocols is limited by fear of change in existing applications. Yet, as developers, we want to remain relevant and have fun with all the disruptive changes in our industry. This talk will drill-down from a high-level architectural view to the actual implementation of modern, strangling services in a legacy monolith, using DDD to define bounded contexts, in a safe and controlled manner.

Weitere ähnliche Inhalte

Ähnlich wie Pragmatic Architecture, Today.

The layperson's guide to software architecture

Infrastructure architecture

Omar Baqueiro Espinosa

Closing the loop in the OpenStack development process, Thierry Carrez, OpenSt...

OW2

6+1 Technical Tips for Tech Startups (2023 Edition)

Ahmed Misbah

The Cost of Microservices

Michael Nadel

Distributed Agile: An Oxymoron?

Strategic innovation

Pravin Asar

DevOps isn't something you buy - DevOpsDays Cape Town

How a Product Development Portal Can Help Turn Innovative Ideas Into Marketab...

rivetlogic

An Army of One? A Nation of Millions? Collaboration is not the key, it's the...

Christopher Cashdollar

$The Cloud: CIO\'s Perspective$ $The Cloud: CIO\'s Perspective$

The Cloud: CIO\'s Perspective

Ivo Vachkov

Integrated Project Delivery

Mike Purdy

Overview of Modular Construction Triumph Modular 2017

Overview of Modular Construction

Architectural thinking - the Sucess Factor of Scaled Agile

Wolfgang Göbl

Product Development & Design for Additive Manufacturing (DfAM)

Katie Marzocchi

Agile Architecture (MAE slides with speaker notes)

Richard Green

UX, Agile and product management

Phil Barrett

You only have to change one thing to make DevOps work, Everything

dradis Framework: Overview

etd

Ähnlich wie Pragmatic Architecture, Today. (20)

The layperson's guide to software architecture

Infrastructure architecture

Closing the loop in the OpenStack development process, Thierry Carrez, OpenSt...

6+1 Technical Tips for Tech Startups (2023 Edition)

The Cost of Microservices

Distributed Agile: An Oxymoron?

Strategic innovation

DevOps isn't something you buy - DevOpsDays Cape Town

How a Product Development Portal Can Help Turn Innovative Ideas Into Marketab...

An Army of One? A Nation of Millions? Collaboration is not the key, it's the...

$The Cloud: CIO\'s Perspective$ $The Cloud: CIO\'s Perspective$

The Cloud: CIO\'s Perspective

Integrated Project Delivery

Overview of Modular Construction Triumph Modular 2017

Overview of Modular Construction

Architectural thinking - the Sucess Factor of Scaled Agile

Product Development & Design for Additive Manufacturing (DfAM)

Agile Architecture (MAE slides with speaker notes)

UX, Agile and product management

You only have to change one thing to make DevOps work, Everything

dradis Framework: Overview

Mehr von Bart Blommaerts

Cloud-Native Architecture

Innovation Without Asking Permission

JavaDay 2017: 10 tips to become an awesome technical lead (v4)

Updated slidedeck for JavaDay, currently with 12 tips. As you grow in your career, chances are that one day you will end up as the Technical Lead of 1 or more projects. Often not by choice. The role of Technical Lead is quite different from the role of (senior) Software Developer and this talk will bring you answers on questions like: * How do I do technical interviews? * How do I lead a team? How do I lead multiple teams? * How do I cope with my new responsibilities? * How do I cope with success / failure? * How do I prevent losing focus on the technical challenges? * … In summary, everything you want(ed) to know on your first day as a Technical Lead and that you can use every day from that point onwards.

JavaOne 2017: 10 tips to become an awesome Technical Lead (v3)

As you grow in your career, chances are that one day you will end up as the Technical Lead of 1 or more projects. Often not by choice. The role of Technical Lead is quite different from the role of (senior) Software Developer and this talk will bring you answers on questions like: - How do I do technical interviews? - How do I lead a team? How do I lead multiple teams? - How do I cope with my new responsibilities? - How do I cope with success / failure? - How do I prevent losing focus on the technical challenges? - … In summary, everything you want(ed) to know on your first day as a Technical Lead and that you can use every day from that point onwards.

10 tips to become an awesome Technical Lead v2 (Devoxx PL)

10 tips to become an awesome technical lead

As you grow in your career, chances are that one day you will end up as the Technical Lead of 1 or more projects. Often not by choice. The role of Technical Lead is quite different from the role of (senior) Software Developer and this talk will bring you answers on questions like: • How do I do technical interviews? • How do I lead a team? How do I lead multiple teams? • How do I cope with my new responsibilities? • How do I cope with success / failure? • How do I prevent losing focus on the technical challenges? In summary, everything you want(ed) to know on your first day as a Technical Lead and that you can use every day from that point onwards.

Serverless as a Collaborative Economy Enabler

In recent years, the uprise of the cloud has brought us a lot of new and disruptive technology. Everybody is talking about SaaS, PaaS, IaaS and other aaS’es. In 2014 Amazon launched AWS Lambda as the pinnacle of the cloud computing. It allows developers to focus on code, without spending time on managing servers. The goal of this talk is not only introducing the serverless architecture style, but also tackle popular myths regarding “No More Servers” and “No More Ops”. Throughout the talk, we will focus on a “collaborative economy” approach to explain these concepts.

The Serverless Cloud @ JAX London 2016

In recent years, the uprise of the cloud has brought us a lot of new and disruptive technologies. Everybody is talking about SaaS, PaaS, IaaS and other sorts of aaS. In 2014, Amazon launched AWS Lambda as the pinnacle of the cloud computing. It allows developers to focus on code, without spending time on managing servers. The goal of this talk is to introduce the serverless architecture style, but it will also contain demos (eg. using AWS Lambda and Google Cloud Functions) on how to make this style work. Expect Lambda functions in NodeJS, using DynamoDB, consuming other functions via the AWS API Gateway. The talk will conclude with best practices on how to use these serverless functions.

The Collaborative Economy

JavaOne: Efficiently building and deploying microservices

Since Martin Fowler’s article on microservices in the beginning of 2014, there has been a lot of controversy about the topic. Although most articles talk about microservices from an architectural perspective, this session intends to go further and also provide examples of and best practices for building and deploying polyglot applications in an enterprise Java environment. In the session, the build process focuses on efficiency and shows that microservices don’t necessarily cause overhead for a project. Microservices don't imply copying and pasting the same boilerplate code over and over. The deployment process in the presentation is, of course, automated but also demonstrates best practices for integration testing between different active services.

e-IB Bouwstenen: Magda

Developing applications for the cloud

As we know, HP is all about "The New Style of IT". To achieve this, HP has highlighted 4 Big Bets: Cloud, Security, Mobility and Big Data. Bart Blommaerts, Expert Information Developer, is going to talk about “Developing applications for the Cloud“. Bart will focus on these questions: Why do we want applications in the cloud? Which applications do we want in the cloud? What methodology do we need to use, to move to the cloud? Does the cloud have implications on how applications should be developed? Bart will demonstrate potential pitfalls, and explain the HP approach that aims to avoid issues on the performance, elasticity, resilience and security of Cloud applications. This brown bag session will be an incremental update of a presentation Bart did at HP Discover in Barcelona last year. It is about concepts and methodology, not about technical implementation.

Java security

This document discusses secure connections in Java using SSL/TLS. It provides information on key concepts like keystores, certificates, and truststores. It also demonstrates how to set up a basic client-server application with mutual authentication using self-signed certificates and keytool to generate and manage the certificates. Troubleshooting tips are provided for common exceptions encountered.

Code Quality Assurance

The document discusses code quality assurance and clean code. It begins with an agenda covering why clean code is needed, what constitutes clean code, how to write and test clean code, and how to measure code quality. Writing clean code makes code easier to read, understand and maintain. Clean code follows principles like the single responsibility principle and boy scout rule. Code quality can be measured using tools like Sonar that integrate with build systems like Maven and Ant. While primarily focusing on making code work, practices like clean code aim to produce well-structured and maintainable code.

HP Discover - Developing new applications for the cloud