The tension between agile and architecture
|
|
- Darleen Moore
- 6 years ago
- Views:
Transcription
1 The tension between agile and architecture Useful definitions on software design and architecture Peter Hendriks IT Architect at Info Support blogs.infosupport.com/peterhe/
2 Agile and architecture: cats and dogs? 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?
3 Architecture: a concept, process and role Like so many software development terms, "architecture" is not a very well defined thing. For starters, the term architecture is used for wildly different categories: The architecture concept: the notion that certain aspects and design choices of a system are more important and fundamental. The architecture process: the way architecture concerns are addressed in the way teams The architect role: the person considered responsible for architecture We ll look at each category to establish how "agile friendly" architecture actually is.
4 A definition of architecture: the concept "Worries about the hard stuff - whatever that organization thinks is hard - Martin Fowler and Ralph Johnson, thought leaders in agile and design, on architecture "Design is the structure or behavior of an system whose presence resolves or contributes to the resolution of forces on that system. - Grady Booch, one of the fathers of modern software design, on design "All architecture is design but not all design is architecture. Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change. - Grady Booch, now on architecture
5 Architecture versus design A design has correlated, but different goals. Design may be needed to allow communication, collaboration and complex problem solving. Since all architecture is design, these goals matter for architectural significant design decisions as well. Design often exists in multiple levels of detail, with the lowest level being the code. High level design is often considered the architecture. Most of the time this makes sense: high level design naturally contain a lot of decisions that are hard to change after the system is built. Considering high level design as the only architecture is risky: you might want to do too much of it, while missing decisions with a high cost of change at lower levels.
6 Architecture in the context of system design An example model of system design, relevant forces, and architecture Features Laws Security Monitoring & control Stakeholder needs Performance Operational costs Existing systems Common practices Environment Design System Design Future Technology changes Team changes Productivity Licensing deals Corporate standards Design Design Design Extendable Technology capabilities Framework support Achievability Team skills Project budget (time/money)
7 The need for the architecture concept in agile Architecture-as-a-concept assumes that certain parts of a system will be hard to change. It also assumes that design decisions here will be considered more significant, because of the greater short-term risk and possible long-term limitations for the evolution of the system. It's safe to say these assumptions are still valid for systems built in an agile fashion. Common agile practices, like automated testing and short iterations, drive down the overall cost of change. In that sense, agile reduces the amount of architecture needed. But there is no silver bullet here, there will still be "hard stuff". Making wrong decisions here will still seriously hurt or kill an agile project. The other way around, agile practices, like working in small teams, releasing early and often or being testable, often add extra demands on the system design, even at the architecture level. Also, some architectural design decisions, like applying modularity, may reduce cost of change and support other important agile values. In order for agile to be a successful approach to building a system, the architecture must support it.
8 So, where is the problem? Architecture still matters for agile projects. Some things that need to be built in almost every system just don't change easily after the fact. Only relying on "refactoring" will not cut it. There is very little debate on the need for architecture-as-aconcept in an agile project, once you focus on design decisions with a high cost of change. In some aspects, architecture is even a critical element for the success of important agile practices. However, when we look at architecture as a process, the tension becomes more apparent.
9 Defining the architecture process If we consider that architecture is about design decisions that have a high cost of change, then an architecture process should strive to lower the rate of change on these decisions once they are committed to. As a secondary goal, the process should help to identify what changes will be more costly to make, making the software development process more predictable and improving the confidence of the team. Agilists should feel a tension here. Lowering rates of change and long term predictions does not feel very agile. It isn't, and in a way, this is where the ideals of agile meet the boundaries of practical reality.
10 Why change a design decision? Reason for change: The decision was wrong; the resulting system does not work A change in a force invalidates the decision A more optimal decision is found Some countermeasures: Investigate unclear and changing forces Consult existing experience and expertise Early evaluation of the decision Delay the decision Add abstractions that are more stable Considering these goals, it becomes apparent that the architecture process should involve all disciplines in a software development team. Investigating and negotiating stable insight is key to predict whether the design decision will last for a longer period. Testing design assumptions as soon as possible and fixing problems before building an entire system on them can help immensely. Planning the system evolution around tough choices, or adding abstractions, can postpone or alleviate effects of change.
11 Deliberate vs accidental architecture During the evolution of a system, not all design decisions with a high cost of change are deliberately made using an architecture process. This design that just happens is often called accidental architecture. Accidental architecture can be a judgment- or communication problem, but also a learning effect of building the system. We should expect that while the system is being built, we may periodically need to evaluate which design decisions matter most, and if existing decisions need adjustments. Agile places heavy emphasis on feedback early and often. This is a big help for an architecture process. We can continuously evaluate design decisions using the real system as it s built. Also, we learn what matters for decisions that come up later.
12 Tools and practices for architecture processes There are many established software architecture tools and practices available. These vary from complete and specialized process frameworks like TOGAF to various notations and metamodels, like UML and ArchiMate, to best practices, like design patterns and the SOLID design principles. There are design tools, like Enterprise Architect, or code analysis tools like Structure101, that can be very useful, but require skill to use. Often, a whiteboard is used, easy for everyone to participate, without the distractions of having to operating a complex tool while thinking about a difficult problem. Personally, I believe all these methods and tools can be applied in an agile fashion, if used in a small package form. However, they are often marketed as big and overarching things. This results in a lot of resistance in agile teams.
13 The role of the architect So who is driving the architecture process? In the "classical" architecture process, an architect creates a detailed Big Design Up Front (BDUF). The architect is a senior specialist, who knows what's the best way to build the system and anticipates how design forces will behave during the lifetime of the system. He/she designs the system before the "construction" team starts, so they don t have to wait during the period needed to create the BDUF. Then, the process aggressively limits any deviation to the original architecture. As an industry, we have learned that this is an naïve approach. It assumes an all-knowing architect, a completely predictable future, and a team that just reads a document and then knows what to do. However, consider the architecture process we've just discussed. There is complex decision making, multi-discipline collaboration and communication, and specialized design methods and tools. Experience with both the problem domain and the technologies used to build the system are essential to effectively predict and communicate design decisions and their effects. Even in an agile team, this definitely seems like a candidate for a specialist role, especially for larger systems, where the amount of architecture rapidly increases and the stakes are much higher.
14 Is the architect part of the team? Agile focuses on small, empowered teams. In most cases, the biggest challenge for an architect is collaborating with everyone involved creating the system. From a team perspective, the best way to collaborate is to be part of the team. An architect ideally does hands-on work. Reading and writing code, for instance, is useful for a software architect to feel the effect of design decisions. It is also a great way to earn the respect of the team. Being part of the team makes it easier to do hands-on work. In larger enterprises, the architecture may span multiple teams and systems. In this case, the architect operates on a different level, often called enterprise architecture, outside the team. Usually, this architecture is perceived different, with other main stakeholders and design goals, but still is very important for a team building a system. For an architect, trust is a key aspect of being successful. Face-to-face communication and close collaboration, whether as formal part of the team or not, helps to build trust, and provides a lot of learning opportunities.
15 Wrap-up Software architecture is all about design decisions with a high cost of change This is the nature of complex system design; while agile reduces cost of change overall, it does not eliminate the need for critical elements to stay stable Architecture in your process is about managing these decisions This involves your entire team, and is needed throughout the lifetime of the system Architects should not be positioned as an all-knowing oracle But shaping a good architecture for a large enough system requires a lot of responibility, expertise and experience that should not be considered a common skill set Architecture is essential for agile success Systems built using agile need to work, and need to last, too Many agile practices rely on advanced architecture design
Chapter 3 Agile Software Development
Chapter 3 Agile Software Development Chapter 3 Agile Software Development Slide 1 Topics covered Rapid software development Agile methods Plan-driven vs. agile development Extreme programming (XP) Agile
More informationIntroduction to Agile/Extreme Programming
Introduction to Agile/Extreme Programming Matt Ganis, Senior Technical Staff Member (Certified Scrum Master) IBM Hawthorne, New York ganis@us.ibm.com August 2007 Session 8061 Current slides at: http://webpage.pace.edu/mganis
More informationLecture 1. Topics covered. Rapid p development and delivery is now often the most important requirement for software systems.
Chapter 3 Agile Software Development Lecture 1 Topics covered Agile g methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods Rapid software development
More informationBuilding a Platform for Innovation
10 October 2013 Building a Platform for Innovation Architecture and Agile as Key Enablers Peter Eeles FSS Industry Lead, IBM Rational Worldwide Tiger Team peter.eeles@uk.ibm.com Agenda 1 Introduction 2
More informationSoftware Processes. Chapter 2. CMPT 276 Dr. B. Fraser Based on slides from Software Engineering 9 th ed, Sommerville.
Software Processes Chapter 2 CMPT 276 Dr. B. Fraser Based on slides from Software Engineering 9 th ed, Sommerville. 18-05-15 Slides #4 1 Topics 1) What activities are part of software development 2) What
More informationSoftware Engineering Lecture 5 Agile Software Development
Software Engineering Lecture 5 Agile Software Development JJCAO Mostly based on the presentation of Software Engineering, 9ed Exercise Describe the main activities in the software design process and the
More informationLecture 8 Agile Software Development
Lecture 8 Agile Software Development Includes slides from the companion website for Sommerville, Software Engineering, 10/e. Pearson Higher Education, 2016. All rights reserved. Used with permission. Topics
More informationAgile Manifesto & XP
Agile Manifesto & XP Chapter 3.1-3.3 CMPT 276 Dr. B. Fraser Based on slides from Software Engineering 9 th ed, Sommerville. Slides 8 18-06-10 1 Topics 1) What is Agile trying to do? 2) How to choose plan-driven
More informationTopics to be covered. Commercial Levers Available to the PM to Manage Agile project delivery
Commercial Levers Available to the PM to Manage Agile project delivery Ash Forrester & Nick Semple, PA Consulting Group CCR: Strategic & Business Management 2016 Building Leaders for Business Topics to
More informationUser-centered System Design. Agile
User-centered System Design Agile Department of Information Technology Methods - what are they? Why do we have them? Business modeling Usability Design Requirements Analysis & design Implementation Test
More informationOi Requirements Communication in New Product Development
Steer Your Development! Goal-Oriented Oi Requirements Communication in New Product Development September 9, 2008 Samuel Fricker, Tony Gorschek, Martin Glinz Product Manager in Context: Simplified, Stylized
More informationOvercoming Waterfallacies and Agilephobias: Tales of Resistance and Woe
Overcoming Waterfallacies and Agilephobias: Tales of Resistance and Woe Mike Cohn December 5, 2007 1 Topics today... 1. Waterfallacies 2. AgilePhobias 3. Overcoming resistance 2 3 Waterfallacy noun. mistaken
More informationMike Vincent. mvasoftware.net
Scrum and ALM Coach Over 30 years as software developer and architect Marketing director, construction project manager and structural engineer previously Microsoft MVP - Visual Studio ALM Professional
More informationIntroduction to Agile Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016
Introduction to Agile Life Cycles CSCI 5828: Foundations of Software Engineering Lecture 07 09/13/2016 1 Goals Introduction to Agile Life Cycles The Agile Manifesto and Agile Principles Agile Life Cycles
More informationSoftware Process. Overview
Software Process Overview What is software process? Examples of process models Unified Process (UP) Agile software development N. Meng, B. Ryder 2 1 Software Process Definition [Pressman] a framework for
More informationAgile Manifesto Principles
Agile Manifesto Principles Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes
More informationBy: Ronny Trefftzs CSCI 5828: Foundations of Software Engineering Spring 2012 Professor: Kenneth Anderson
By: Ronny Trefftzs CSCI 5828: Foundations of Software Engineering Spring 2012 Professor: Kenneth Anderson WATERFALL? XP? SCRUM? While there is really no standard solution, the following presentation will
More informationAgile Architecture how much is enough?
Agile Architecture how much is enough? EAC2007 Eoin Woods UBS Investment Bank www.ibb.ubs.com/futuresandoptions www.ubs.com/careers www.eoinwoods.info Introductions I m a stream technical architect for
More informationAgile Test Plan How to Construct an Agile Test Plan
Agile Test Plan How to Construct an Agile Test Plan XBOSoft White Paper How to Construct an Agile Test Plan www.xbosoft.com 2 Agile is changing not only the way we develop software but the way we work
More informationIntroduction. Failure. Why Projects Fail. Agile in an Hour
Agile in an Hour Joe Bergin & Fred Grossman Seidenberg School Computer Science and Information Systems Pace University Introduction Agile Software Development is a high discipline and very iterative development
More informationFlexibility on what is delivered High
Flexibility on what is delivered level 1: Stakeholders are very comfortable with the fact that limited flexibility on budget and time may be necessary in order to deliver the full scope on quality, and
More informationCOACHING I 5. BUSINESS MANAGEMENT COACHING TIPS & STRATEGIES The Influence of the Human Resource Department
COACHING I 5. BUSINESS MANAGEMENT COACHING TIPS & STRATEGIES 5.1. The Influence of the Human Resource Department "There is a great man who makes every man feel small. But the real great man is the man
More informationLeadership Agility Profile: 360 Assessment. Prepared for J. SAMPLE DATE
Prepared for J. SAMPLE About this Report Introduction LEADERSHIP that special quality that enables leaders to achieve extraordinary success. In today's uncertain world the need for leadership is at an
More informationSystems Thinking Navigating Through Complexity. How to Implement Internal Mediation Services. May 13, Karen Delaronde
Systems Thinking Navigating Through Complexity How to Implement Internal Mediation Services May 13, 2008 Karen Delaronde Introduction: I work in Staff Development and Organizational Change with Regional
More informationChapter 3 Agile Software Development. Part 1b
Chapter 3 Agile Software Development Part 1b 1 Testing in XP Testing is central to XP and XP has developed an approach where the program is tested after every change has been made. XP testing features:
More informationSoftware Engineering Chap.3 - Agile Software Development
Software Engineering Chap.3 - Agile Software Development Simão Melo de Sousa RELEASE (UBI), LIACC (Porto), CCTC (Minho) Computer Science Department University of Beira Interior, Portugal Eng.Info./TSI,
More informationTOGAF usage in outsourcing of software development
Acta Informatica Pragensia 2(2), 2013, 68 76, ISSN 1805-4951 Section: Online: aip.vse.cz Peer-reviewed papers TOGAF usage in outsourcing of software development Aziz Ahmad Rais 1, Rudolf Pecinovsky 1 1
More informationService Validation, Incremental and Iterative Development
Colorado Software Summit: October 19 24, 2008 Service Validation, Incremental and Iterative Development David Moskowitz Productivity Solutions, Inc. Slide 1 Agenda Service Reality Check Common language:
More information1. The Case for Agile 2. The Scrum Process 3. Scaling Scrum
1. The Case for Agile 2. The Scrum Process 3. Scaling Scrum Delivering late Delivering over budget Delivering the wrong thing Unstable in production Costly to maintain Smart people trying to do good work
More informationChapter 3 Prescriptive Process Models
Chapter 3 Prescriptive Process Models - Generic process framework (revisited) - Traditional process models - Specialized process models - The unified process Generic Process Framework Communication Involves
More informationSoftware Life Cycle. Main Topics. Introduction
Software Life Cycle Main Topics Study the different life cycle models Study the difference between software maintenance and evolution Study product line engineering as a design methodology 2 Introduction
More informationAgile Enterprise Architecture. Presented by Russell Bryant March 4, 2009
Agile Enterprise Architecture Presented by Russell Bryant March 4, 2009 The Rise of Agile Architecture Traditional Enterprise Architecture maturing Demands of IT and business require agility, adaptability
More informationANA Adopted Values and Associated Behaviors. May 27, 2015
Background ANA Adopted Values and Associated Behaviors May 27, 2015 - Values work launched at the February Directors Retreat. - A Values work group (Directors) determined and recommended a draft of 5 ANA
More informationSoftware Development Methodologies. CSC 440: Software Engineering Slide #1
Software Development Methodologies CSC 440: Software Engineering Slide #1 Topics 1. The Waterfall Model 2. Agile Software Development 3. The Unified Process 4. Object-Oriented Analysis and Design 5. The
More informationAgile Acquisition. Peter Modigliani 10 Dec 12. Presented to: Mr. Koen Gijsbers. General Manager NATO Communications and Information Agency
Agile Acquisition Peter Modigliani 10 Dec 12 Presented to: Mr. Koen Gijsbers General Manager NATO Communications and Information Agency Approved for Public Release; Distribution Unlimited 12-4964 2012-The
More informationChapter 3. Information Systems Development. McGraw-Hill/Irwin. Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 3 Information Systems Development McGraw-Hill/Irwin Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Objectives 3-2 Describe the motivation for a system development process
More informationIntroduction. Failure. Why Projects Fail. Agile in an Hour
Agile in an Hour Joe Bergin & Fred Grossman Seidenberg School Computer Science and Information Systems Pace University Introduction Agile Software Development is a high discipline and very iterative development
More informationAgile versus? Architecture
Agile versus? Architecture This presentation is about Software Architecture and its relationship to Agile practices. There is often a kind of tension between Agile Concepts and Architecture concepts. Why
More informationAgile at Mid-Scale. Al Shalloway. Introducing FLow for Enterprise Transformations (FLEX)
Agile at Mid-Scale Introducing FLow for Enterprise Transformations (FLEX) Al Shalloway CEO, Founder alshall@netobjectives.com @AlShalloway Co-founder of Lean-Systems Society Co-founder Lean-Kanban University
More informationIntroduction to Software Engineering
UNIT I SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, objects oriented) -system engineering computer
More information7 TIPS TO HELP YOU ADOPT CONTINUAL SERVICE IMPROVEMENT, BY STUART RANCE 1
7 TIPS TO HELP YOU ADOPT CONTINUAL SERVICE IMPROVEMENT, BY STUART RANCE 1 CONTINUAL SERVICE IMPROVEMENT Continual Service Improvement (CSI) is one of the most important concepts in ITIL, but very few IT
More information7. Project Management
Subject/Topic/Focus: 7. Project Management Management of Systems Engineering Processes Summary: Project management Systems engineering Maturity model and process improvement Literature: Ian Sommerville:
More informationBMC MainView: Holistic Systems Management Made Possible
Holistic Systems Management Made Possible Volatility Becomes the Norm Mobile applications and digital business practices have effectively rewritten the way you operate. In addition to driving up transaction
More informationAgile Development Processes. CSCE Lecture 3-08/31/2017
Agile Development Processes CSCE 740 - Lecture 3-08/31/2017 Common Practice: Code & Fix Sit down, write out the code, and fix problems as they occur. No formal structure to development. What is wrong with
More informationIntroduction to Extreme Programming
Introduction to Extreme Programming Brian Button bbutton@objectmentor.com, Inc Overview Motivation Business Case Description Case Studies References 1-800-338-6716 2 My Typical Client Manager doesn t trust
More informationLecture 2: Project Management, Part 1: Requirements, WBS, Scheduling, and Risk Management. Prof. Shervin Shirmohammadi SITE, University of Ottawa
Lecture 2: Project Management, Part 1: Requirements, WBS, Scheduling, and Risk Management Prof. Shervin Shirmohammadi SITE, University of Ottawa Prof. Shervin Shirmohammadi ELG 4912 2-1 Goal of Project
More informationWelcome to this IBM Rational podcast, Do you. Have What it Takes to be a Successful Business Analyst? I'm
[ MUSIC ] Welcome to this IBM Rational podcast, Do you Have What it Takes to be a Successful Business Analyst? I'm Kimberly Gist with IBM. The role of business analyst changes day by day, and the opportunities
More informationSAP BUSINESS GROUP AGILE FOR SAP SOLUTIONS
SAP BUSINESS GROUP AGILE FOR SAP SOLUTIONS AGILE AND SAP PROJECTS: FINDING THE FIT In a constantly changing business environment, enterprise systems and agile approaches are powerful allies. Enterprise
More informationHolding Accountability Conversations
Holding Accountability Conversations 5 Scripts And Guides To Help You Through The Process PRACTICAL TOOLS Holding Accountability Conversations / / / / / / / / / / / / / / / / / / / / / / / / / / / / /
More informationOmnichannel Inventory Optimization: Where Are My Products?
Going Glocal Executive Summary 1 retail consulting and industry thought leadership Omnichannel Inventory Optimization: Where Are My Products? Where Are My Products? 2 Macy s best customers are those who
More informationRisk Management in BPA / BPI Projects
Abstract Risk Management in BPA / BPI Projects Chandra Sekhar Ramaraju and Venugopal Juturu Before embarking on the business process assessment and improvement (BPA & BPI) projects that might lead to multiple
More informationAgile Essentials Track: Business Services
Agile Essentials Track: Business Services Presenter: Mark Thomas Synopsis Are you a victim of building the wrong solutions slowly? If so, you re not alone, and considering an Agile approach may be the
More informationBI Expert Panel. Planning Business Intelligence Solutions Avoiding Common Challenges Applying Best Practices
BI Expert Panel Planning Business Intelligence Solutions Avoiding Common Challenges Applying Best Practices SolidQ Mentors: Rushabh Mehta Mark Tabladillo Paul Turley Erik Veerman Objectives Facilitate
More informationSections. ! Introduction. ! Development Activities. ! Dealing with Technical Debt. ! Bonus: How to become an Agile Architect
Me Sections! Introduction! Development Activities! Dealing with Technical Debt! Bonus: How to become an Agile Architect Agile! Lean! Value Stream! Discipline! Embrace Change Architecture! Everything that
More informationPrimary Care Home: population health-based workforce redesign
NAPC National Association of Primary Care Primary Care Home: population health-based workforce redesign A brief guide #primarycarehome 02 PRIMARY CARE HOME Contents Foreword 03 Introduction 04 Three key
More informationExecutive Justification for Adopting Model Driven Architecture (MDA)
Executive Justification for Adopting Model Driven Architecture (MDA) Stanley J. Sewall Away from the Hype...MDA gives companies a viable alternative to application development instead of corporate stagnation
More informationTHE FIVE BUILDING BLOCKS OF AN EXCEPTIONAL WEB EXPERIENCE. Your guide to winning the personalization race.
THE FIVE BUILDING BLOCKS OF AN EXCEPTIONAL WEB EXPERIENCE. Your guide to winning the personalization race. 2018 EXECUTIVE SUMMARY The most important component for brand relevance and long-term customer
More informationBecoming Agile: A Grounded Theory of Agile Transitions in Practice
Becoming Agile: A Grounded Theory of Agile Transitions in Practice Agile software development "Agile" means being able to adapt to changing requirements including requirements that are understood only
More informationAnnual STATE MARKETING REPORT
st Annual STATE OF AGILE MARKETING REPORT THE EVOLUTION OF THE AGILE MARKETING REVOL UTION Wanna hear something cool? You re reading the 1st Annual State of Agile Marketing Report, and that title isn t
More informationAgile Planning. Petri Heiramo. Agile Coach, CST
Agile Planning Petri Heiramo Agile Coach, CST An Agile Plan Is Not a Rough Guide Some teams think that, if they did not finish all stories, that was OK, we are agile Postponing stories was seen as an acceptable
More informationFuture Proofing HR Survey Series Research Insights
Future Proofing HR Survey Series Research Insights Greg Selke Business Transformation Executive SAP November 2017 San Francisco INTERNAL Introduction and Session Goals 10 Topics x 5 Ideas = 50 Takeaways
More informationMarrying AM and EA in large organizations
Marrying AM and EA in large organizations Bartek Kiepuszewski, PhD Cutter Consortium Agile Project Management Team: Jim Highsmith, Scott Ambler, Kent Beck, Alistair Cockburn, Mike Cohn, Ken Collier, Ron
More informationIntroduction to Agile Change Management
Introduction to Agile Change Management Author Melanie Franklin Director Agile Change Management Limited Introduction Agile change management is a term that is picking up momentum around the world. In
More informationAchieving Balance: The New Pivotal Points of Software Development
White Paper Software Delivery & Testing Achieving Balance: The New Pivotal Points of Software Development A rational model of software is to design it quickly; the economic pressure to improvise presents
More informationBoard and Senior Management Reporting. Eric Holmquist Managing Principal Enterprise Risk Management
Board and Senior Management Reporting Eric Holmquist Managing Principal Enterprise Risk Management April 28, 2018 CONTENTS 01 02 03 04 05 OVERVIEW AND COMMON CHALLENGES IT S ALL ABOUT ROLES LESS IS MORE,
More informationBUSINESS PLAN Preparing for the Future
Delivering great services locally BUSINESS PLAN 2018-19 Preparing for the Future DRAFT: 21 February 2018 1 FOREWORD It is a great pleasure and privilege to present Publica s first Business Plan in which
More informationBest Practices for Creating an Open Source Policy. Why Do You Need an Open Source Software Policy? The Process of Writing an Open Source Policy
Current Articles RSS Feed 866-399-6736 Best Practices for Creating an Open Source Policy Posted by Stormy Peters on Wed, Feb 25, 2009 Most companies using open source software know they need an open source
More informationInformation Systems Development
Information Systems Development Based on Chapter 3 of Whitten, Bentley, and Dittman: Systems Analysis and Design for the Global Enterprise (7th Ed). McGraw Hill. 2007 Wei-Tsong Wang 1 IIM, NCKU 3 Objectives
More informationOrganizational Dysfunctions on Testing - Agile Remedies. 2017, Bill Allen / Kieran Murphy. All Rights Reserved.
Organizational Dysfunctions on Testing - Agile Remedies 2017, Bill Allen / Kieran Murphy. All Rights Reserved. #BDD-TDD 1 Introductions: Bill Allen - agile Innovation Labs Bill@agileInnov.com Kieran Murphy
More informationTHE POWER OF ONLINE REVIEWS. Free ebook BACK TO CONTENTS. thrivehive.com
THE POWER OF ONLINE REVIEWS Free ebook 2 CONTENTS 03 Introduction 04 The Power of Online Reviews 08 Where to Get Reviews 09 How to Get More Reviews 11 How to Ask for Reviews 15 Important Review Tips 3
More informationExtreme Programming, an agile software development process
Extreme Programming, an agile software development process Paul Jackson School of Informatics University of Edinburgh Recall: Waterfall and Spiral Models 1.Determine objectives Cumulative cost Progress
More informationSaving Troubled Projects
Saving Troubled Projects 2013 Instructor and Developer Mark Waldof Mark Waldof Consulting Retired Lockheed Martin University of Minnesota Instructor CCE Business Improvements Consultant Project Management
More informationAccelerating Your DevOps Journey
06 October 2016 Accelerating Your DevOps Journey Peter Eeles Executive IT Architect DevOps Global Tiger Team, IBM Hybrid Cloud peter.eeles@uk.ibm.com Agenda 1 The Business and IT Context 2 The Relevance
More informationA Comparative Study of Universally Accepted SDLC Models for Software Development
2018 IJSRST Volume 4 Issue 5 Print ISSN: 2395-6011 Online ISSN: 2395-602X Themed Section: Science and Technology A Comparative Study of Universally Accepted SDLC Models for Software Development ABSTRACT
More informationImplementing Test Automation
Implementing Test Automation Myths Truths Steps to Success page 1 plvision.eu Introduction More and more successful software companies are getting to the point where their existing testing strategy stops
More informationSign up to mailing list Join Slack, teaching team is available. All links are on the course website Slides are uploaded there too
Sign up to mailing list Join Slack, teaching team is available All links are on the course website Slides are uploaded there too Week 1 (Oct 16 Oct 20) Introduction lectures Week 2 (Oct 23 Oct 27) Work
More informationIntroduction to Disciplined Agile Delivery
IBM Software Group Introduction to Disciplined Agile Delivery 2010 IBM Corporation Agenda What is Agile Why are organizations moving to Agile and what challenges do they face How IBM is addressing these
More informationThe ABC of Agile Business Change. James Yoxall BCS 17 September, 2013
The ABC of Agile Business Change James Yoxall BCS 17 September, 2013 Introduction Purpose is to explore the concept of Agile Business Change What does it mean? Why might it be a good thing? Where and when
More informationResource Management 2.0 The Next Chapter of Just-in-Time Resourcing
Resource Management 2.0 The Next Chapter of Just-in-Time Resourcing Randy Mysliviec President and CEO Jenna Schofield Senior Consultant 2 2008-2017, Inc. All rights reserved. Just-in-Time Resourcing is
More informationMake Your Business Case
Make Your Business Case How to Use Business Planning for Successful Business Growth George Simmons, Senior Partner Derby Management Consultants www.derbymanagement.com Quick Agenda Ok? A bit about me Stages
More informationKen Auer RoleModel Software, Inc. Copyright , RoleModel Software, Inc.
Ken Auer RoleModel Software, Inc. ken.auer@rolemodelsoftware.com http://rolemodelsoftware.com Copyright 2003-04, RoleModel Software, Inc. Documentation is not Understanding (tacit) One Study of Typical
More informationLean Software Development
The PROJECT PERFECT White Paper Collection Lean Software Development Dasari. Ravi Kumar Introduction They may be clearly identified, but are poorly acknowledged. The problems of the software development
More informationInternal controls over financial reporting
Internal controls over financial reporting Outlining a program that meets stakeholder expectations kpmg.ca After showing why a company s internal controls over financial reporting (ICOFR) program may be
More informationThe Faster Road to Innovation Why Workopolis Went Agile
The Faster Road to Innovation Why Workopolis Went Agile What I m Covering Today Why did we transition to Agile? What we wanted to Achieve Highlights of How We Did It What we Achieved What we Learned Technology
More informationAn overview of The Open Group's Enterprise Architecture and Evolution of IT4IT
An overview of The Open Group's Enterprise Architecture and Evolution of IT4IT Krishnamoorthy Marimuthu 1, Dr. V.Prasanna Venkatesan 2 1 BI Architect, Tata Consultancy Services, Chennai, India 2 Head-Dept.
More informationBuilding a Platform for Innovation: Architecture and Agile as Key Enablers
Building a Platform for Innovation: Architecture and Agile as Key Enablers Peter Eeles FSS Industry Lead, IBM Rational Worldwide Tiger Team peter.eeles@uk.ibm.com 1191A 2013 IBM Corporation Please note
More informationCrossing the Chasm Helping Testers Make an Agile Transition Lisa Crispin With material from Janet Gregory
Crossing the Chasm Helping Testers Make an Agile Transition Lisa Crispin With material from Janet Gregory 1 Agenda Introduction The Chasm Support for the Transition Transition of Traditional Activities
More informationDecision Analysis Making the Big Decisions
Decision Analysis Making the Big Decisions Endeavor Management 2700 Post Oak Blvd. P + 713.877.8130 Suite 1400 F + 713.877.1823 Houston, Texas 77056 www.endeavormgmt.com Overview You probably face a lot
More informationMedical Device Product Development for Startups
Medical Device Product Development for Startups - The Bitter Pill AZBIO WEEK / CEI 8/19/2016 ERIC MILLER PADT, INC. Agenda Introduction Medical Device Development Fundamentals The Design Process Manufacturing
More informationOrganizational Matters
Organizational Matters Christoph Matthies christoph.matthies@hpi.de Software Engineering II WS 2018/19 Prof. Plattner, Dr. Uflacker Enterprise Platform and Integration Concepts group Communication If you
More informationCommunicate for Success
FEDERER PERFORMANCE MANAGEMENT GROUP, LLC TRANSFORMING VISIONS INTO RESULTS WHITE PAPER Communicate for Success Introduction You might be surprised at how many issues in the workplace and in general could
More informationPart 1. Software engineering Facts. CSC 4181 Compiler Construction Software Engineering Lectures. What is software engineering? What is software?
Software engineering Facts CSC 4181 Compiler Construction Software Engineering Lectures Part 1 Fact: The economies of ALL developed nations are dependent on software. Fact: More and more systems are software
More informationSoftware Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000)
Software Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000) armahmood786@yahoo.com alphasecure@gmail.com alphapeeler.sf.net/pubkeys/pkey.htm http://alphapeeler.sourceforge.net
More information10x. Your Thinking. and Build a Culture of Innovation 1/9. 10x Your Thinking. and Build a Culture of Innovation
10x Your Thinking 1/9 Is your company a hotbed of invention? Do your employees have more good ideas than they know what to do with? What was the last calculated risk your team embraced, and what did you
More informationDebunking Agile Myths
Debunking Agile Myths Rick Clare CBAP, PMP, CSM, MSPM Solutions Partner 634 Alpha Drive Pittsburgh, PA 15238 (888) 762-3683 Fax (412) 963-8618 Presentation Purpose Purpose This presentation will discuss
More informationAgile Project Planning and Management
Agile Project Planning and Management Carl Erickson Atomic Object LLC July 2007 Atomic Object 1 Plan is a Noun Success requires a plan heavyweight upfront document created at point of maximum ignorance
More informationAgile Software Development. Agile Software Development Basics. Principles of the Agile Alliance. Agile Manifesto. Agenda. Agile software development
Agile Software Development T-110.6130 Systems Engineering in Data Communications Software P, Aalto University Agile software development Structured and disciplined, fast-paced Iterative and Incremental
More informationworking hours full time is 35 hours a week. You ll agree your working pattern with your manager.
resourcing manager reporting to head of learning, talent and resourcing direct reports resourcing partners working hours full time is 35 hours a week. You ll agree your working pattern with your manager.
More informationAssessment: was ist ein High Performance Team
Assessment: was ist ein High Performance Team Truly Emergent Architecture Comfortable with de- composition on- the- fly; no BDUF! Drive Sprint #0 s as appropriate Backlogs contain learning activity Research
More informationThe Answer Company White Paper
The Answer Company White Paper Cloud ERP is ready but you might not be. It's all about the Risk-Adjustment Cost-Benefit. THIS IS A PREVIEW Prepared by: 101: Cloud-based ERP What s in this Section: Market
More information