Agile roles

There are a number of different roles in the agile methodology, and these need to be well-understood to make agile work effectively in your organisation. In particular, the scrum master and product owner need to have enough time to devote to doing their roles properly.

Agile artefacts

For agile methodologies to succeed, there needs to be maximum transparency and planning. A number of agile artefacts have been developed to ensure that the team and the stakeholders have a clear understanding of what's happening.

Agile methodology in the wild

Agile methodologies like Scrum sound amazingly efficient when presented by people who have implemented them in a non-hostile environment. But conditions are not always perfect, and things can sometimes go wrong.

One of the key features of agile project methodologies is that they have different types of meetings. Each different type of meeting has a very specific function. They can become tedious and unproductive if they deviate from the prescribed form and function. With that in mind, let's look at the different types of meeting, how they are meant to work, and what can go wrong.

Getting agile to work for you

Different project management tools will work for different types of work and different scales of organisation. Depending on the context, your project may work better with agile, lean, scrum, kanban, or some hybrid approach.

Upload a PDF and link to it from your blog

Sometimes you need to upload a printable document, such as a flyer, a newsletter, or an information sheet to your blog or website.

The Blogger tool (unlike Google Sites) doesn't have the facility to attach documents.

Fortunately, you can create a public folder for documents on Google Drive, and link to it from your blog.

Here is a step-by-step guide to how to do that.

jQuery style switcher

It's often the case that you want to provide more than one CSS stylesheet for your app or website. You can do this by including a style switching function in your app. Here's how to do it in jQuery.

Angular promises

I have been struggling to understand Angular promises for months, and I finally found an answer on Stack Overflow that explains them really well. There's also this really helpful cartoon which has a nice story explaining the fetching of data. However, the Stack Overflow answer was what really did it for me, and fully deserves its current status of 383 upvotes.

The problem

The problem that promises set out to solve is that when you make asynchronous calls to a server where the results of one call are dependent on another call, you need to return the results in the order of your dependencies, not in the random order that will happen depending on which server call returns its results first.