Monday, 11 January 2016

Roles of Scrum Developers in Scrum Project

Scrum developers, also referred to as the development team or Scrum team, are responsible for developing the product and they possess all the essential skills required to carry out the work of the project. They have a high level of collaboration to maximize productivity, so that minimal coordination is required to get things done. To minimize dependency, team members are experts in chosen domain, but also possess basic knowledge and skills about other domains.
Some of the key responsibilities of Scrum developers which they are required to fulfill in any Scrum project are:
  1. Provides inputs for creation of the Collaboration Plan and the Team Building Plan
  2. Ensures a clear understanding of Epic(s) and Personas
  3. Understands the User Stories in the Prioritized Product Backlog
  4. Agrees with other Scrum Core Team members on the Length of Sprint
  5. Seeks clarification on new products or changes in the existing products, if any, in the refined Prioritized Product Backlog
  6. Provides inputs to the Product Owner on creation of User Stories
  7. Estimates User Stories approved by the Product Owner
  8. Commit User Stories to be done in a Sprint
  9. Develops Task List based on agreed User Stories and dependencies
  10. Estimates effort for tasks identified and if necessary, updates the Task List
  11. Develops the Sprint Backlog and the Sprint Burndown Chart
  12. Creates Deliverables
  13. Identifies risks and implements risk mitigation actions, if any
  14. Updates Impediment Log and dependencies
  15. Updates Burndown Chart, Scrumboard, and Impediment Log
  16. Discusses issues faced by individual members and seeks solutions to motivate the team
  17. Identifies risks, if any
  18. Submits Change Requests, if required
  19. Participates in Prioritized Product Backlog Review Meetings
  20. Provides inputs to Scrum Master for Scrum of Scrums Meetings
  21. Demonstrates completed deliverables to the Product Owner for approval
  22. Identifies improvement opportunities, if any, from the current Sprint and agrees on any actionable improvements for the next Sprint
  23. Participates in the Retrospect Project Meeting

Wednesday, 6 January 2016

Scrum Fundamentals

There are lot many ways to develop or code software. Easiest is the one in which no documentation, design or testing is involved. Others describe on how to improve coding, testing etc.

All developers claim that software delivered is better by their method and also is faster with less effort. It sounds really good but everything should have a proof when it comes to software. Although, Agile methods are not at the peak but its growing and getting very popular every day.

However, it’s difficult to prove on whose method of software development is better as there is no scientific uniform data to compare or methodologies like Agile or Scrum. All the projects depend on the skills and knowledge of the people involved in it, domain used, choices made at every stage, process method. This comparison is more like comparing cars to trucks where anyone can easily say: that is not a real car and this neither a truck.

We all know that every project of software is different n by its nature software development is exclusive. It is fundamentally true. There are people who still try to differentiate the effectiveness of methods of software development. It has been proved that there are several different methods and most of them were significant in specific situations.

Also, people promote the methods of software development, which many say is nothing but a way of earning more money by many consultants. Small companies of trainers and consultants get created easily with the help of the certifications and eventually they get busy training the delegates of big companies. It’s always better to take the help when needed moreover nothing wrong in it as it might act as the help you were actually looking out to give the final touch to the project.

Agile is very well known and popular as it give u many best practices, focuses on the job to be done, though we should accept it that it doesn’t happen every time. As far as Scrum is considered, a well-judged product owner’s presence will prove it to be the faster and effective than waterfall approach.

Acknowledgement: The content is borrowed from (original blog url: