English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Today all organizations are required to achieve process compliance, be it ISO 9000, Six Sigma, CMM, Sarbanes-Oxley, Balanced Score Cards etc. Each of these compliance activities seeks to ensure that the company has the appropriate processes in place to ensure that the company can serve the needs of their customers and shareholders. Most mandate some form of continuous improvement measurement, dare I say metrics, so that the organization can monitor its improvement. Many of these efforts were originally targeted at improving manufacturing, operations or finance, but they are having an increasing impact on the IT and SE. Also, while these efforts were initially applied to larger companies, they have trickled down to the smaller ones who supply these larger firms. Having a documented process has therefore become a mandatory requirement for software development. It isn't sufficient to say " we are doing Waterfall, Iterative or Agile; go away and let us get our work done ". Like it or not, everyone needs to be able to articulate the process they use for software development. It is time for developers to take ownership of the process side of things so that they can stop fighting it. Process is like democracy: if you don't participate, you get the process you deserve. However, there is no need for process tension to obstruct productive development! Ask any software developer and they will tell you if they feel they are working in a good software culture, and most who answer no will say that they would like to be. However, ask most developers how they feel about their company's software process and they will complain bitterly. Yet the best software cultures always have very disciplined processes which developers follow almost to a fault. Indeed the culture is defined by a unique combination of people and process. The open source Apache foundation is an example of

The Unnecessary Tension between Process and Programmer Some of My Best Friends Use an Agile Software Process.