Teams sometimes consider to skip a retrospective meeting, when they feel time pressure, or do not see direct benefits of doing one. Next they question themselves if they have to keep doing retrospectives? Agile retrospectives help teams to learn and improve continuously, and there are valid reasons to keep doing them also with mature teams.
Microsoft and Google are working together in a fight for greater transparency on Foreign Intelligence Surveillance Act (FISA) orders. Not satisfied with the limited out of court agreement that’s already been reached with the US government to disclose summary data relating to national security requests, the two companies are now taking legal action and lobbying for support from Congress.
Recently Steve Jones from CapGemini commented on some text in a Nokia API project on github which indicated that designing and documenting APIs for REST based services was no longer required and that HATEOAS was sufficient. Given Steve's previous comments on IT valuing technology over thought, this was something he needed to call out as bad practice.
When enterprises implement agile ways of working, questions can arise if changes are needed in the way performance appraisals are being done? Several authors have suggestions on how you can use feedback next or as a replacement for existing appraisal processes, to improve the performance of individuals and teams.
For many of us Twitter has become an essential communications utility. Since experiencing scalability problems in 2010, Twitter has moved to a loosely coupled service oriented architecture based on the JVM, allowing it new levels of scalability and feature agility. Twitter engineering recently reported a new record throughput and took time out to describe their new architecture.
The 8th annual State of Agile Development Survey was announced at the Agile 2013 conference. Previous surveys have provided insight into agile adoption. You can participate in the survey, and get the data before it goes public.
"Don't version unless you absolutely must, and it is rare that you absolutely must" says Mike Amundsen in a series of API design workshops he held recently. Amundsen describes the "USE" paradigm for API design focussing on usability, scalability and evolvability. He describes the three most common styles of API implementation and how they compare to these principles.
Many of the presumptions of how slow and resource-demanding "Fat” XML is compared to JSON’s lightweight payload do not hold up to a test David Lee, lead engineer at Marklogic, states after running a "crowd sourcing" experiment with 33 different documents and almost 1200 tests on a multitude of browsers and operating systems.
Earlier this year Ganesh Prasad discussed the concept of thinking of SOA as "Dependency-Oriented Thinking". Based upon further interactions and involvement with real-world use cases, Ganesh has come up with a dozen principles which he believes can help successful SOA.
To stay competitive, enterprises look for ways to do innovation inside their organization. A first step can be to make time available which people can use to think about new products and services and discuss ideas and develop concepts, for instance with a dedicated “full-time” innovation team, by arranging frequent innovation time-slots, or by organizing short and intense innovation workshops.
Node.js has built a user-base and reputation for fast and scalable back-end systems. In a recent edition of the Nodeup podcast, four engineers share their experiences developing APIs using the platform. The conversation covers a range of key concerns including API design, security, testing, documentation, schemas and streaming. But advertising your API as RESTful may not be a good idea.
The principle of “responding to change over following a plan”, is it a strength or a flexibility that can’t work in practice? For example, what about agile projects that had difficulties managing changes and customers who expect too much flexibility? Can agile not live up to its promises, or is it the way that teams and organizations have adopted agile that is causing the problems?
Version 4.0 of NServiceBus, a service bus for .NET, has just been released with support for RabbitMQ and ActiveMQ in addition to MSMQ. Support for using database tables as queues has also been added, and performance for the MSMQ transport has been significantly improved. According to Udi Dahan, the founder of NServiceBus, this is the biggest release ever.
WSO2 has announced App Factory, a PaaS-enabled DevOps platform for the enterprise providing a set of integrating tools for creating, managing and governing applications along with the necessary runtimes to run those applications in the cloud.
Microsoft has detailed their plan for a major reorganization. All OSes will be under one lead. Other engineering areas will be Apps, Cloud and Devices.