Thursday, March 29, 2012

The Future of ALM

A keynote presentation describing recent trends in Application Lifecycle Management (ALM) using a car manufacturing example. With, for example, four dozen software suppliers, we see huge software ecosystem changes. His observations:
  • Taiwan now approaching Germany as top eclipse downloader
  • Software development increasing much faster than workforce
  • Henry Ford doubled employee salary, automation next
  • Toyota's just-in-time gave every worker autonomy - able to stop line
  • Empower the people
  • Autonomy, Transparency, Collaboration
  • Software delivery silos: testers, project managers, devs, business analysts, operations
  • Cultural gaps, devs see all devs as rocket scientists, etc.
  • Boeing had delays because of software traceability
  • Handing off to each production stage lost accountability and traceability
  • Long term cost
  • They stopped production to fix traceability
  • Requirements -> development -> testing -> operations
  • Just in time = reduce inventory
  • In development, it's requirements
  • No link between req and ops
  • Toyota proved it's faster not to batch up what's handed off
  • Optimize task batch size = collaboration
  • Task needs to maintain workflow, activity and context
  • Incorporate social stream
  • Mylyn's model: planning, product, user story, task, commit
  • Expose Mylyn workflow
  • Contribution, workflow, automation
  • Gerrit -> Hudson -> review task -> build -> Mylyn workflow -> review -> push = collaboration
  • All involved need to collaborate.

No comments:

Post a Comment