From agile development to agile evolution of enterprise systems
Upcoming SlideShare
Loading in...5
×
 

From agile development to agile evolution of enterprise systems

on

  • 1,293 views

 

Statistics

Views

Total Views
1,293
Views on SlideShare
1,292
Embed Views
1

Actions

Likes
2
Downloads
80
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • With a Ph.D. in information technology (IT), I have always worked in the provision of IT services. The posts that I have occupied have progressed through the phases of programmer, developer, business analyst, project manager to, most recently, enterprise solutions architect . Over the last several years, I successfully architected and delivered several IT solutions for different needs ranging from a heavy-duty production process to a federated distributed organization. I have innovated and employed an architectural framework for improving business process management systems. This framework is agile, service-oriented and provides for the integration of people, processes, systems and IT tools. Aiming towards achieving a good synergy between business needs and IT potentials, I have always managed to earn the respect and appreciation of users and clients. Skills and Experience Analysis and conceptual design of service-oriented architectures . A leadership role in the design and implementation of the automation of production business processes Experience in the design, implementation and maintenance of IT systems Successful use of the agile approach to software development . Strong leadership in the management of informal groups. Extensive experience with IT technologies Last position: " Chief Enterprise Solutions Architect " responsible for the architectural design, implementation, deployment and evolution of enterprise systems. The client base comprised international organizations, multinational and local companies, as well as public sector services in the French speaking part of Switzerland. Some work done: - development a ECM-based architecture for a private bank in Geneva (mainly for systems integration and business process automation), - demonstration of the Web Content Management solution for a public hospital, - preparation a proposal based on ECM products for a cantonal library, - implementing a working prototype of the document management for the ISO 9001 quality management system for an SME in Lausanne, - installation and evaluation of tools in a scope of a short-term contract with an international organization in Geneva for a pilot project on the archiving e-mails, and - discussing with several clients how ECM products and the “right” architecture can be used to transform their business operations to improve significantly their effectiveness and efficiency.
  • The illustration is taken from the book “The innovator’s dilemma” Plone is a disruptive technological innovation Plone already delivers performance demanded at the low end of the market Assuming that Plone targets also the high end of the market Treat Plone as an “adult” on the ECM and BPM market and in the enterprise environment
  • To automate and manage typical business procedures a multi-layer model has been used. Each layer is a level of abstraction of the business and addresses some particular concerns: The business data layer comprises information that is stored in existing repositories and traditional applications. The business objects layer comprises objects (actually, business data containers) specific for a particular business. The business regulations (and rules) layer comprises the actions on the business objects, which must be carried out to perform the business tasks. The business execution layer carries out the business procedures (each procedure is an orchestrated set of manual and automated tasks). The business modelling (and monitoring) layer analyses the business events, which summarize execution of the business procedures. The business intelligence layer implements enterprise-wide planning, performance evaluation and control actions applied to the business procedures. Each layer has some responsibilities; it uses the lower layer functionality, and it serves the higher layer. Each layer has a well-defined interface and its implementation is independent of that of others. Each layer comprises many building blocks that could be reused in different activities. Another practical observation is that different layers have life-cycles of different time scales: typical repositories have a 5-10 year life-span while the business requires continuous improvement. Because of the implementation independence of different layers, each layer may evolve at its own pace without being hampered by others. As a rule, the existing applications already implement many of business objects, relegations and events, but in a much unstructured way. The lasts are intermixed, not reusable and to be implemented again and again. This model is a tool which helps the organization to design system in business terms, but not in IT tools. Also, this model doesn't mandate to have all layers at the same time and to provide them in one project.
  • This model is applied for both meta- and micro-projects. In an established architectural framework, we don’t actively involved into micro-projects. (if system works without you then you did a good job). But, it is critical to control evolution of the architectural framework itself.
  • As the framework changes project management, two types of projects emerge; micro-projects for agile implementations of new features and meta-projects for framework maintenance and development. The latter resembles the Deming wheel: "plan" the feature(s) to be accomplished next as a micro-project according to results measurement and business priorities; "carry out" the changes; "validate" the changes; "analyse" the effect of the changes on the system and eventually propose unifications if, for example, a local modification was effective and should therefore be used to a wider extent. With a typical time per cycle per micro-project of 2 to 3 weeks, such project management is inherently different from the traditional multi year planning and the whole process becomes similar to maintenance rather than development. The descriptive below shows micro-projects mapped into phases of traditional IT projects. A note about timing – all values are real. They were achieved for automation of a production environment. Typical duration of a micro-project should correspond to a typical duration of related business. Typical timing of micro-projects: Definition phase: less than an hour. Specification / conception phases: one day Development / test / validation phases: from hours to days (depending on user’s availability). Deployment phase: practically instant. Definition phase: Business optimisation potential is evaluated. Features to be implemented are understood. Priorities and availability of features are communicated. Specification / conception phases: A product prototype using a workflow, an electronic form or a screen dump is used to validate what will be implemented. Missing components (if any) are identified and specified. Missing components (if any) are evaluated; use of new tools and/or utilities are justified. Development / test / validation phases: Missing components (if any) are incrementally developed, tested and validated. Complete product is assembled from existing and new components. The product is incrementally tested, validated and deployed. Extra monitoring, where necessary, is deployed. Resources requirements are estimated and the system is reconfigured to provide them. Production phase: The new product or latest version of the product is made available for use. In case of product or version replacement, verification of previous product retention cycle The documentation issue is addressed and simplified in several ways: Built-in document quality management system. Maximal use of visual tools (e.g. workflow, forms). User modifications are documented by the users IT-specific documentation is largely derived from the meta-project(s) and their adopted patterns. Programs, such as workflows, e-forms and schemas, work as documents and vice-versa.

