Why We Need Architects (and Architecture) on Agile ProjectsRebecca Wirfs-Brock
This is an updated version of this talk which I will present at Agile 2013.
The rhythm of agile software development is to always be working on the next known, small batch of work. Is there a place for software architecture in this style of development? Some people think that software architecture should simply emerge and doesn’t require ongoing attention. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration. Complex software systems have lots of moving parts, dependencies, challenges, and unknowns. Counting on the software architecture to spontaneously emerge without any planning or architectural investigation is at best risky.
So how should architecting be done on agile projects? It varies from project to project. But there are effective techniques for incorporating architectural activities into agile projects. This talk explains how architecture can be done on agile projects and what an agile architect does.
Talk I gave at the IT Architect Regional Conference in Phuket Thailand on October 8th, 2009. Full title as given was "Agile Architecture: A practical approach for combining holistic design with process agility". Happily it seemed to be well received.
This keynote was presented by Rebecca Wirfs-Brock at Explore DDD 2017.
The ouroboros (οὐροβόρος in the original Greek) is an image or archetype of a serpent shaped into a circle, clinging to or devouring its own tail in an endless cycle of self-destruction, self-creation, and self-renewal. Becoming a good software designer sometimes feels like that.
Over time, we build up our personal toolkit of design heuristics. To grow as designers, we need to do more than simply design and implement working software. We need to examine and reflect on our work, put our own spin on the advice of experts, and continue to learn better ways of designing.
We now acknowledge that complete upfront requirements is an impossible mission. Agile approaches have emerged as a way to manage the creation of systems that can never be completely defined and are certain to change.
But what about architecture and design for these systems? How much is the right amount? How do you plan for emergent design? What is the architect's role on an agile project?
Topics include:
- Role of the agile architect
- Agile design
- Keeping change easy
- Reducing technical risks
- Capturing non-functional and technical requirements and constraints
- Dealing with technical debt
- Addressing architectural concerns within the Scrum framework
- Tests – They're not just for finding bugs
- Architecture anti-patterns
Agile Architecture Agile Dev Practices 2013 KeynoteAdam Boczek
Keynote: Agile Dev Practices 2013
Adam Boczek, codecentric – “Agile Architecture – Yet Another Oxymoron?”
We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customer’s software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on…
In this talk I won’t give you perfect answers to all these questions, however I’m pretty sure I will open your eyes and let you create your own point of view.
Why We Need Architects (and Architecture) on Agile ProjectsRebecca Wirfs-Brock
This is an updated version of this talk which I will present at Agile 2013.
The rhythm of agile software development is to always be working on the next known, small batch of work. Is there a place for software architecture in this style of development? Some people think that software architecture should simply emerge and doesn’t require ongoing attention. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration. Complex software systems have lots of moving parts, dependencies, challenges, and unknowns. Counting on the software architecture to spontaneously emerge without any planning or architectural investigation is at best risky.
So how should architecting be done on agile projects? It varies from project to project. But there are effective techniques for incorporating architectural activities into agile projects. This talk explains how architecture can be done on agile projects and what an agile architect does.
Talk I gave at the IT Architect Regional Conference in Phuket Thailand on October 8th, 2009. Full title as given was "Agile Architecture: A practical approach for combining holistic design with process agility". Happily it seemed to be well received.
This keynote was presented by Rebecca Wirfs-Brock at Explore DDD 2017.
The ouroboros (οὐροβόρος in the original Greek) is an image or archetype of a serpent shaped into a circle, clinging to or devouring its own tail in an endless cycle of self-destruction, self-creation, and self-renewal. Becoming a good software designer sometimes feels like that.
Over time, we build up our personal toolkit of design heuristics. To grow as designers, we need to do more than simply design and implement working software. We need to examine and reflect on our work, put our own spin on the advice of experts, and continue to learn better ways of designing.
We now acknowledge that complete upfront requirements is an impossible mission. Agile approaches have emerged as a way to manage the creation of systems that can never be completely defined and are certain to change.
But what about architecture and design for these systems? How much is the right amount? How do you plan for emergent design? What is the architect's role on an agile project?
Topics include:
- Role of the agile architect
- Agile design
- Keeping change easy
- Reducing technical risks
- Capturing non-functional and technical requirements and constraints
- Dealing with technical debt
- Addressing architectural concerns within the Scrum framework
- Tests – They're not just for finding bugs
- Architecture anti-patterns
Agile Architecture Agile Dev Practices 2013 KeynoteAdam Boczek
Keynote: Agile Dev Practices 2013
Adam Boczek, codecentric – “Agile Architecture – Yet Another Oxymoron?”
We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customer’s software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on…
In this talk I won’t give you perfect answers to all these questions, however I’m pretty sure I will open your eyes and let you create your own point of view.
This presentation by Excella Consulting's Shahed Chowdhuri and Sahil Talwar covers EF Code First Migrations and Lean Enterprise Architecture Design.
Including:
- How we use EF Code First Migrations to keep our developers' databases in sync, automatically deploy updates using TeamCity and work with DB Architects who utilize tools like ER/Studio.
- Real world examples to explain how to combat over engineering in an enterprise application through lean startup principles.
The tension between agile and architecturePeter Hendriks
Agile and architecture are often considered cats and dogs. Many "classic" software architecture methods are considered an enemy of agile principles: often describing heavyweight, upfront documents and decisions, and a hierarchy with architects wielding all technical decision power and responsibility.
Although there are some new "agile architecture" concepts out there, these typically only address small parts of the problem and often require significant skill to practice correctly. There is even the notion that architecture is not needed anymore when applying agile practices.
But what is "architecture" anyway? This infodeck gives an overview on architecture as a concept, a process and a role. It is delivered as stand-alone slides, and should be useful for anyone involved in building software systems.
As Allen Brown admitted in my August 2013 Forbes article on TOGAF, “EA needs to catch up with the agile approach, not ‘Agile as such’.” This confusion over the word “agile” is actually one of the challenges with EA today. Brown continued: “‘Agile’ is a loaded term and largely associated with building solutions rather than the Enterprise Architecture.”
So, what does "agile" -- or in some quarters, "Agile" -- mean today, and how do we apply Agile to architecture? Most people use the phrase "Agile Architecture" to refer to software architecture appropriate for Agile software development projects -- not EA at all.
Nevertheless, there is a growing Agile EA movement that extends the core principles of the Agile manifesto to EA more broadly. This approach deemphasizes the role of frameworks and other artifacts, and instead treats the enterprise as a complex adaptive system.
Agile EA thus leverages complex systems theory, including the role of emergent properties, to rethink how organizations innovate and otherwise deal with change within the context of market and regulatory constraints.
Sandeep Paudel presented on "Beyond Scrum and SAFe - How to Choose the Right Framework for your Teams or Organizations" at the DC Scrum User Group (DCSUG) on June 11, 2021.
Are you confused why Scrum is not working for your software development teams; then you moved to Kanban, which turned out to be a worse decision too. In this presentation, I will share the importance of the Strategic Product Development Life Cycle and not just the Software Development Life Cycle (SDLC) when building software products. You will uncover the Cynefin Framework and how you can apply it to your use case to find the Right Software Delivery Framework for your Teams and Organizations.
One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.
What is Agile & Agile Project Management?. Introduction to Plan-based vs value-driven development; Scrum framework and roles and ceremonies; self-organised team, agile values. and leadership
MX: Managing Experience | Day 2 - Designing Delivery: A Unified Approach to D...Adaptive Path
The digital service economy demands the ability to create coherent user experiences while achieving end-to-end agility and efficiency. The ability to deliver them together requires seamless system, process, and organizational design. Companies need a unified approach to design and operations that centers the entire organization around helping customers achieve their goals.
This workshop teaches participants how to connect user-centered design to the entire service delivery lifecycle. It introduces a holistic approach that interconnects marketing, design, development, and operations into a circular design/operations loop. Through talks, discussions, and guided exercises, participants learn how to improve both customer satisfaction and operational effectiveness by:
-designing for service, not just software
-minimizing latency and maximizing feedback throughout the organization
-designing for failure and operating to learn
-using operations as input to design
ITIL and DevOps at War in the Enterprise - DevOpsDays Amsterdam 2014Jan-Joost Bouwman
The journey from ITIL/CMMi to DevOps in the corporate setting of ING Netherlands. Presentation by Mark Heistek and Jan-Joost Bouwman at DevOpsDays Amsterdam 2014.
IASA 2014 Conference - Cape Town, South Africa #iasa2014Karen Du Toit
Report back about attending the most recent International Association of Sound and Audiovisual Association Conference in Cape Town from 5 - 9 October 2014
Only possible to mention but a few of the papers that were read.
Information about the conference can be found here: http://2014.iasa-web.org/
This presentation by Excella Consulting's Shahed Chowdhuri and Sahil Talwar covers EF Code First Migrations and Lean Enterprise Architecture Design.
Including:
- How we use EF Code First Migrations to keep our developers' databases in sync, automatically deploy updates using TeamCity and work with DB Architects who utilize tools like ER/Studio.
- Real world examples to explain how to combat over engineering in an enterprise application through lean startup principles.
The tension between agile and architecturePeter Hendriks
Agile and architecture are often considered cats and dogs. Many "classic" software architecture methods are considered an enemy of agile principles: often describing heavyweight, upfront documents and decisions, and a hierarchy with architects wielding all technical decision power and responsibility.
Although there are some new "agile architecture" concepts out there, these typically only address small parts of the problem and often require significant skill to practice correctly. There is even the notion that architecture is not needed anymore when applying agile practices.
But what is "architecture" anyway? This infodeck gives an overview on architecture as a concept, a process and a role. It is delivered as stand-alone slides, and should be useful for anyone involved in building software systems.
As Allen Brown admitted in my August 2013 Forbes article on TOGAF, “EA needs to catch up with the agile approach, not ‘Agile as such’.” This confusion over the word “agile” is actually one of the challenges with EA today. Brown continued: “‘Agile’ is a loaded term and largely associated with building solutions rather than the Enterprise Architecture.”
So, what does "agile" -- or in some quarters, "Agile" -- mean today, and how do we apply Agile to architecture? Most people use the phrase "Agile Architecture" to refer to software architecture appropriate for Agile software development projects -- not EA at all.
Nevertheless, there is a growing Agile EA movement that extends the core principles of the Agile manifesto to EA more broadly. This approach deemphasizes the role of frameworks and other artifacts, and instead treats the enterprise as a complex adaptive system.
Agile EA thus leverages complex systems theory, including the role of emergent properties, to rethink how organizations innovate and otherwise deal with change within the context of market and regulatory constraints.
Sandeep Paudel presented on "Beyond Scrum and SAFe - How to Choose the Right Framework for your Teams or Organizations" at the DC Scrum User Group (DCSUG) on June 11, 2021.
Are you confused why Scrum is not working for your software development teams; then you moved to Kanban, which turned out to be a worse decision too. In this presentation, I will share the importance of the Strategic Product Development Life Cycle and not just the Software Development Life Cycle (SDLC) when building software products. You will uncover the Cynefin Framework and how you can apply it to your use case to find the Right Software Delivery Framework for your Teams and Organizations.
One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.
What is Agile & Agile Project Management?. Introduction to Plan-based vs value-driven development; Scrum framework and roles and ceremonies; self-organised team, agile values. and leadership
MX: Managing Experience | Day 2 - Designing Delivery: A Unified Approach to D...Adaptive Path
The digital service economy demands the ability to create coherent user experiences while achieving end-to-end agility and efficiency. The ability to deliver them together requires seamless system, process, and organizational design. Companies need a unified approach to design and operations that centers the entire organization around helping customers achieve their goals.
This workshop teaches participants how to connect user-centered design to the entire service delivery lifecycle. It introduces a holistic approach that interconnects marketing, design, development, and operations into a circular design/operations loop. Through talks, discussions, and guided exercises, participants learn how to improve both customer satisfaction and operational effectiveness by:
-designing for service, not just software
-minimizing latency and maximizing feedback throughout the organization
-designing for failure and operating to learn
-using operations as input to design
ITIL and DevOps at War in the Enterprise - DevOpsDays Amsterdam 2014Jan-Joost Bouwman
The journey from ITIL/CMMi to DevOps in the corporate setting of ING Netherlands. Presentation by Mark Heistek and Jan-Joost Bouwman at DevOpsDays Amsterdam 2014.
IASA 2014 Conference - Cape Town, South Africa #iasa2014Karen Du Toit
Report back about attending the most recent International Association of Sound and Audiovisual Association Conference in Cape Town from 5 - 9 October 2014
Only possible to mention but a few of the papers that were read.
Information about the conference can be found here: http://2014.iasa-web.org/
Why IT needs more IT Architects (IASA style)Paddy Baxter
This is a deck I presented to IT leaders in the public sector. In it I explain the IASA definition of IT Architect and how in-house tech leaders can deliver substantially to their teams, IT and their whole organisation by focusing on the skills IASA defines as required for a high performing IT architect.
Iasa Architect responsibilities in the cloudiasaglobal
Cloud platforms drive marketing campaigns that offer to simplify the hardest challenges of information technology. From resilience to scalability, disaster recovery to management, the cloud platforms offer to take the challenge off of the table forever! It can be easy to ?buy in? to the platform. Too often, we find out later that our responsibility as architects cannot ?end at the door? to the provider, that there are provisos and implementation considerations we discover ? often after the provider falls down.
Title: The Role of the Software Architect
Speaker: Hayim Makabee, co-founder of the Israeli Chapter of the International Association of Software Architects (IASA)
Abstract:
In this talk Hayim will present the practical aspects of the role of the Software Architect, including:
- The four areas of expertise: Design, Domain, Technology and Methodology.
- The cooperation with stakeholders: Developers, Team Leaders, Project Managers, QA and Technical Writers.
Understanding the expected areas of expertise is essential for the architect to develop his/her professional skills.
Understanding how to cooperate with the diverse stakeholders is essential to improve the architect's impact and effectiveness.
A Top 10 Key to Success for Architects, delivered by author Pete Eeles, IBM, hosted on the "Good Design is Good Business" group on developerWorks: https://www.ibm.com/developerworks/mydeveloperworks/blogs/669242b1-dd91-4d63-a08f-231314c793bb/entry/top_10_success_secrets_for_software_architects_good_design_is_good_business_series?lang=en
Are You an Accidental or Intention Software ArchitectRandy Ynchausti
This presentation challenges viewers to consider what knowledge body and skills base a professional software architect possesses. It was presented originally at the UT IASA Chapter meeting November 21, 2013.
This lecture describes the Platform model or Two-sided Markets. Platforms serve multiple customer groups and benefit from network effects that take place with and between those groups. Businesses based on Platforms are able to adopt innovative pricing structures in which one side subsidizes another. When the marginal costs are near zero it can be practical to drop the subsidized price all the way to zero.
Structured Approach to Solution ArchitectureAlan McSweeney
The role of solution architecture is to identify answer to a business problem and set of solution options and their components. There will be many potential solutions to a problem with varying degrees of suitability to the underlying business need. Solution options are derived from a combination of Solution Architecture Dimensions/Views which describe characteristics, features, qualities, requirements and Solution Design Factors, Limitations And Boundaries which delineate limitations. Use of structured approach can assist with solution design to create consistency. The TOGAF approach to enterprise architecture can be adapted to perform some of the analysis and design for elements of Solution Architecture Dimensions/Views.
The Framework for Agile Living Labs (FALL) projects aim to provide practitioners with actionable guidelines on how to run a Living Lab project in an agile way. Developed by imec.livinglabs
Tips and techniques for writing smarter user stories to support Agile teams.
For Scrum and Kanban projects.
Sasan Afsoosi
Enterprise Agile Coach
May 2020
In this advanced business analysis training session, you will learn Use Cases and Its use in Agile World. Topics covered in this session are:
• Requirements Principles
• Identify the principles that lead to effective Agile requirements
• Setting the Stage for Requirements
• Establish the vision as the foundation of Agile requirements
• Levels of Agile Requirements
• Identify the different level of Agile requirements for effective requirements
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
Why should you use User Stories? What is specification by example?
What is a valid role (As a...)
This presentation covers some of the concepts and uses of user stories
Life cycle of user story: Outside-in agile product management & testing, or...Ravi Tadwalkar
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
Defining work items is a challenge. We could argue that a work item is anything that is delivered to the customer.
As much as we've been trying and done some good work on defining user stories over the last decade it’s still a major source of confusion for a lot of projects.
Let’s try another way using examples or scenarios.
User Story Mapping Definitions & Basics - StoriesOnBoard.pdfStoriesOnBoard
User Story Mapping Definitions & Basics - by StoriesOnBoard
Learn more & start your 14-day free trial: https://storiesonboard.com/
- How to start story mapping
- Definitions
- Basics
- What is user story mapping?
- How do you conduct a story mapping session?
- What does a story map consist of?
- Who created story mapping?
- What is the lifecycle of story mapping?
- What is a user story workshop?
- Why is story mapping important?
- How do you make a story map?
- What is user story in Agile?
- How to write a good story?
- How do you use story mapping?
- User goals & steps in a narrative flow
- Who writes a user story?
- What is user persona on the story map?
- What are releases?
- How to brainstorm user stories?
- Why is prioritization crucial while working with user stories?
- How to convert a story map into conventional product backlog?
- What is MVP release?
- What is the difference between epics and user stories?
StoriesOnBoard is a visual and collaborative story mapping tool to prioritize the customer value sprint by sprint.
Build your story map on StoriesOnBoard.com
User Story Canvas by Maksim Gaponov
Next webinars:
In Search for Team's Efficiency https://attendee.gotowebinar.com/register/471689760712542978?source=slideshare
Best Tools to Develop Soft Skills in Scrum and Agile Development https://attendee.gotowebinar.com/register/3974870146644735746?source=slideshare
Building shared understanding in a scaled and distributed Agile environment is a challenge. The big picture view of a product is often lost, team members in one location are not aware of activities in other locations, and everyone is using their own standards – all while common misunderstandings of the User Story concept create an even bigger mess.
At Luxoft Agile Practice, we have developed a special tool for discussing and documenting User Stories. We call it User Story Canvas.
Similar to User story estimation with agile architectures (20)
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
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
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/
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Welocme to ViralQR, your best QR code generator.ViralQR
Welcome to ViralQR, your best QR code generator available on the market!
At ViralQR, we design static and dynamic QR codes. Our mission is to make business operations easier and customer engagement more powerful through the use of QR technology. Be it a small-scale business or a huge enterprise, our easy-to-use platform provides multiple choices that can be tailored according to your company's branding and marketing strategies.
Our Vision
We are here to make the process of creating QR codes easy and smooth, thus enhancing customer interaction and making business more fluid. We very strongly believe in the ability of QR codes to change the world for businesses in their interaction with customers and are set on making that technology accessible and usable far and wide.
Our Achievements
Ever since its inception, we have successfully served many clients by offering QR codes in their marketing, service delivery, and collection of feedback across various industries. Our platform has been recognized for its ease of use and amazing features, which helped a business to make QR codes.
Our Services
At ViralQR, here is a comprehensive suite of services that caters to your very needs:
Static QR Codes: Create free static QR codes. These QR codes are able to store significant information such as URLs, vCards, plain text, emails and SMS, Wi-Fi credentials, and Bitcoin addresses.
Dynamic QR codes: These also have all the advanced features but are subscription-based. They can directly link to PDF files, images, micro-landing pages, social accounts, review forms, business pages, and applications. In addition, they can be branded with CTAs, frames, patterns, colors, and logos to enhance your branding.
Pricing and Packages
Additionally, there is a 14-day free offer to ViralQR, which is an exceptional opportunity for new users to take a feel of this platform. One can easily subscribe from there and experience the full dynamic of using QR codes. The subscription plans are not only meant for business; they are priced very flexibly so that literally every business could afford to benefit from our service.
Why choose us?
ViralQR will provide services for marketing, advertising, catering, retail, and the like. The QR codes can be posted on fliers, packaging, merchandise, and banners, as well as to substitute for cash and cards in a restaurant or coffee shop. With QR codes integrated into your business, improve customer engagement and streamline operations.
Comprehensive Analytics
Subscribers of ViralQR receive detailed analytics and tracking tools in light of having a view of the core values of QR code performance. Our analytics dashboard shows aggregate views and unique views, as well as detailed information about each impression, including time, device, browser, and estimated location by city and country.
So, thank you for choosing ViralQR; we have an offer of nothing but the best in terms of QR code services to meet business diversity!
3. Who I am
Raffaele Garofalo
IASA Member
Software Architect
Kitesurf addict
Contacts
Twitter: @Raffaeu
Blog: http://blog.raffaeu.com/
Mail: raffaeu@gmail.com
4. Introduction to Agile Architecture
What is agile architecture?
Agile Architecture key objectives
Agile Architecture principles
5. What is Agile Architecture?
What?
Why?
The main concept that stays behind Agile Architecture is:
“Bring agility to architecture”
“Bring architecture into the Agile world”
Most Agile teams
believe that an
Architect is not
required
There are two major problems when we adopt Agile methodologies and bring them into our
environment:
Agile assumes that a software needs to be developed
Agile assumes that we have a sort of control on how the system is and will be built
How?
First of all we should be able to keep our agility while staying focus on the main picture, by
bringing architecture into agile and vice-versa
6. Agile Architecture key objectives
Also Agile Architecture has its own key objectives:
Deliver working solutions (a Diagram is not a working solution …)
Maximize Stakeholders’ values
Find a solution that meets the goals of all the Stakeholder
Enable the next effort
Being able to Manage changes and complexity
7. Agile Architecture principles
Value
People
Communicate
Less
is more
Embrace
Choose
Deliver
Model
changes: plan and deliver
the right solution for the Enterprise, not for your User Story
quality
and documentation in an Agile fashion
8. User Story
What is a User Story?
How can we add details to a User Story?
How you estimate a User Story?
Pitfalls of a User Story
9. What is a User Story?
User stories are short, simple description of a feature told from the perspective of the
person who desires the new capability, usually a user or customer of the system.
They typically follow a simple template:
“As a user, I can buy and sell stocks that are in my portfolio”
“As a portfolio manager user, I can act on portfolios for which I have permissions”
“As a user, I can reports that analyze my portfolios’ status”
10. As a USER, I can buy
and sell
STOCKS in my
Portfolio
11. How can we add details to a User Story?
Details can be added to user stories in two ways:
By splitting a user story into multiple, smaller user stories.
By adding “conditions of satisfaction.”
“When a relatively large story is split into multiple, smaller agile user stories, it is natural
to assume that detail has been added. After all, more has been written”
“The conditions of satisfaction is simply a high-level acceptance test that will be true
after the agile user story is complete”
12. User Story estimation
Pending
As a USER, I can buy
and sell
STOCKS in my
Portfolio
As a USER, I can buy
and sell
STOCKS in my
Portfolio
As a USER, I can buy
and sell
STOCKS in my
Portfolio
…
User
auth.
Port.
Mgmt
Docu
ment.
Stock
Search
Buy
mech.
Test
QA
2
4
8
16
13. What are the pitfalls of a User Story?
Even the best written user story leave room for interpretation and interpretation is not
design
Design is bring to the stakeholder when it’s ready and that’s the first time the
Stakeholder can start to ask for changes
The format of the user story is too agnostic. “As a User …”: which, how, when?
Sometimes stories become very big and the whole architecture is described in the
story details.
Unfortunately a User Story is not a technical document and it should not replace it
14. Common Estimation Mistakes
Don’t use Fibonacci, use the technique that fits your team (i.e. Power of 2 scale)
4 Values are more than enough to estimate a story
Define a size scale and stick on that
Vote independently
Always over estimate, never underestimate cause you will always forget about a
requirement or impediment
No laptops/tablets and ask for participation
16. Definition
An Architecture View is
“Architecture views are representations of the overall architecture that are meaningful to one or
more stakeholders in the system”
An Architecture Viewpoint is
“A Viewpoint is an abstract model that can describe part of a View or a View in a specific context”
So in essence each viewpoint is an abstract model of how all the
stakeholders of a particular type see the overall system
20. Some Numbers - ROI
Return of Investment
” The term "return on investment" (ROI) is frequently used to describe the benefit derived
Formula:
ROI = (V1 – V0)
_____________
I
V0 Initial Value
V1 Later Value
I Capital invested
Example:
Team cost (month): 50,000 $
Current rev.: 300,000 $
Estimated: 550,000 $
Project est. : 26
Team Velocity (be-week): 5
Result:
(550,000 – 300,000) / ((26/5*2)/4.5 *
50,000)
26/5*2 = num of weeks
/ 4.5 = num of months
211% we spend 115K but gain 250K
21. The estimation game
Provide to an Agile Team few stories in the form of Comics
Provide a simple View of the Architecture
Ask the teams to use a common estimation scale
Give two hours to provide viewpoints with estimation on it
23. TOGAF and estimation
PHASE A
LEARNING
EXPERTISE
ALGHORIT.
PHASE
C
PHASE D
PHASE E
PHASE F
PHASE G
PHASE H
Vision
GUESSING
PHASE B
Business
System
Technology
Opport.
Migration
Govern.
Change
Mgmt
WHYSoftware ArchitectIssues with Agile TeamsIssue in providing ROI without an architecture in placeDeveloped this session over my experiments with teams
BRIEF INTRODUCTIONHow I came to Agile ArchitectureWHEN should be adopted?ALWAYS, Working with Agile Teams, less formal Architecture is required
WHATAgile believe that every member can cover ANY positionWe know is not possible cause it requires experience and knowledgeArchitecture can be slow and too formal, we need a more agile way of using itIt’s hard to estimate the “architecture effort”WHYIt is not always is like thatSometimes the system is legacy, but we still need to do our jobSometimes we need to maintain an existing systemSometimes is not just about Software Development
Provide value work on SOLUTIONS, not DOCUMENTSTry to optimize solutions for multiple stakeholders to reduce cost and effortFind COMMON solutions for common GOALSYou should support it in the future WHETER change is requiredMinimize complexity to keep the solution maintainable
GOLDEN RULESPEOPLEit’s all about people, VALUE PEOPLE -> MOTIVATION is a great asset to haveCOMMICATIONCOMMUNICATE with every stakeholder, ask questions, provide mocks and views and discuss it, INVOLVE, promote DISCUSSION and FEEDBACKS are ALWAYS welcomeLESS IS MOREEVERYTHING you PROVIDE to stakeholders has a COST, cost of MAINTENANCE, LESS you provide to communicate, less it will cost in the FUTUREEBRANCE CHANGESMake your ARCHITECTURE AGILE not FRAGILE, be capable to ADAPT to the MARKET CHANGESCHOOSE RIGHT SOLUTION CATCH the VISION of the stakeholders, try to PICTURE a GLOBAL vision in order to find the RIGHT ARCHITECTUREDELIVER QUALITY QUALITY your architecture in AGILE WAY, TEST your views, TEST your visions and ideas using other ACTORSAGILE DOCUMENTATIONPURPOSE, REASON, MODEL only what is REQUIRED, SIMPLE
PROBLEMS?context? We don’t knowUser WHO, WHAT?Buy and sell, HOW, WHEN?MISS VISION and CONTEXT, does not express enough
AGILE SOLUTIONS? Add details …The things become more complex, we can have now multiple USER STORIESSub tasks of a story and bugs and other BACKLOG ITEMSWHERE IS the architecture? How can my team understand how to operate on THESE stories?
Ok we have increase the number of post-it, but still don’t see an ARCHITECTURE hereIS REQUIRED?Of course because now we have to estimate these post-it without a VISION in our mindsWHAT’S MISSING?A Vision, a View of the System, a Flow of what we should achieveWe need something QUICK, UNDERSTANDABLE, MAINTAINABLE and it should fits a rich AUDIENCE
INTERPRETATIONThe issue is that a SENTENCE on a BOARD can be read by ANY STAKEHOLDERS andINTERPRED in a different WAYFEEDBACKS are too lateWithout VIEWS, VIEWPOINTS, MOCKS you can’t communicate properly with the STAKEHOLDERS until some piece of software is READYNO SPECIFICATIONS, OFTEN TOO GENERICThink about the BUILDING ARCHITECT, without a blueprint how the customer knows the RESULT?No SPECIFICATIONS, no CONVENTIONSNOT A TECHNICAL DOCArchitecture should still have ITS OWN REPOSITORY, its own DOCUMENTATION, the backlog is not an ARCHITECTURAL repositoryUser Story provides a link to a TECHNICAL DOCUMENT (Visio, ArchiMate, PDF)
Fibonacci STRING are not always working with different BRAINS4 values EXAMPLE …After few ROUNDS use always the same SCALEWHY? Otherwise statistics are not correctVOTE ALONE, WHY? Juniors get influenced by SENIORS and vice-versaDevelopers are NOT ALWAYS architects, they DON”T HAVE VISION so often they under estimateNO DISTRACTION, is a TECHNICAL MEETING, AGILE but still FORMAL and TECHNICAL
When I discover views and view pointsWhy I believe there are different views and styles for different stakeholders
THIS is what most STAKEHOLDERS of ACME.com explain to meCan we consider this a VIEW? Or better a MOCKUP?
THIS is what most DEVELOPERS of ACME.com needs in order to estimate
Four different types of estimationGUESSINGHere you are really guessing what could be the potential costLEARNINGAcquiring knowledge to provide a better estimationEXPERTISEProvide feedbacks and estimation based on experienceALGHORIT.Provide estimation based on specific rulesA – Main Vision to get approval on the projectB – Business development to support the proposed VISIONC – Description of the information system architectureD – Describe the phase where technology comes into playE – Grouping implementation projects (high estimation required)F – Description of the process to move from an original solution to the final solution proposed in the Vision phaseG – Governance, restrict, organize provide constraints and policiesH – Maintenance phase/process
In SCRUM estimation happens in multiple places/times