LOGIN | REGISTER NOW | SUBSCRIBE
 
Print

Developer Populism is changing the face of ALM


By Dave West


 Dave West
Email
July 9, 2012 —  (Page 2 of 2)

Developer Populism, a special form of tech populism, describes how practitioners are bringing in technology from home and the open-source community to better serve them in their job. The example often cited are workers bringing their Macs into the office even though the company gave them a PC. Developers not only bring in different machines, but also the tools for building software and sometimes the software itself.

And there’s the rub: Software innovation is crucial for business opportunity and value, but to do it requires empowered, innovative software engineers. Management practices encourage process and control over empowerment. ALM, the application of management discipline to the practice of software engineering is, for many, the embodiment of anti-empowerment and choice. But it does not need to be that way!

Instead of concentrating on one tool to “bind them all,” ALM vendors need to instead focus on enabling the value streams of multiple tool adoptions. To do this, they need to embrace tool variety, while not forgetting the principles and practices of ALM. It should not be forgotten that the increased use of good business management to software development will help everyone. This leads to the creation of a different sort of ALM, an ALM that:

• Concentrates on federation of development systems of record instead of forcing each practitioner to use one tool. Consider the value stream of software delivery to be heterogeneous in nature, with many tools providing their own system of record. Each system of record must provide its information in a way that allows it to be unifying into one definition of the truth about the application and projects.  
• Adopts open standards for integration instead of imposing a set of vendor-appointed standards. By applying standards such as REST and the de facto standards provided by open-source tools, the ALM strategy will be better placed for success.  
• Provides transparency across tools instead of focusing on one vendor’s data without any regard for the other vendors in the development stack. This requires tools to integrate data from other tools in their own context. For example, bugs may be discovered in the testing tools, but then used in backlog reports for the project management tool and then resolved in the IDE.
• Allows for workflow to be delegated to different tools instead of expecting one tool to manage the whole value chain. Expect that each tool will come with its own workflow. For example, a defect’s state will be managed by each tool that uses it, but each tool will be responsible for checking with the other tools to ensure that it has not violated the aggregated workflow.
• Integrates the whole life cycle instead of focusing on just development. By not applying a single-tool approach, it is possible to consider the whole value stream, not just the development or software development life cycle. Portfolio Management and operations can be included. ALM becomes the enabler to the emerging DevOps and agile demand management trends.

Developer Populism is happening with or without management’s blessing, but that does not mean that you have to lose out on the promise of ALM. Traceability, reporting and workflow can still be served, but in a different way. By concentrating on integrating the development flow, organizations can better position ALM as a unifying, rather than disruptive, technology that allows software developers and their teams to work together in the tools of their choosing. By combining ALM and Developer Populism, perhaps we are on the first step toward making software delivery a truly integrated discipline, where management and development work together to efficiently deliver amazing software.

Dave West, who led the development of the Rational Unified Process at IBM Rational, is Chief Product Officer at Tasktop. Guest Views are contributions by SD Times readers. Interested in contributing a Guest View? See the guidelines for the details.


Related Search Term(s): agile, ALM

Pages 1 2 


Share this link: http://sdt.bz/36784
 
Most Read  Latest News  Resources
SAP unveils SAP HANA platform innovations for Big Data and spatial processing
Features include smart data access and expanded cloud deployment options
Alteryx raises $12 million to put Big Data analytics in the hands of all business analysts
Quest founder's firm, Toba Capital, selects Alteryx as its first analytics investment
Google I/O kicks off
Developers get new APIs and tools, and the Go language hits version 1.1
Jelastic launches new version of its Java and PHP hosting platform
Jelastic today announced the launch of a new version of its ultra-scalable cloud hosting platform
Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter



Comments


07/10/2012 10:13:03 AM EST

Nice article, on "Open standards" I might clarify that REST is really just an architectural style and by just doing REST does not just give you integration. OSLC http://open-services.net actually defines implementable specifications based on REST-style and Linked Data architecture and defining vocabularies for various ALM resource types.

United StatesSteve Speicher


close
NEXT ARTICLE
Agile and ALM: Banded together
ALM 2.0 is insufficient to meet today's needs, but infused with agile, it may yet be useful Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
MAY 2013 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?