Skip to main content

Are there any standards (Best practices) in Agile/scrum world? How important are they?

Standards help the people to work and communicate  in time tested manner. This helps to reduce the noise and chaos. Standards help  a newbie to learn the tips and tricks of trade.

But is it advisable to follow the standards always?

Change is the only  thing which is constant. Any standard or best practice which doesn't evolve with the changing environment doesn't help anyone. Such obsolete standards prevents the team from improving continuously. In many cases thy prevent new thinking and innovation.

A standard/ guideline made for one company/project/person may not work for another because they have unique requirement.  These guidelines will have to reviewed and adopted to the new project/person. Like everything ins scrum, even the standards will have to undergo the process of continuous improvement.

Some Thoughts 

  • It is advisable to put the good practices on the team wall so that everyone can view them. Any standard hidden in some SharePoint site or any other repository might not get enough views. If these are pasted on common areas team will get to see them every day and can suggest  any improvement.
  • If any automation can be made to verify the output against the standards then the necessary investment should be made .

Improvement process

  • Team identifies a problem and the necessary process/standard changes 
  • Team discusses the new process & make the necessary changes. Team publishes the process change within the team and stakeholders
  • After a specified duration team revisits the standards to check the effectiveness  
  • If the process/standard change has achieved the necessary outcome then it is circulated as a best practice guideline to other teams also. 


Popular posts from this blog

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation. In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can up

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices. Some of the rules  The roles of Scrum • Scrum Master - • Product Owner • Feature Team The PDCA cycle (  )  frequent communication about risks (daily) • Plan – Sprint planning • Do – Actual engineering sprint – deliver a potential shippable code • Check – Sprint review • Act – Retrospective  The scrum guide @ will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum. Apart from these rest of

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I