Skip to main content

3 key ingredients for success of Agile

For a team to be successful  at using Agile, following three things are key ingredients

  1. Transparency
  2. Inspection
  3. Adaptation

Transparency...

All things within the Scrum team should be open and visible. Every task and story should be visible not only to Scrum team but also to people outside the team. Kanban board is one example which can be used to show the team progress to everyone. Openness should be highly encouraged with the team. Openness gives the team the courage to highlight any potential issues.Another example is a common definition of 'Done' which is accepted by those performing the work and those accepting the working product.

Inspection...

A team should be able to inspect all scrum artefacts to keep a check on what is working and what is not. Inspection should be performed at regular intervals but not so often that it gets in the way of actual work to accomplish the goal. Ideally inspection should be performed by an external inspector. A good example of inspection would be retrospective performed by a Scrum master from another team. You can perform inspection at sprint planning, daily stand up or at sprint reviews.

Adaptation...

Transparency and inspection helps to identify key things that are going well and more often things that are not going well. If things are not working to teams benefit, the scrum team together decide on how to make it better. Often these could be recorded as lessons learnt at sprint retrospective. The lesson learnt log should be reviewed at each sprint retrospective to make sure mistakes are not being repeated. One example could be task being carried forward to next sprints. A lesson learnt would be to finish all the task in one story before stating next story. 

Adapting is the key to success of Agile. Things change and often they are beyond our control. For example, team members leave or are off sick or the business requirement changed because of a change in market condition which is beyond our control. In such cases, the whole team collectively make a decision on how to adapt to this sudden change and keep the focus on delivering business value.

Hope this short article has given you enough ingredients to implement a successful Agile process in your team. Pleas drop a comment if you have any queries or concerns.


Labels:

Comments

Post a Comment

Popular posts from this blog

How to detect HTML5 support for a browser?

HTML5 has introduced lots of new cool  tags . Not all the browsers support all tags and also the implementation of these tags may be different for each browser. HTML5 specification defines the functional aspects of these tags and not the implementation. Also the general concensus is that by 2022 all browsers will support all new features of HTML5. Of all the modern browsers, Chrome seems to have implemented most, if not all, featutes of HTML5. IE9 supports few. Firefox sits in between. So as a developer how do you make use of the cool HTML5 features without causing any compatibility issues with existing browsers? Traditionally developers have used User Agent to detect browser type and use the features accordingly. However these days, you can easily change a User Agent by using addons in your browser. So you need a more robust way to detect the features supported by the browser as the same engine of two different versions of a browser mig...
Post a Comment
Read more

Searching Unicode characters in Oracle table

Oracle implementation of Regular expression has no support for using hexadecimal code to search for Unicode characters. The only way to search for Unicode character is it use the character itself. Normally with Regular expression, you can use \x or \u followed by hexadecimal code to search for any character. E.g. \x20 will match space. But REGEXP_LIKE in Oracle does not support \x. You need to use unistr function to convert the code to equivalent character and then use it with REGEXP_LIKE. E.g. REGEXP_LIKE(source,'[' ||unistr('\0020')|| ']');
Post a Comment
Read more

System.Configuration in .Net Framework 2 onwards

Often application need custom configuration section. System.Configuration namespace includes classes for reading and writing configuration settings. There is a slight difference in how you use this namespace depending on the Framework version you are using Prior to .Net Framework 2.0, the .Net Framework included System.Configuration namespace, but that version of the namespace is now outdated. If you simply add the System.configuration namespace to your project (using in C#), your application references the outdated namespace. To refer to the updated namespace, follow these steps 1. In VS, open the project that requires System.Configuration namespace. 2. Click on the Project menu and then click Add Reference 3. On the .Net tab, Select System.Configuration as shown in following figure, and click OK 4. Now add the System.Configuration namespace to your project normally using Imports (in VB) or using (in C#) and your application will reference the correct version of the namespa...
Post a Comment
Read more