Agile development and testing can help to achieve the security and quality of software that users need and stakeholders expect.
One of the most common issue no matter how much agile adoption has matured within enterprises is investment on environments/infrastructure and deployment automation. My experience working with organizations where a whole hearted recognition of investment on development and test environments is required, has not been that great and hence the post.This only reduces the capability of team to deliver continuous value.
CloudBees, Inc., the Java Platform as a Service (PaaS) innovation leader, today announced that the Codesion cloud development platform from CollabNet, is now offered as part of the CloudBees Partner Ecosystem. CloudBees provides the only Java PaaS that offers easy, one-click access to integrated, partner-provided services.
A common question that a Scrum coach would face while transitioning an organization into Agile is “Why story points?” While this question appears very trivial, people seem to ask this question very seriously. Before we attempt to answer the question let’s have a quick look at what the story points are?
The daily standup meeting or scrum meeting presents the team with a regular opportunity to synchronize development activities with the iteration plan and to check and reflect on the progress of the team’s commitments towards the iteration goal. As a forum for communication and feedback, the team members co-ordinate their work and make a commitment to the team about what they aim to achieve in the day. They also identify any difficulties and obstacles to progress. The meeting is not intended to generate solutions nor remove obstacles.
Any product team in today's world would want to deliver any or every feature right away and right now. Needless to say this not just puts pressure on the development teams but majority of times end up messing the entire hardwork they have done adopting agile to deliver continuous value. The natural course of action is to prioritize the product backlog in such a way that the value reaches the customer as quickly as possible and there is a commitment on minimum deliverable along with some others as should or could deliver kind of scope.
I’m reading books on TRIZ and becoming enthusiastic about its potential for software development industry. Yes, it is not clear how to apply it directly, since TRIZ focuses on technical systems, but I believe we can apply general rules and even have solution patterns in the future. TRIZ has several patterns of evolution. Here are my thoughts about the most interesting patterns and their applicability to software development.