Aligning Architecture work with Agile Teams
|
|
- Anna Alexander
- 6 years ago
- Views:
Transcription
1 Aligning Architecture work with Agile Teams Eoin Woods Endava 15 th July Agile software development is a very widely practiced software development approach and nowadays there is also broad recognition of the role of the software architect in the process of making the key design decisions for a project. However in my experience there are often difficulties when agile development teams and software architects work together. This can be caused by differing priorities, different language and sometimes different development philosophy. The result can be development teams dismissing software architecture as big design up front and in turn, architects doing a poor job at producing architectural work that is useful for agile teams. Difficulties when architects try to work with agile teams can be a real problem for organisations, causing them to miss the benefits to be gained when this relationship works well. Agile teams often do a tremendous job at delivering useful software in a timely manner, but can encounter problems coping with factors such as security, system monitoring or systems integration, none of which tend to feature in a product owner s priorities. However it is exactly these areas that software architects usually address. In an earlier Pragmatic Architect column [1], Eltjo Poort explained how the Risk and Cost Driven Architecture approach can help architects to align their work with agile teams. In this column, we will suggest some more general ways in which to achieve this. Agile Software Development The term agile development is applied to a wide variety of specific approaches, some of the best known being Scrum and Extreme Programming (XP). What unifies agile approaches is an unifying philosophy summarised in the wellknown Agile Manifesto [2]. The agile manifesto states that its philosophy values: Working software over comprehensive documentation Customer collaboration over contract negotiation Individuals and interactions over processes and tools Responding to change over following a plan While the manifesto acknowledges that the items at the start of each point do have value, the second item in each point is valued more highly. While it is difficult to disagree with these principles (who honestly prefers completed documentation over working software?), what has been remarkable has been their ability to inspire the strong community that has formed and created the practice of agile development.
2 Software Architecture We have previously defined and characterised the role of the software architect in this column [3] and so let s just summarise it again, as making the design decisions that are risky, costly, hard to change later, or all three. And let us remind ourselves that it tends to include: A focus on design work; Meeting the needs of a wide stakeholder community (well beyond users and acquirers); Concerning ourselves with the system wide concerns (which are often non-functional); Balancing competing concerns to find acceptable solutions to the design problems; and Providing leadership where required to ensure that the architecture of the system is well understood so that it can be implemented successfully. Working Together Having worked as an architect with many agile teams over the last 10 years, I realised that there were some architecture practices that really helped us to cooperate and get the architecture work done in a way that supported agile development. These practices were inspired by the principles of the agile manifesto and address different aspects of it, as shown in Figure 1. Allow for Change Deliver incrementally Capture decisions and rationale Capture clear architecture principles Define components clearly People Over Processes & Tools Share information using simple tools Have customers for every deliverable Collaboration Over Contracts Work in Teams Don t (Just) Deliver Documents Focus design on stakeholder concerns Focus on architectural concerns Software Over Documents Create good enough architectural artefacts Define solutions for cross-cutting concerns Deliver something that runs Figure 1 - Practices for Agile Architectural Working Let us briefly explore each of these practices, to understand how they fit together. Allow for Change The Agile Manifesto urges us to embrace change rather than rely on following a plan. The following practices help to make architecture work more amenable to change.
3 Deliver Incrementally when working on a significant piece of design work, there s a natural tendency to want perfection before sharing it. However our agile principles encourage us to do the opposite and to make a minimum number of key decisions initially and then to make a flow of decisions as needed to meet the system s delivery goals. This allows the architecture work to respond to changing priorities and increased knowledge. In practice I have found that initially you need just enough architecture work to define the key system structures and you can then refine each aspect of the architecture as it is needed, as the project develops. In his recent article in this column, Eltjo Poort explained how to use risk and cost to drive this flow of decisions [1]. Capture Clear Architecture Principles agile teams need to empower team members to make good design decisions themselves. A good way to support this is to define a clear set of architecture principles that help people understand why the architectural structures exist and the most important characteristics of the architecture. Principles provide team members with a mental framework to use when they extend and change the architecture. Capture Decisions and Rationale on a related point, help the team to understand why certain decisions were made by capturing important design decisions and rationale [4] and keep explaining them verbally so that they become part of the project s aural tradition. Define Components Clearly - as the system evolves, new components will be introduced, existing ones changed and component interactions altered. To allow coherent evolution the components need to be well understood, meaning that each one needs to have a good name, a clear set of responsibilities, a clear set of well-defined interfaces through which it communicates and a clear set of dependencies that it requires. Without this knowledge, it is very difficult to evolve the system structure coherently. People over Process & Tools The Agile Manifesto reminds us that people create the software, not the processes and tools. When considering architectural work there are two key practices that reflect this. Share Information Using Simple Tools a key part of a software architect s job is to communicate the architecture to relevant stakeholders, be they infrastructure designers, end-users, compliance officers or the development team. I have found that effective communication normally requires the use of simple approaches that people are already familiar with. While sophisticated modelling tools can be valuable, particularly for the architect themselves, other stakeholder communication is often best achieved through familiar mechanisms such as wikis, presentations and short, accessible documents. Have Customers for Every Deliverable it s easy to write a document that seems to be important at the time, and then only later start considering who should read it. This often results in a document that no one wants! To focus the architecture work on high value areas, all deliverables need
4 to be created with a definite purpose and audience in mind, so maximising the chances that they will be useful. Software over Documents Agile software development emphasises the value of working software over documentation describing what might be. There are several practices for architecture work inspired by this principle. Create Good Enough Architectural Artefacts the architectural models and documents for a system can be quite significant pieces of work in themselves and there s an understandable pride in creating a comprehensive and polished result. However these deliverables aren t part of the final system and so they should be fit-for-purpose rather than polished to the point of perfection. This isn t an excuse for sloppy work, but rather a guide for when it s time to move on to the next task. Deliver Something that Runs everything we do needs to be validated and tested, whether it s production code or design principles and ideas. In the case of architectural design, this means that rather than documents full of theoretical ideas, it s important to deliver something that validates the architectural thinking. In many cases while it s not production software, the best way to do this is to create examples and prototype implementations that validate the key ideas, prove that they really work and them to be understood and adopted quickly. Define Solutions for Cross-Cutting Concerns some aspects of a systems design are complicated because they cut across a lot of the system s implementation. These design decisions normally address qualities like security or scalability, and should be a major focus of the architecture work. Delivering clear, proven solutions for each of the system s important quality properties is tremendously valuable because it allows the team to focus on other aspects of the design and achieve the required qualities without a lot of research and rework. Collaboration over Contracts The final aspect of the Agile Manifesto urges us to collaborate with each other rather than to rely on formal boundaries and agreements. Such collaboration is key to effective architecture work and is supported by the following practices. Work in Teams Don t (Just) Deliver Documents a common complaint about architects is that they are a long way from the people suffering the results of their decisions. To avoid this, architects need to work collaboratively with development teams, working directly with and in teams wherever possible. This allows a two-way flow of ideas, helping the architect to understand the real problems they need to solve and helping the team to understand what the architecture really means. Focus Design Work on Stakeholder Concerns another aspect of collaboration is making sure that architectural design work is addressing the most important aspects of the system. It s easy to create architectures that are scalable or flexible or efficient without considering what the system s stakeholders really need. Making sure that the design work
5 being undertaken aligns with stakeholder needs helps to focus it in the right places. Focus on Architectural Concerns when working with a development team, it s important that the software architect is engaged in a way that the team find valuable. I ve found that the best way to achieve this is to focus on the cross-cutting concerns in the system, such as common design patterns, how the system will be deployed and how the critical qualities (such as security or availability) will be achieved. You may remember that a metaphor we used in the last column to identify architecture work was architecting in the gaps. Taking ownership of these aspects of a system is a useful service that the architect can provide to the team. Summary Software architects and agile development teams have a mixed history of working together harmoniously, which is unfortunate but in my experience, rectifiable. With a little flexibility and goodwill on both sides, it is quite possible for the software architect to channel their efforts through a set of practices that align with the underlying principles of agile development. These practices combine to allow the architect to work constructively with agile teams and make a real contribution to the success of the project. References [1]. Eltjo R. Poort, "Driving Agile Architecting with Cost and Risk", IEEE Software, vol.31, no. 5, pp , Sept.-Oct. 2014, doi: /ms [2]. Manifesto for Agile Software Development, retrieved 15 th July [3]. Eoin Woods, "Return of the Pragmatic Architect", IEEE Software, vol.31, no. 3, pp , May-June 2014, doi: /ms [4]. Philippe Kruchten, Rafael Capilla, Juan Carlos Dueñas, "The Decision View's Role in Software Architecture Practice", IEEE Software, vol.26, no. 2, pp , March/April 2009, doi: /ms [5]. Eoin Woods, "Architecting in the Gaps: A Metaphor for Architecture Work", IEEE Software, vol.32, no. 4, pp , July-Aug. 2015, doi: /ms
Agile Software Architecture how much is enough?
Agile Software Architecture how much is enough? JAX London April 2011 Eoin Woods www.eoinwoods.info About Me Software architect at UBS Investment Bank responsible for synthetic equity platform in Prime
More informationAgile Software Architecture how much is enough?
Agile Software Architecture how much is enough? Eoin Woods www.eoinwoods.info 1 About Me Software architect at BlackRock the world s largest asset manager (having acquired BGI) head of the Application
More informationSMART AUTOMATION: ALLOWING THE MODERN ENTERPRISE TO SURVIVE AND THRIVE
/automation SMART AUTOMATION: ALLOWING THE MODERN ENTERPRISE TO SURVIVE AND THRIVE EOIN WOODS CTO ENDAVA CONTENTS 1 INTRODUCTION 04 2 WHY SMART AUTOMATION? 05 3 AUTOMATION THE UNFULFILLED PROMISE 07 4
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 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 informationSoftware Engineering Part 2
CS 0901341 Software Engineering Part 2 In this part, we look at 2.1 Software Process 2.2 Software Process Models 2.3 Tools and Techniques for Processing Modelling As we saw in the previous part, the concept
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 informationAgile leadership for change initiatives
Agile leadership for change initiatives Author Melanie Franklin Director Agile Change Management Limited Contents Introduction 3 Agile principles 3 Introduction to Agile techniques 6 Working in sprints
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 informationAgile Software Development:
Agile Software Development: 1.Agile methods 2.Plan-driven and agile development 3.Extreme programming (XP) 4.Agile project management 5.Pair Programming 6.Scrum 7.Scaling agile methods Rapid software development:
More informationImpact of Agile on Change Management
Impact of Agile on Change Management Author Melanie Franklin Director Agile Change Management Limited Introduction Agile approaches and techniques are having significant impact on the volume, frequency
More informationAgile. How would you implement agile methodologies and tools for web projects? What do you see as the benefits and challenges to doing this?
Agile How would you implement agile methodologies and tools for web projects? What do you see as the benefits and challenges to doing this? What is Agile? The term agile (sometimes written Agile) was popularised
More informationImproving Employee Performance: How Technology Can Help
Improving Employee Performance: How Technology Can Help Index Introduction What is getting in the way of performance management that really works? What to look How technology can help Picking the best
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 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 informationThe role of the service-oriented architect
Copyright Rational Software 2003 http://www.therationaledge.com/may_03/f_bloomberg.jsp The role of the service-oriented architect by Jason Bloomberg Senior Analyst ZapThink LLC Web services have moved
More informationFIT2101 Software Engineering Process and Management
FIT2101 Software Engineering Process and Management Agile and Software Process Models Topics Covered Features of Agile What Agile Isn t Agile Process Models Software Process Models In 2001 leaders of lightweight
More informationAddressing the Challenges of Medical Content Authoring
Addressing the Challenges of Medical Content Authoring Five Recommendations for Combining English Content Development with Localization A Publication of Lionbridge Life Sciences INTRODUCTION RECOMMENDATION
More informationTenStep Project Management Process Summary
TenStep Project Management Process Summary Project management refers to the definition and planning, and then the subsequent management, control, and conclusion of a project. It is important to recognize
More informationChapter 2. The Nature of Project Work
Chapter 2 The Nature of Project Work This chapter provides a brief overview of project work and its distinctive features. It looks at the important role of teamwork and at the relationship between time,
More informationHigh Performance Coaching. Guide. theperformanceroom.co.uk
High Performance Coaching Guide High Performance Coaching your essential guide! Coaching a dispensable ingredient in a high performance world? Imagine this an international football team with no coach
More informationAn Overview of Software Process
An Overview of Software Process Objectives To introduce the general phases of the software development life cycle (SDLC) To describe various generic software process models and discuss their pros and cons
More informationImproving Employee Performance How Technology Can Help
Improving Employee Performance How Technology Can Help Introduction It would be easy to conclude from recent articles that employee performance management is a fundamentally flawed process and should disappear
More informationAgile delivery. Delight your organisation & increase job satisfaction
Agile delivery Delight your organisation & increase job satisfaction Overview Why should you be interested? What Agile is NOT... Typical project issues What is Agile? Basic concepts Agile framework outline
More informationDigitalizing the customer journey
Why RAD is Right for Mobile and Web Front-End Development Digitalizing the customer journey requires front-end touchpoints that are easy to use, attractive, and full featured. The explosion of mobility
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 informationDELIVER SOLUTION. Predictive versus Adaptive Approaches. Predictive Approach
DELIVER SOLUTION All the work done so far is about understanding the current state, finding possible solutions and finally selecting the best-suited solution. The next step is to develop the solution.
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 informationArchitectural Practices and Challenges in Using Agile Software Development Approaches
Architectural Practices and Challenges in Using Agile Software Development Approaches M. Ali Babar 1 Today s Talk Agility and architecture: A match made in Heaven broken on Earth? Talk summarizes The design,
More informationImpact of Agile on Change Management
Impact of Agile on Change Management Author Melanie Franklin Director Agile Change Management Limited Introduction Agile approaches and techniques are having significant impact on the volume, frequency
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 informationWHITE PAPER. Six Simple Steps to Improve Service Quality and Reduce Costs
WHITE PAPER Six Simple Steps to Improve Service Quality and Reduce Costs INTRODUCTION Do you have challenges with maintaining your SLA commitment? Does your customer support department get more complex
More informationAgile SCRUM in Systems Engineering A Practical Application
Agile SCRUM in Systems Engineering A Practical Application Author Paul Wheway, Principal Systems Engineer, Thales UK. Paul.wheway@uk.thalesgroup.com Categorisation Accessibility Practitioner Application
More informationAgility and Architecture: Why and How They can Coexist?
Agility and Architecture: Why and How They can Coexist? M. Ali Babar IT University of Copenhagen, Denmark Keynote, Third Turkish Software Architecture Conference Ankara, Turkey, November 4, 2010 Background
More informationReducing Business Risk
July 2005 Reducing Business Risk Through Agile Development Fred Tingey Head of Risk Systems BNP Paribas Introduction Context What is Agile Programming? Traditional vs Agile approach A New Way to do Things
More information6. Models of the Design Process
6. Models of the Design Process 17 September 2008 Bob Glushko Plan for ISSD Lecture #6 Meta-Methodology: Sequential, Iterative, Work Product, and Portfolio Approaches "User-Centered Design at IBM Consulting"
More informationTickITplus Implementation Note
Title Understanding Base Practices Requirement Sizing Date April 2015 Reference TIN015-1504 Originator Dave Wynn Version v1r0 Key Terms Base Practices, Implementation, Requirements, Sizing, Estimating,
More informationStrike the right balance with Disciplined Agile Delivery (DAD)! October 6, 2016 Kiron D. Bondale, PMP, PMI-RMP, CDAP, CDAI
Strike the right balance with Disciplined Agile Delivery (DAD)! October 6, 2016 Kiron D. Bondale, PMP, PMI-RMP, CDAP, CDAI Learning Objectives 1. Learn the economic rationale for agile project delivery
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationAgile Mumbo Jumbo. Helping ICEAA and Cost Estimators Be Agile. ICEAA Professional Development & Training Workshop
Agile Mumbo Jumbo Helping ICEAA and Cost Estimators Be Agile ICEAA Professional Development & Training Workshop June 2017 Abstract You don t put any stock in this Agile mumbo jumbo do you? Well, Agile
More informationHOW CAN YOU ENSURE SUCCESSFUL BUSINESS TRANSFORMATION? By Suzanne Costella
HOW CAN YOU ENSURE SUCCESSFUL BUSINESS TRANSFORMATION? T H E I M P O R T A N C E O F B R I D G I N G T H E S T R A T E G Y T O D E L I V E R Y G A P By Suzanne Costella L A U D A L E T H O U G H T S HOW
More informationScaling Up & Scaling Down
Iterative Project Management: A Scalable Approach to Managing Software Development Projects 1 Iterative software development methodologies offer many benefitsfor modern software development projects but
More informationTear It Down to Build it up
Tear It Down to Build it up Case study in progress Arjay Hinek Red Hat Global Agile Coach April 5, 2018 I need your help INSERT DESIGNATOR, IF NEEDED I need your help INSERT DESIGNATOR, IF NEEDED I need
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 informationPutting our behaviours into practice
Putting our behaviours into practice Introduction Our behaviours are an important part of One Housing. They are designed to shape how we work - they are the ideas and approaches that form the foundation
More informationSOFTWARE DEVELOPMENT. Process, Models, Methods, Diagrams Software Development Life Cyles. Part - V
SOFTWARE DEVELOPMENT Process, Models, Methods, Diagrams Software Development Life Cyles Part - V Extreme Programming (XP) was conceived and developed by Kent Beck to address the specific needs of software
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 informationCTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal
CTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal There are 30 questions on this exam. Each question is worth
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 informationFoundations of Software Engineering. Process: Agile Practices Michael Hilton
Foundations of Software Engineering Process: Agile Practices Michael Hilton 1 Learning goals Define agile as both a set of iterative process practices and a business approach for aligning customer needs
More informationSociety Time for Change
Well-Being, W ell-being ell-b, Good od Work Work & Society Time for Change 0161 232 4910 www.robertsoncooper.com www.carycooperblog.com The Business ess Well-Being Well Well-Being Being Network Annual
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 informationChapter 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 informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More information4 Steps To Scaling Agile Across The Enterprise. The Guide To Agile At Scale
4 Steps To Scaling Agile Across The Enterprise The Guide To Agile At Scale Portfolio for Jira is a powerful Jira Software add-on for large organizations that want to scale agile practices, linking agile
More informationSecrets of Successful Modernization
White Paper Secrets of Successful Modernization www.looksoftware.com blog.looksoftware.com info@looksoftware.com White Paper Secrets to Successful Modernization Page 1 Contents IBM i the ultimate application
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 4 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More information3. Comparison of Above Described SDLC Models
123 3. Comparison of Above Described SDLC Models Waterfall Model is little hard to manage due to the rigidity of the model as each phase has specific deliverables and a review process. It works well for
More informationdeveloper.* The Independent Magazine for Software Professionals Automating Software Development Processes by Tim Kitchens
developer.* The Independent Magazine for Software Professionals Automating Software Development Processes by Tim Kitchens Automating repetitive procedures can provide real value to software development
More informationXpertHR Podcast. Original XpertHR podcast: 22 September 2017
XpertHR Podcast Original XpertHR podcast: 22 September 2017 Hi and welcome to this week s XpertHR podcast with me, Ellie Gelder. Now TUPE, possibly not a term that inspires enthusiasm amongst a lot of
More informationArchitecture Planning Adding value to projects with Enterprise Architecture. Whitepaper. September By John Mayall
Adding value to projects with Enterprise Architecture Whitepaper September 2007 By John Mayall W O R L D C L A S S A R C H I T E C T U R E Architecture Planning Introduction We are often asked what an
More informationV Model material adapted from Steve Easterbrook. Waterfall Model material adapted from Steve Easterbrook. Lifecycle of Software Projects
Lifecycle of Software Projects ECE450 Software Engineering II Lifecycle models are useful to compare project management strategies in abstract terms Birds-eye view strategy Detect strengths and weaknesses...
More informationRUP and XP Part II: Valuing Differences
RUP and XP Part II: Valuing Differences by Gary Pollice Evangelist, The Rational Unified Process Rational Software In the last issue of The Rational Edge, we looked at the common ground between the Rational
More informationHOW YOUR CAREER BACKGROUND CAN HELP YOU BECOME A BUSINESS ANALYST
By Laura Brandenburg Lesson Objective: After completing this lesson, you ll be able to identify strengths from your career background that will directly support your transition into business analysis.
More informationIOT SOLUTION DEVELOPMENT. Best Practices
IOT SOLUTION DEVELOPMENT Best Practices IoT Solution Development Best Practices The market for IoT applications continues to experience explosive growth. Its expansion is driven by falling hardware and
More informationToolkit. The Core Characteristics of a Great Place to Work Supporting Framework and Tools. Author: Duncan Brodie
Toolkit The Core Characteristics of a Great Place to Work Supporting Framework and Tools Author: Duncan Brodie 01 About this document This framework has been designed based on the results of the literature
More informationThe Agile Leader Participant Name Lara Croft Participant ID HE Date
The Agile Leader Participant Name Participant ID HE655682 Date 9.28.2017 The Agile Leader Redefining Leadership for a Digital World Many leaders today find it challenging to cope with the increasing pace
More informationWhy We Need Architects (and Architecture) on Agile Projects
Why We Need Architects (and Architecture) on Agile Projects Rebecca Wirfs-Brock rebecca@wirfs-brock.com Twitter: @rebeccawb www.wirfs-brock.com 2015 Wirfs-Brock Associates Three Questions??? What is the
More informationSoftware Engineering COMP 201
Software Engineering COMP 201 Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk COMP 201 web-page: http://www.csc.liv.ac.uk/~coopes/comp201 Lecture 2 Software Processes
More informationBe Agile. Scale Up. Stay Lean. Have More Fun.
Be Agile. Scale Up. Stay Lean. Have More Fun. with the Scaled Agile Framework 1 Keeping Pace Our development methods must keep pace with an increasingly complex world driven by software We ve had Moore
More informationAgile Software Development
Agile Software Development Chapter 3 Agile Software Development in the textbook 3.1 Agile methods 3.2 Plan-driven and agile development 3.3 Extreme programming (XP) - A well known agile method 3.4 Agile
More informationChapter 2 Objectives. Pfleeger and Atlee, Software Engineering: Theory and Practice (edited by B. Cheng) Chapter 2.
Chapter 2 Objectives What we mean by a process Software development products, processes, and resources Several models of the software development process Tools and techniques for process modeling 2.1 The
More informationThe Quality Profession Challenge and ISO 9001:2015
The Quality Profession Challenge and ISO 9001:2015 With the changes to ISO9001 imminent, Ruth Mortby from Nuvia Ltd and the Next Generation Network looks at the CQI s competency framework. The framework
More informationStrategic Planning. Visioning. Strategic planning serves a variety of purposes in organisations, including to:
Strategic planning serves a variety of purposes in organisations, including to: Clearly define the purpose of the organisation and to establish realistic goals and objectives consistent with the mission
More informationPassion for People. Power for Projects
Passion for People Power for Projects AYXANO we safeguard the success of projects and organizations Based on 25+ years of experience we know how to combine processes, methods and tools to build an operative
More information2. True or false: In Scrum all the requirements for the project are known prior to the start of development.
CTC-ITC 310 Program Management California State University Dominguez Hills Fall 2018 Instructor: Howard Rosenthal Assignment 5 A Deeper Look At Agile Methodologies Answer Sheet Each question is worth 10
More informationChapter 3 Software Process Model
Usman Akram COMSATS Institute of information Technology lahore musmanakram@ciitlahore.edu.pk March 8, 2015 About software process model Outline 1 About software process model Build and Fix Model Why Models
More informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More information4 challenges to CM that the business case addresses
Building your Business Case for Change Management Agenda: What is a business case? 4 pieces of the definition and how they connect to CM Value for change management 4 challenges to CM that the business
More informationImproving Agile Execution in the Federal Government
Improving Agile Execution in the Federal Government 1 Committed Partner. Creating Results. In December of 2010 the government introduced the 25 Point Implementation Plan to Reform Federal Information Technology
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 informationDefining the right cloud strategy and plan for your organisation. The what, why, where and when OM INTELLIGENCE D ATA CINTELLIGENCE
DATACOM D ATA CINTELLIGENCE OM INTELLIGENCE WHITE W H IPAPER T E PA P E R Issued: October 20th 2013 82 ## ISSUED January 2016 Defining the right cloud strategy and plan for your organisation The what,
More informationResource: Complexity and project risk
Creating value from uncertainty Broadleaf Capital International Pty Ltd ABN 24 054 021 117 www.broadleaf.com.au Resource: Complexity and project risk We assume that large and complex projects will be risky.
More informationOur Approach to the Scaled Agile Framework (SAFe )
ESSENTIAL WHITE PAPERS Our Approach to the Scaled Agile Framework (SAFe ) by Al Shalloway Our Approach to the Scaled Agile Framework (SAFe ) by Al Shalloway A Net Objectives Essential White Paper Net Objectives
More informationEVERYTHING YOU VE HEARD ABOUT AGILE DEVELOPMENT IS WRONG
EVERYTHING YOU VE HEARD ABOUT AGILE DEVELOPMENT IS WRONG Simon O Toole Australian Astronomical Observatory SOFTWARE DEVELOPMENT QUIZ What is the Waterfall model of software development? What are the advantages
More informationEMR GOVERNANCE: BUILDING A BUSINESS CASE IS JUST THE BEGINNING
EMR GOVERNANCE: BUILDING A BUSINESS CASE IS JUST THE BEGINNING Nothing is more important to the likelihood of an EMR implementation s success than good governance. Implementing an electronic medical record
More informationThe Product Manager and the Product Development Process. Martin Cagan Silicon Valley Product Group
The Product Manager and the Product Development Process Martin Cagan Silicon Valley Product Group THE PRODUCT MANAGER AND THE PRODUCT DEVELOPMENT PROCESS Martin Cagan, Silicon Valley Product Group OVERVIEW
More informationGetting Comfortable with being Uncomfortable! Using Agile IA to transform your internal audit function
Getting Comfortable with being Uncomfortable! Using Agile IA to transform your internal audit function Houston IIA 9 th Annual Conference April 9, 2018 * NRG Center Copyright 2018 Deloitte Development
More informationThe Key to Project Success: Reducing Solution Scope
The Key to Project Success: Reducing Solution Scope Contact Us: 210.399.4240 info@enfocussolutions.com Copyright 2014 Enfocus Solutions Inc. Enfocus Requirements Suite is a trademark of Enfocus Solutions
More informationSuccess of Agile Environment in Complex Projects
Edith Cowan University Research Online Australian Information Warfare and Security Conference Conferences, Symposia and Campus Events 2010 Success of Agile Environment in Complex Projects Abbass Ghanbary
More informationProject Management: As it ought to be!
Project Management: As it ought to be! Brian D. Krichbaum September 21, 2007 Process Coaching Incorporated Project Management As it ought to be! Most of us are beyond the point where we believe that successful
More informationA Business Agility e-book. Planning your SharePoint Intranet
A Business Agility e-book Planning your SharePoint Intranet Business Agility is expert in the delivery of solutions built on Office 365 and SharePoint. 3 We build solutions to both the common and the
More information30 Course Bundle: Year 1. Vado Course Bundle. Year 1
30 : Year 1 Vado s 30 Year 1 Vado 1. Employee Career Aspirations Coaching Career Development 2. Communicate Clear and Concise Messages Communication Skills for Managers 3. Conflict Management Expectations
More informationA Business Oriented Architecture. Combining BPM and SOA for Competitive Advantage
Combining BPM and SOA for Competitive Advantage Phil Gilbert Introduction In a recent survey of 1,400 CIOs by Gartner Executive Programs, the top business priority identified by CIOs was business process
More informationThe Systems Development Lifecycle
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system developments projects The project Major attributes of the Lifecycle Moves systematically
More informationSoftware Engineering Roles. Kristian Sandahl
Software Engineering Roles Kristian Sandahl 2 Role catalogue Roles are needed to: identify and develop knowledge make sure that nothing is forgotten plan hiring and personal development avoid detailing
More informationAgile (Project) Management NOT a contradiction
Agile (Project) Management NOT a contradiction Barbara Roberts Agile Business Consortium Michael Young Australian Institute of Project Management Peter Coesmans International Project Management Association
More informationChapter 3 Project Management
Chapter 3 Project Management Overview What you will learn this chapter Executive Support Project Manager Process Tracking (PERT, CPM, Gantt) Summary of the chapter What you learned in this chapter Assignment
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 informationAgile Extremely Scaled
Product Owner in an Agile Extremely Scaled World Agilia 2016 - Olomouc Felice de Robertis Let s start from the Agile Manifesto Agile Manifesto - Values We are uncovering better ways of developing software
More information