If you ever worked in a project where a scaling factor applies, you know that appropriate tooling can help a lot achieve your objectives. But on the other hand, tools are often identified as impediments for agile adoption.
The Agile Scaling Model defines several reasons why you may work in an environment where core agile practices are not sufficient. But even in such an environment, you want to ensure your product owner, your scrum master, your development team, and your stakeholders collaborate efficiently through sprints and releases.
IBM Rational provides an ALM (Application Lifecycle Management) for disciplined agile teams. Based on Jazz, the platform integrates requirement management, design management, quality management, and change management. Team members and stakeholders have access to the same project information and assets from a web browser. Anytime, from anywhere (distributed teams will appreciate!). They can collaborate through a centralized platform., The Jazz repository provides real time status on project progress. And the team can quickly react to changes by leveraging lifecycle integration and traceability, dashboards, queries, impact analysis, an reports.
Because the ALM platform leverages OSLC, you can even integrate with other OSLC compliant vendors. No more vendor lock-in. No more silos. Everyone working together to deliver better software. This is agility for ALM !
Pragmatic Architecture, DevOps, and Cloud Computing
Matching: alm X
jl.marechaux 060001NWA6 Tags:  alm rational agility-at-scale agileadopt architecture tools rsa pragmatic agile clm 4,545 Views
jl.marechaux 060001NWA6 Tags:  featured agileadopt agility-at-scale architecture clm alm pragmatic agile rational 5,383 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.
jl.marechaux 060001NWA6 Tags:  alm rational agility-at-scale agileadopt featured agile architecture pragmatic clm 4,835 Views
[Previously on ALM and agile design..... The pALMatic architect]Seasoned agile teams want to address risk early in the process to remove uncertainties as soon as possible. When a story may imply some technical challenges, it is a safe approach to increase its priority. Also, pragmatic practitioners know that some dependencies may exist between stories. Sometime, a high priority story can only be implemented once the work of a related story is completed. So when a new iteration starts, it is important to identify the most risky stories and to uncover the dependencies between features. This information influences development priorities for the team.
Agile teams develop software iteratively. The product backlog lists all the stories to implement and the team decides which ones they will address during the next release or iteration. In an ALM environment, teams want to plan and align their activities across all the disciplines, including requirements, design, development, and tests. The real challenge is to identify the right set of features to develop first. Any mistake in the priorities will lead to plan commitments that you will not be able to deliver. For most teams, business value is an important factor to prioritize the product backlog. But other aspects must also be considered, such as risks and dependencies.
How can you identify risks and dependencies? In most software-intensive systems, practitioners must apprehend the structure of the application before they commit to deliver any change. They must also understand the impact of a new story or a change request on the existing code. This is where design helps. It provides insights to the team so that they prioritize the backlog based on concrete information. With a quick access to a design element or a diagram, team members can decide if the priority of a story must be increased. They may even conduct a brief brainstorming session to better understand the technical challenges.
Design management is an integral part of ALM to deliver software-intensive systems in a complex environment. During planning activities, agile teams refer to design information to make rational choices. The backlog is prioritized as the team takes into account the business value, the risks, and the dependencies.
For the 4th consecutive year, the Agile Tour (http://www.agiletour.org/) will stop in Montreal this Fall. With more than 450 attendees last year, the Montreal conference is the right place to meet Agile experts and practitioners.
For the first time this year, I am part of the conference organizing committee. I am very excited about it! I hope we will prepare a high quality and unforgettable event.
FYI, the call for speakers is now open. So if you happen to be in Montreal (Canada) on November 24 and you want to share your Agile experience, do not hesitate to submit a proposal.
Agile Tour Montreal conference
jl.marechaux 060001NWA6 Tags:  agility-at-scale agile architecture agileadopt rational rsa alm 4,322 Views
In July, Todd Dunnavant and I presented at the Good Design is Good Business, a virtual, online conference for both clients and IBMers.
We talked about the collaborative design management capabilities (DM) that are being added to the IBM Rational offering.
Design Management (DM) is an ALM discipline that integrates software and systems design into the lifecycle. DM extends ALM disciplines such as requirements management, change & configuration management, and quality management.
The presentation material is now available online. It covers lifecycle integration, in-context collaboration, and lifecycle traceability.
Later this year, we plan to have more in-depth sessions on Design Management & ALM. Stay tuned....And join the Good Design is Good Business community group to be notified about future webcasts.
If you want to be a speaker at AgileTour Montreal, hurry up, you've got until Sept 12 to submit your presentation proposal. In you are in the Montreal (Canada) area, this is a great opportunity to share you experience on agile practices.
jl.marechaux 060001NWA6 Tags:  rsa agile alm clm rational architecture agileadopt agility-at-scale 4,651 Views
The IBM Rational Solution for Collaborative Lifecycle Management has a new component!This new version contains many enhancements to the 3.x release, in particular the integration with CLM 2012. CLM and DM can share the same centralized server and repository. The common administration console provides a single interface to manage users, roles, permissions, licenses, and lifecycle projects.
Rational Software Architect Design Manager 4.0 has been released on September 7th.
Design Management capabilities include reviews, comment, document generation, impact analysis, configuration management, lifecycle traceability and many other features for effective collaborative design management.
With the addition of DM 4.0, CLM 2012 provides a comprehensive environment for agile Application Lifecycle Management (ALM): requirements management (RM), design management (DM), quality management (QM), and change & configuration management (CCM). All natively integrated using the Open Services for Lifecycle Collaboration (OSLC) standard.
With CLM 2012 (including DM 4.0), teams can link designs to requirements to ensure that technical solutions are aligned with business needs. All team members and stakeholders can easily access design information during development sprints. They collaborate on design activities and are involved in design reviews. They leverage dashboard mashups to gather information on requirements, designs, tests and changes. Application delivery is facilitated with access to real time planning. Reaction to change is improved with lifecycle traceability and impact analysis.The centralized environment provides live reports on the development team to reflect the activity and trends of the team. All the information collected during a project is used to improve the team dynamic and fine-tune the ALM platform for better productivity.
In-context collaboration, real-time planning, lifecycle traceability, development intelligence and continuous improvement: 5 imperatives for effective ALM that CLM 2012(with DM 4.0) supports.
Go to jazz.net for more information on new DM 4.0 features. https://jazz.net/downloads/design-management/releases/4.0?p=news
jl.marechaux 060001NWA6 Tags:  architecture clm agileadopt rational alm agility-at-scale rsa agile 4,801 Views
About 10 days ago, I blogged on the new Design Management 4.0 release. If you want to experiment with design management, you can download the DM 4.0 trial edition.
Now to gain skills on DM 4.0, wouldn't it be cool to have access to some training material?
Guess what.... ? DM 4.0 contains a free self-paced training to help you adopt the product in your environment. The training includes:
Again, this is free. Yes, you heard me...FREE! So you cannot miss this opportunity to learn through hands-on labs.