[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)
Pragmatic Architecture, DevOps, and Cloud Computing
Matching: rational X
jl.marechaux 060001NWA6 Tags:  architecture agileadopt alm-sig agility-at-scale clm rational pragmatic alm agile 7,139 Views
jl.marechaux 060001NWA6 Tags:  alm pragmatic alm-sig agileadopt architecture clm agile rational agility-at-scale 4,791 Views
Interested in agile ALM and collaborative architecture? Check the video at https://www.youtube.com/watch?v=O70P8IpV0oY. It will only take 3:20 minutes of your time.
Then read the related article published on developerWorks and tell me more about the pragmatic architecture approach that you have adopted in your agile projects.
Share your experience!
jl.marechaux 060001NWA6 Tags:  pragmatic agile alm-sig alm rational agility-at-scale clm architecture agileadopt 4,755 Views
Just back from Agile Tour 2012, a conference held in Montreal (Canada) on November 24.
Ok, it was not a long trip as the conference center is probably at less than 2 miles from home.
This year, I was a member of the organizing committee. Quite an experience which started around March, an initiative led by the Agile Montreal community.
Key facts and figures from the conference:
People I talked too during the conference are not interested in the "agile dogma". They value "pragmatic agility", agility applied to their specific context. Sometimes it means governance, sometimes ALM, sometimes lean software development.
So far the feedback from attendees is very good. It was an amazing day. I am glad I had the opportunity to be involved in the organization of this conference.
jl.marechaux 060001NWA6 Tags:  architecture agileadopt agility-at-scale clm alm agile alm-sig pragmatic rational 4,487 Views
I will be a speaker at Agile Tour 2012 (Montreal) on November 24. My session is about the role of the agile architect in an ALM environment.
Here is a teaser.....I hope it will prompt people to attend the session.
What someone can expect to take away from the presentation?
Table of content
Interested?..... Take a look at the Agile Tour 2012 (Montreal) page for further information.
jl.marechaux 060001NWA6 Tags:  architecture rational agile agility-at-scale alm-sig clm alm agileadopt pragmatic 5,061 Views
Pragmatic architecture for agile Application Lifecycle Management is a new article published on developerWorks this week. It covers Agile concepts applied to architecture using the Rational Solution for Collaborative Lifecycle Management (CLM).
Architecture & design is a key discipline in ALM. Agile teams value pragmatism and practical experience over dogmatism and theory. They focus on key collaborative design activities that accelerate the development of software-intensive systems. Design information can help during several agile activities such as backlog prioritization, sprint planning, development, impact analysis, and technical debt reduction.
Read more here....
Studies show that a lot of software systems are not aligned with business needs. Sometimes, it is because a few requirements are not implemented. Most of the time, it is because the software system contains features that do not correspond to any real requirement.
The main challenge for a development team is to understand the requirements. Otherwise, the team will develop features that nobody needs. But understand requirements is not easy in business domains always more complex.
Let's take a simple example. On the following diagram, here is the requirement: "Connect the nine dots with four straight lines, without lifting the pencil".
You've got it? Bravo!
If you don't, read the requirements one more time. Take your time. Need some help to find the solution? Click here.....
Don't worry if you failed to solve the problem. The test is a well known cognitive science puzzle. Most of use are supposed to fail. Why ? Simply because of the way our brain works for problem solving. We interpret the problem statements in the light of our own knowledge and experience. In other words, human reasoning is often biased.
So what can we learn from this?
Requirements are hard to understand. And we (our brains) often misinterpret the needs. So it is no surprise that software systems do not always correspond to initial requirements. Agile teams should catch on cognitive science.
Agile approaches foster collaboration between business people and developers throughout the project. When the development team works closely with the customers, requirements are clarified on the fly, during informal discussions. The overall quality of a software system is improved.
In the nine dots square example, it would have been helpful to ask questions about the requirements. You would have discovered early that there is no constraint to keeps lines inside the square. The solution to the puzzle would have been easier to find.
Great news in this OSLC world this month. Eclipse Lyo 1.0 is now available and IBM Rational Lifecycle Integration Adapters 1.0 has been released.
Eclipse Lyo is an open-source initiative to make OSLC more meaningful and approachable. Lyo contains a Java toolkit for building OSCL applications (OSLC4J), an OSLC reference implementation, and an OSLC test suite (to measure your implementation compliance against OSLC specification). Lyo also provides documentation and samples to help people adopt OSLC.Rational Lifecycle Integration Adapters is a set of adapters to facilitate integration between the IBM solution for Collaborative Lifecycle Management (CLM) and third party offerings such as HP ALM, Atlassian JIRA, and open source Git.
With Eclipse Lyo, it is easier to develop OSLC providers and consumers. With Rational Lifecycle Integration Adapters, it is straightforward to integrate heterogeneous lifecycle products (different products, from different vendors). And of course, OSLC continue to evolve to better support lifecycle integration. Check it out at http://open-services.net/
jl.marechaux 060001NWA6 Tags:  architecture clm agileadopt rational alm agility-at-scale rsa agile 4,838 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.