The aim of the project “Improving quality of QA stress testing and Feedback mechanism” is to give a formal data to support the decision taken during planning. The data could be refined over each releases to get closer to the goals. The project will have two stages where we first define the metrics to collect the required data. The second stage will retrieve information from the data and give feedback to the current quality of testing. A. What is done in the project to achieve the

Continuous Delivery is important in agile development for rapid feedback. Building a full Continuous Delivery Pipeline can seem like a daunting task. This talk will demonstrate that this is not the case by building a working Continuous Delivery pipeline in less than 1 hour. This knowledge can then be extended for use in more complex systems. The talk will introduce Rake, Powershell Remoting and YAML as tools in a .NET developers toolbox to create a simple & cost effective Continuous Delivery pipeline.

Acceptance Test Driven Development has been around for a while. Recent improvements in tool support make ATDD more prevalent, and this topic more relevant. ATDD makes testing, especially functional testing, the responsibility of not just testers but the entire team. Developers start by writing a failing automated functional test (guided by BAs/QAs), and then make the test pass. Much alike the complementing practice of TDD.

In this no-nonsense demo of ATDD using JBehave, a Java framework for BDD-style tests, I will use start-to-end examples to highlight the ATDD process and resulting tests.

Cucumber lets software development teams describe how software should behave in plain text. The text is written in a business-readable domain-specific language and serves as documentation, automated tests and development-aid - all rolled into one format. Cucumber enables developers and product owners to communicate in a manner that has never happened before in the software world. In this session, I will introduce Cucumber, its usage and its advantages. The code shown will be in Ruby and Java.

Velocity is such an important metric for agile teams that is used to see how fast or slow a team is building the features. Though this metric seems to be simple, it is very loaded in my opinion. I would like to explain what exactly is Velocity and how to interpret and how to it.

This demo will show that it is possible to setup a CD infrastructure from scratch with open source [and free!] tools and without much effort. We will also demo specific techniques such as Feature Toggling which allow the team to take advantage of this infrastructure.

Finally, we will talk about the value of such a CD setup for a services start up. Eg: A non-techie client can preview a feature in Staging and deploy the feature to PROD by themselves.

This is a stage show performed by 3 persons playing the role of customer, developer, domain expert, business analyst and developer. The story covers all the important stages of an agile project project: * contract negotiation * vision, initial design, release planning * acceptance test definition * test driven implementation of the first sprint The show ends up with working software automatically deployed onto a remove server.

The script’s style is similar to this: http://agilerenovation.com/#English/Publications/Cartoons.html animated cartoon.

“Release Early, Release Often” is a proven mantra, but what happens when you push this practice to it’s limits? .i.e. deploying latest code changes to the production servers every time a developer checks-in code?

At Industrial Logic, developers are deploying code dozens of times a day, rapidly responding to their customers and reducing their “code inventory”.

This talk will demonstrate our approach, deployment architecture, tools and culture needed for CD and how at Industrial Logic, we gradually got there.

Rational Outsourcing Solution targets at rapidly developing software outsourcing market. It helps the outsourcers&outsourcees strengthening collaboration through transparent agile/traditional managing process in outsourcing business. . Protect clients’ current investment to their development infrastructure by integration via standardized APIs (OSLC) . Hide the general complexity from customer by delivering one more layer on CLM platform to remove the barrier of making decisions . Best leverage government’s investment in Software Parks to grow software companies.

The talk will help its attendees understand the founding principles of a Kanban based system, the advantages of adopting lean techniques in software projects and the various trade offs of adopting the Kanban principles. The talk describes the experience of a project that adopted the Kanban principles to execute a project. The methodology borrows many of its concepts from the Lean world such as Pull based work streams, minimum work in progress and awareness about slack. The talk describes the various decision points and why a particular technique was adopted and what were the outcomes.