- Team collaboration
- Evolutionary design
Pragmatic Architecture, DevOps, and Cloud Computing
jl.marechaux 060001NWA6 Tags:  pragmatic architecture clm alm-sig agility-at-scale agile rational alm agileadopt 11,075 Views
Yesterday, I was co-presenting an InformationWeek webcast on Agile Development: Three Pillars of Success. With Vishy Ramaswamy , the lead architect for Design Manager, we talked about some agile architecture practices and how these practices were adopted by the IBM development team to create and deliver the Design Manager product.
During the Q&A session, there was a question that we saw a question that we did not answer (lack of time, too many good questions). It was something like: “What should we pay attention to when we try to adopt agile architecture practices on our projects?”
When I started this blog, I used the following description (from http://bitly.com/Sg2FQe) to define what Pragmatic Architecture is:
To summarize a bit, I would say that the three pillars of pragmatic architecture are:
jl.marechaux 060001NWA6 Tags:  alm-sig agileadopt pragmatic agility-at-scale alm clm architecture agile rational 9,396 Views
Earlier this month, Dan Leroux and I delivered a session at the Innovate 2013 conference. Our objective was to cover two different aspects:
Back from Orlando, I created a prezi with some of the information that we presented during the conference.(Click the image to launch the presentation)
jl.marechaux 060001NWA6 Tags:  architecture agileadopt alm-sig agility-at-scale rational clm pragmatic alm agile 7,072 Views
[Previously on ALM and agile design.....Part 2 – Release plans, iterations, and design ]
Each sprint begins with a planning exercise where the team defines the sprint goal and the sprint backlog. Team members examine the backlog to select the most valuable stories that can be contained in the sprint.
During sprint planning, design information can be used for three different purposes.
First, to assess the technical feasibility of a requirement. If the new feature is straightforward, then this task can be skipped, but for more complex features, the team can explore different design options to agree on a target solution.
Second, design information is used to identify the tasks to implement the sprint stories. A technical perspective on each story is needed to understand the work to complete. For some stories, the team will need to develop new component, for others, the team will need to integrate or reuse existing assets.
And last but not least, agile team can leverage design resources to evaluate the development effort. If the team is using the planning poker technique, design information will help choose the right card.
Development effort should be assessed based on the understanding of what needs to be delivered. Design information helps the team identify what can be delivered (technical feasibility) and what can be contained in the next sprint (estimation)
jl.marechaux 060001NWA6 Tags:  architecture rational clm agility-at-scale alm pragmatic agileadopt agile alm-sig 6,468 Views
In June, I will be a speaker at the Innovate Conference in Orlando, FL. The presentation will describe how a lightweight design approach supports agile teams to deliver software. Real examples from the internal Design Management development team (the IBM lab) will be used to illustrate the approach.
I am honored to co-present this session with Dan Leroux, Distinguished Engineer at the IBM Lab.
If you are interested in attending the session at the conference, here are the details
jl.marechaux 060001NWA6 Tags:  rational architecture pragmatic agileadopt alm agile alm-sig webcast clm agility-at-scale 5,924 Views
On January 22, I co-presented an InformationWeek webcast with Vishy Ramaswamy. the architect of the Design Management Server. The webcast was mostly an informal discussion where Vishy and I shared our opinions on four different topics.
The replay and the slides are available on--demand from the InformationWeek website at https://www.techwebonlineevents.com/ars/eventregistration.do?mode=eventreg&F=1005386&K=CAA1AC.
To access the material, you need to register with a valid email address. You will receive an email with a link to the recording session.
jl.marechaux 060001NWA6 Tags:  featured agileadopt agility-at-scale clm architecture alm agile pragmatic rational 5,359 Views
Today I am starting a series on ALM and Agile design (probably 4 or 5 different posts in the coming weeks).
A bit like humans, software-intensive systems are conceived, come to life, grow, evolve, do their job to contribute to business goal achievements, are retired, and die. Application Lifecycle Management (ALM) is the process of managing a system throughout its entire life.
In small teams and simple environments, core agile practices are usually enough to manage applications. For agility at scale, things are a bit more complicated. ALM is often defined as an approach that integrates disciplines as diverse as requirement management, design management, quality management, and change and release management. Benefits are obvious. ALM breaks down functional silos and promotes collaboration and role-focused views of the application lifecycle. The entire team gets greater insights into the project. Actionable information leads to better productivity, improved quality.... and enhanced customer satisfaction.
Design management is a key building block in ALM. The pragmatic architects do not work in isolation (read more on Pragmatism in architecture) . Those completing architecture and design tasks want to understand the business needs (requirement <--> design). They also have to make sure that the design supports the implementation of the solution (design <--> code). And design is eventually validated by some tests to validate its quality (design <--> tests).
In other words, design participates in lifecycle traceability. During the life of the application, the pragmatic architect evolves and refines the design to meet changing requirements and new technical challenges. And the pragmatic architect also ensures that the design information is available for efficient requirement management, quality management, and change management.
The pragmatic architect is also a pALMatic architect:
Design management is an integral part of ALM to deliver software-intensive systems in a complex environment. The pragmatic architect manages design information and conducts design tasks for successful and collaborative ALM.
The Rational Solution for Agile ALM is for customers looking to adopt Rational Team Concert (RTC) throughout the development of their Agile ALM projects. The solution is free to customers (and RTC is free for up to 10 developers).
The Agile ALM solution Release 2 is compliant with RTC 4.0.5, and is consistent with the latest version of the Scrum Guide published in July 2013. With this new release, we have improved the following assets:
Read more on the Agile ALM Solution and download the free assets at http://jazz.net/downloads/agile-alm-scrum/latest/
IBM Rational Solution for Agile ALM Release 2 is now available!
The IBM Rational Solution for Agile ALM is for teams seeking a solution for agile software development adoption and automation. This solution brings together our core agile product, IBM Rational Team Concert™ (RTC), practices, and supporting assets to help agile teams maximize the value they can achieve through agile development using Scrum.
The IBM Rational Solution for Agile ALM makes it easy to adopt and automate Scrum. Governance is "baked in" with tool automation defined by the template, while in-context guidance advises the team what to do next. The solution directly supports key Scrum artifacts (Product Backlog, Sprint Backlog) and events (Sprint Planning, Daily Scrum, Sprint Reviews and Retrospectives) in an integrated environment that maximizes transparency, collaboration and productivity.
The following are the core solution assets and links to where they can be accessed, free of charge:
if you wonder how to be agile in an ALM context or if you want to engage with other agile practitioners, visit the DevOps community forum