From agile development to agile evolution of enterprise systems From agile development to agile evolution of enterprise systems Presentation Transcript

  • From agile development to agile evolution of enterprise systems Dr Alexander Samarin www.samarin.biz Clio S.A. EuroPython conference 2006, CERN, Geneva, Switzerland
  • Who am I? An enterprise solutions architect
    • Have always worked in the provision of IT services
    • From a programmer to a systems architect
    • Experience in academic, international and industry environments: CERN, ISO, IOC, BUPA
    • Have created systems which work without me
    • Current specialisation is improving business process management systems
      • effectiveness (“Do the right things”)
      • efficiency (“Do the things right”)
  • Agile software development is a classic case of disruptive technology
    • The customers appreciate it
      • an order of magnitude increase in IT value for the customers
      • no comprehensive up-front specs
      • results-oriented
    • The IT establishment criticises it
      • bad or no design
      • no documentation
      • works only for top professionals
  • My position: agile means adaptable
    • Agility is the ability not only to create change but to respond to change
    • Agility is the ability to balance flexibility and structure
    • Gartner: Agility is the ability of an organization to sense environmental change and to respond to it efficiently and effectively
  • A daunting optimisation task
    • From a typical enterprise environment:
      • a complex system of systems that has grown over years
      • a very hostile environment for new things
    • To a flexible business system which is easily adaptable to:
      • policies, priorities, existing data, IT systems, business processes, size, complexity, budgets, culture, etc.
    • Subject to socio-technical aspects:
      • how you do something may be more important than what you do
  • Lean production is an example of optimisation in industry
    • See the whole picture
    • Learn constantly
    • Decide as late as possible
    • Deliver as fast as possible
    • Eliminate waste
    • Empower the team
    • Build in integrity
    • Avoid sub-optimisation
  • Harvard Business School studies: development practices that spell success
    • Early release of the evolving product design to customers
    • Daily incorporation of new software code and rapid feedback on design changes
    • Teams with broad-based experience of shipping multiple projects
    • Major investments in the design of the product architecture
  • A dilemma
    • Agile software development is sound
    • … although there are valid criticisms (agile development is like racing a yacht and is not necessarily suited to captaining a liner)
    • We need it to deliver agile evolution of enterprise systems
    • Heuristic: sometimes it is necessary to expand the concept in order to simplify the problem
  • The main lesson from agile development: see and understand the big picture
  • Critical aspects for agile evolution of enterprise systems
    • The big picture (i.e. the enterprise architecture) is
      • available
      • understood
      • agreed internally by consensus
      • not “parachuted” by consultants or a vendor
      • addressing Business Process Management (BPM)
    • Development of the architecture for a particular enterprise should not be a project that takes many man-years and reams of pages
    • Business and IT use common tools
  • Enterprise means Business Process Management
    • Business Process Management (BPM) allows you to model , automate , control , measure and optimise the flow of business process steps
    • It spans your organisation’s systems, people, customers and partners within and beyond your corporate boundaries
    • Gartner estimates that there are currently over 140 business process management vendors
  • My approach to BPM (providing a fishing rod, not a fish)
    • Any enterprise has its own BPM system; some enterprises want to change it
    • An offer of an architectural framework for improving BPM systems
    • It makes use of the synergy that exists between business needs and IT potentials
    • Designed for agile evolution
    • Systemic approach and adaptability
    • Generic operational model (for business)
    • Advanced multi-layer model (for IT)
    • New features are added like pieces of Lego
    • Proven that BPM systems can be improved faster, better and less expensively
    Main characteristics of the architectural framework
  • Typical service and process oriented enterprise Business events : requests, payments, etc. Business processes Business events : offers, invoices, etc. Dept. Dept. Dept. Dept.
  • The simplified multi-layer model Execution Rules Objects Data repository repository repository repository
  • Why this approach produces agile systems
    • Many of the difficult issues are resolved:
      • Architecture, Methodology, Patterns
    • There is no “classic” application – instead, there is a set of orchestrated services
    • Services those are versionable and clonable
    • The business logic is kept in one place
    • This approach has proven itself: production system in place for several years; several successful (easy to do) migrations undertaken
  • Works with other technologies Portal Grid infrastructure ESB infrastructure Business data services Business objects services Business rules services Business execution services Business measurement services Business intelligence services
  • Agile implementation of a new functionality
    • A new functionality is generally implemented across systems
    • Any missing blocks are created in a dynamic language (e.g. Jython) and they are wrapped into services
    • It generally does not have its "own" database
    • It is "outside" existing systems
    • It reuses existing services
  • A common tool with BPMN and BPEL (e.g. www.intalio.com)
  • Many thanks to Jython
    • Excellent as the glue between enterprise applications
    • Easy to manage (e.g. fragments are kept in .jar)
    • Highly flexible (i.e. introspection)
    • Dynamic loading and execution
    • The only thing that was added:
      • a .py wrapper to simplify execution
  • Real agility achieved: two types of project
    • Micro-projects – agile implementations of new features
    • Meta-projects – architectural framework governance for the management of many micro-projects
      • looks like maintenance rather than development
  • Meta-projects are carried out in a manner similar to Deming’s wheel
    • Plan
      • fact- and rule-based selection of what should be done next as a micro-project
    • Do
      • execution of a micro-project
    • Check
      • new findings and solutions are considered for wider use
    • Act
      • refactoring of the system
  • Management of micro-projects
    • In-depth knowledge of the domain is essential
    • Sharing "the vision" with the business process owner
    • Architecting the product (i.e. a business process) in terms of IT and business systems
    • Guiding the project team to implement the product
    • Giving practical help, if necessary
    • Facilitate, influence and coordinate rather than control and act as the ultimate authority
  • Micro-projects: definition phase
    • Business optimisations are evaluated
    • Features to be implemented are understood
    • Priorities (availability of features) are communicated
  • Micro-projects: specification / conception phases
    • A prototype of a product (e.g. an executable business process diagram) is used to validate what will be implemented
    • Missing components (if any) are identified and specified
    • Missing components (if any) are evaluated; use of new tools/utilities should be justified
  • Micro-projects: development / test / validation phases
    • Missing components (if any) are incrementally developed, tested and validated
    • Whole product is assembled from available and new (started as dummies) components
    • Whole product is incrementally tested, validated and deployed
    • Extra monitoring (if necessary) is deployed
    • Necessary resources are estimated and the system is reconfigured to provide them
  • Micro-projects: production phase
    • New product or new version of a product is declared available for use by the business or by other components
    • In the case of replacement, some estimations are made when the previous version of a product is to be discontinued
  • Typical timing of micro-projects for standards production automation
    • Definition phase: 1 hour
    • Specification / conception phases: a few hours
    • Development / test / validation phases: a few hours / days (depending on user’s availability)
    • Production phase: practically instant
  • Address some criticisms from the following book
    • “ Extreme Programming Refactored: The case against XP”
  • “ Extreme culture” (jumping straight to code)
    • There are no obstacles
      • General design and patterns are available
      • Use a common tool for business process mapping
      • Can start with the existing process and refine it
      • A solution is firstly and quickly coded in executable business process diagramming language
  • “ The on-site customer” (as a replacement of requirements)
    • Close work with the customer is mandatory
      • It is just about changing the IT attitude towards the users
      • From master to service provider
      • From talking 95 % about IT issues and 5 % about business issues to a 50 % - 50 % balance
    • Follow one of the principles of the Toyota Production System (TPS):
      • Go and see for yourself to understand thoroughly the situation
  • “Pair programming” (for compensating absence of design, documentation, etc.)
    • From permanent pair programming to systematic code reviewing
      • Code review is necessary to keep conceptual integrity
      • Programming is a way for communication between humans
      • It is a good way to involve junior programmers
    • Follow one of the principles of the TPS:
      • Grow leaders who thoroughly understand the work, live the philosophy and teach it to others
  • “Oral documentation” (documentation in XP tends to be paradoxical and confusing)
    • A lot of documentation is already available, but often IT rejects it:
      • Architectural design document is too complex
      • Workflow diagrams are too much business
      • Jython code requires some formal training
      • Quality documentation (considered bureaucracy)
  • “ Constant refactoring after programming” (If it ain’t broken, fix it anyway)
    • Any enterprise system is never finished
      • Business and IT meaning of “broken” are rather different
      • Features are added if needed
      • It is a very dynamic system
    • Follow one of the principles of the TPS:
      • Become a learning organisation through relentless reflection and continual improvement
  • Lessons learnt
    • Combining the architectural framework and agile software development allows building of agile enterprise systems
    • The use of common tools by both the business side and the IT side is of great benefit
    • Neither agile development nor any architecture works well if the politics don’t fly
  • If the politics don’t fly, the system never will
    • Politics, and not technology, sets the limits of what technology is allowed to achieve
    • Cost rules
    • A strong, coherent constituency is essential
    • Technical problems become political problems
    • The best engineering solutions are not necessarily the best political solutions
  • THANK YOU
    • Questions and answers
  • Short description
    • The aim of this talk is to share my experience in the use of a practical architectural framework for the improvement of enterprise business systems. This framework uses a dynamic language (i.e. Jython) and agile development practices. Experience with business acceptance and composition of applications are discussed.
    • This presentation is complementary to my presentation at Plone conference 2005 in Vienna (“The use of Plone for enterprise solutions”) – it is focused on the technical and practical aspects of agile evolution of enterprise
  • Architectural framework experience (1)
    • Architectural framework provides a basis for technical and political decisions
    • IT development is unified
    • The target is business process automation and not applications development (brings greater flexibility)
    • The system is built mainly from commodity functional blocks (commercial and freely available) that are not modified
  • Architectural framework experience (2)
    • The system is built incrementally (quicker ROI)
    • High level of user involvement
    • Team has ownership and customizes its approach
    • Project retrospection (no post-mortem or witch hunt)
    • Achieve synergy between practices, principles and experiences for building software systems
    • Take advantage of the organisational business and organisational knowledge
  • Based on SOA: In general, a layer, a building block and a version of a building block are all services WSDL GUI (optional) Service logic Service database (optional) Other services (optional)
  • Micro-projects: documentation
    • Built-in quality management system
    • Use of visual tools (e.g. business process diagrams, forms)
    • User management, maintenance and programming
    • IT-specific documentation is mainly available from the meta-project and adopted patterns
    • Programs as documents and documents as programs