Sometimes organizations that are adopting agile complain that they didn't get the benefits that they expected to get out of it. One of the possible reasons could be that insufficient attention has been given to performing the technical practices that support the agile values and principles.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.
Agile software development is sometimes perceived as an undisciplined way of working. There are organizations which use that perception as an excuse to not adopt agile. According to others agile is actually a more disciplined approach than waterfall for software development. Let’s explore how discipline plays a role in agile and why discipline is considered important for agile to be successful.
Successful adoption of agile is related to the approach that is used to introduce changes in the organization. Organization can do a top down “mandated” implementation or use a different approach. Kanban can be used as a way to kick start agile, allowing teams to opt-in to agile practices when they feel ready for it to create a sustainable new way of working .
Three of the organisations in the fractured Scrum community have jointly announced their collaboration and endorsement of the new ScrumGuides.org website as the official source of “The Scrum Guide, The Definitive Guide to Scrum: The Rules of the Game.”
The Scrum Turkey community have launched a program aimed at giving university graduates a deep experiential understanding of the Scrum framework. Going beyond just the two-day Scrum training this program requires participants to apply their knowledge and meet regularly with coaches to reinforce and expand their skills. The program is offered free to students and is supported by sponsorship.
Continuous deployment helps organizations in delivering high quality software fast through build, test and deployment automation. It gives earlier return on investment, earlier feedback and easy process of deployment. Is continuous deployment also good from business perspective?
Oracle have announced details for NetBeans Day 2014. Particular topics of interest include Maven, a new Education initiative and an appearance by James Gosling.
ZeroTurnaround has announced the discontinuation of their application release automation product, LiveRebel, claiming that the release automation market is not big enough because it is not one of the top problems that teams face, and there is no clear picture of what release management should be.
The 9th Annual State of Agile Survey is currently open for participants to share their adoption of Agile practices and processes for inclusion in the annual report.
Management can get the feeling of losing control when their enterprise adopts agile and starts deploying self-organizing teams. Procedures, review boards and consultation bodies can become superfluous when switching to an agile approach, but they may not realize that, says Marcel Heijmans. Trying to regain control with additional planning can make things worse, causing "death by planning".
Responding to recent concerns that hackers could upload rogue versions of common libraries to Maven Central, Sonatype has released a patch that closes a security vulnerability, enabling SSL by default.
At GOTO Amsterdam 2014 conference, agile coach Dan North shared his experience as part of a build team employed in a client project back in 2005. The team introduced several (technical and cultural) practices that became core tenets of the Continuous Delivery book and of the DevOps movement (for instance bridging the gap between development and ops teams was critical to success in that project).
Jesper Richter-Reichhelm, Head of Engineering at Wooga, spoke at GOTO Amsterdam 2014 about some of the challenges teams face developing mobile games with a continuous delivery mindset. In particular Jesper stressed how lack of control over the software delivery process on mobile nearly crashed their business.
Google engineers have recently published a research paper presenting an empirical study of 26.6 million builds produced during a period of nine months by thousands of developers at Google. The paper describes the build workflow, and analyzes failure frequency, compiler error types, and resolution efforts. Such a study, its authors say, can help improve the build process and support to developers.