program selection system

= Biggest problem:

Automated functional testing lives between two sensible testing activities. On the one side, there’s conventional TDD (unit testing). On the other side, there’s manual exploratory testing. It is probably more important to get good at these than it is to get good at automated functional testing. Once you’ve gotten good at them, what does it mean to get good at automated functional testing?

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects? Two issues - a better language to describe tests most product owners don’t speak Fitnesse - tools for acceptance of GUIs (hopefully even a common language with the webbies)

ii) What do you hope to contribute? - Questions - Coding skills (Java & .Net) if that turns out to be useful

iii) What do you hope to get? - An idea of the direction to go in the future

Over the course of this conference our stage has covered what it takes to succeed when practicing agile software development with legacy systems. The last session of our stage brings some of speakers back together as a panel. You should come prepared to ask questions and help us (as a community) summarize the key insights and ongoing questions concerning agile software development with legacy systems.

Thru conference and gathering participation, several companies who have been practicing Agile for a number of years discovered that most of the topics or discussions were not addressing the difficult issues facing larger organizations - i.e. performance management, distributed and offshore teams, Agile portfolio management, etc. Two separate Enterprise Agile discussions amongst the leaders of companies with large development teams and similar experience implementing Agile have been held.

90 Word Summary:

In February of 2002 in Snowbird Utah, the Agile Manifesto was written. It was intended to be provocative, to cause upheaval in an entrenched system of thinking. It targeted the brave and few mavericks willing to let go of a myriad of software development security blankets and instead create value through new dynamics. It is now August 2008 in Toronto Ontario. Are we holding onto too constricted views of that 2002 statement in a way that could be holding us back from continued systems innovation?

In the Web 2.0 age, end-to-end web testing provides tremendous feedback on the quality of your Web application. However this feedback cycle is typically quite long and comes at a high maintenance price. This talk shares our field experience in establishing web acceptance test suites with high return on investment (ROI) for Web applications.

Systematic is an agile CMMI level 5 company, where the default way of working is based on Scrum and story based early testing. Several years of Experiences in combining CMMI with Scrum, has shown that the mix of Scrum and CMMI provides strong synergies and results, which were reported during Agile 2007. This session presents specifically how agile methods like Scrum and story based early testing development can be sucessfully augmented with inspiration from CMMI. CMMI provides solid support for what disciplines to consider.

Developing software in a medical device company imposes a number of challenges on any methodology. There is a high level of dependency on hardware systems, long validation cycles and a strict regulatory environment which requires adherence to international standard and a high level of traceability. At Cochlear Limited (the largest cochlear implant manufacturer) we have been using agile software methodologies in this environment for just over two years.

Agile Development teams can utilize a number of techniques to visualize and track the items they work on. There is also various models to manage your personal life, Getting Things Done and the Mark Forster models.
For Product Owners and analysts there is a lack of similar tools and techniques. This demonstration will show how a Kanban board (task board with “states”) can be combined with a “round robin” scheme to keep analysist and Product Owners working on multiple tasks of high priority, but with potentially long lead times and fuzzy done criteria.