Agile/Scrum blog

Continuous Delivery – Patterns for zero downtime requirements (ARR setup)

Door: Prajeesh Prathap,  17-08-2014
Onderwerp: Continuous delivery  CD  zero downtime deployment  agile  architecture  

Microsoft Application Request Routing (ARR) is a proxy-based routing module that forwards HTTP requests to application servers based on HTTP headers, server variables, and load balance algorithms. With ARR you can increase application availability and scalability by better utilization of content server resources with lower management cost by creating opportunities for shared hosting environments.

Agile Transition Bingo

Stephan van Rooden Door: Stephan van Rooden,  15-08-2014
Onderwerp: agile  Agile Coaches  CD  agilegames  

A few weeks ago at Prowareness HQ in Delft we had a very interesting discussion on how to add more fun to your work. Especially the things that are hard to do or are actually no fun to do at all. Very soon we were talking about gamification which is the use of game thinking and game mechanics in non-game contexts. And this triggered me to add some fun to a very large and important transition we are working on at one of our partners.

An Agile mindset in a marketing company

Dave Woertman Door: Dave Woertman,  01-08-2014
Onderwerp: Scrum in Sales en Marketing  Agile Principles  

When we talk about Agile, we mostly talk about companies that deliver IT products to real customers. We tell these companies to keep on focusing on the products and tell them to gather feedback from real customers by delivering the product faster. But what if you don’t have a product-oriented company? What if you do not have direct customer contact? What if you are running a company that creates creative products as part of a marketing campaign, together with other companies? Which Agile techniques can you use in a marketing company, and which techniques can’t you use? An overview …..

User Acceptance Test in Scrum

Remko Vroomans Door: Remko Vroomans,  28-07-2014
Onderwerp: Testing  

Many teams making the transition from traditional waterfall projects to Scrum are struggling to fit the tollgates they previously had to pass into their work process. Although the testing tollgates, like systems tests and functional tests  seem to fit fine within a sprint, when it comes to User Acceptance Testing, something feels not quite right. When do all the parties, all the departments or all the users officially test the product and accept or refuse it? Before I try to answer that question, a quick reminder of what User Acceptance Testing actually is.