DEV Community: Agnes Reina

My understanding of the Scrum Framework and Benefits Of the Scrum Events

Agnes Reina — Fri, 21 Feb 2020 09:03:51 +0000

Scrum is a framework for Agile software development by which people use to address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

It is most frequently used by software development teams to work together, but it is used for complex product development in general.

In the research done by Hirotaka Takeuchi and Ikujiro Nonaka showed that a team can do great work when it is small and self-organized in a unit of people and has all objectives.

Scrum roles

Product owner

the product owner is the person who owns the product backlog and writes user stories and acceptance criteria and tells the development team what is important to deliver. His main responsibility is to prioritize the Product Backlog and decide the release date and the content.

Scrum master

The scrum master is a dedicated individual responsible for improving the performance of the Team and the business by any means necessary.

In practical terms, it means that he/she helps the product owner to better understand and communicate value, to manage the backlog, and plan the work with the team and break down that work to deliver the most effective learning.

Development team

A Development Team is a dedicated collection of self-organizing, individuals representing different functional roles with all the necessary skills working together to develop and deliver the requested and committed product increments, and they build the product that the Product Owner indicates.

Scrum Events

Scrum defines four events that occur inside each Sprint. A sprint is a set period of time during which specific work has to be completed and made ready for review.

Sprint Planning

During Sprint Planning, the entire Scrum Team(the development team, product owner, and ScrumMaster) collaborates and discusses the desired high-priority work for the Sprint and defines the Sprint Goal.

The Scrum Master’s role is primarily to facilitate the meeting. The Product Owner describes the objective of the Sprint and also answers questions from the Development Team about execution and acceptance criteria.

Daily Scrum Meeting

The Daily Scrum Meeting is a 15-minute meeting for the Team, conducted daily to quickly understand the work since the last Daily Scrum Meeting and create a plan for the next 24 hours. This meeting is also referred to as the Daily Standup Meeting.

During the meeting, each Team member explains :
What did he/she do yesterday that helped the Team meet the Sprint Goal?
What is he/she going to do today to help the Team meet the Sprint Goal?
Does he/she see any blocker that prevents him/her or the Team from meeting the Sprint Goal?

Sprint Review

A Sprint Review is held at the end of every Sprint. During the Sprint Review, a presentation of the increment that is getting released is reviewed.

In this meeting, the Scrum Team and the stakeholders collaborate to understand what was done in the Sprint. They adapt the Product Backlog as needed based on this feedback. The Sprint Review is normally held for two hours for two-week sprints and for four hours for one-month sprints.

Sprint Retrospective

The purpose of the Sprint Retrospective is to :
Combine the learnings from the last Sprint, with regards to people, relationships, process, and tools.
Identify the major items that went well and potential improvements.
Creation of a plan for implementing improvements to increase product quality.

During a sprint retrospective, the Scrum Team discusses what went right and areas for improvement in the Sprint. They make tangible plans for how to improve their own process, tools, and relationships.
The Difference between Sprint Reviews & Sprint Retrospectives is that Sprint reviews focus on the product and Sprint Retrospectives focus on the process.

Benefits Of the Scrum Events

Quicker release of the useable product to users and customers
Higher quality
Higher productivity
Greater ability to apply changes as they occur
Courage to work on tough problems during the Sprint
Better user satisfaction

My experience with Test Driven Development (TDD) and how to implement it in a project

Agnes Reina — Sat, 15 Feb 2020 11:53:40 +0000

Introduction

Test-driven development (TDD) is a development technique where you first have to write a test that fails before writing a passing code. It relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the code is improved so that the tests pass.

“For my first-time using TDD, I asked myself why should we write code to test other code that we don’t even have.`”

TDD starts with designing and developing tests for every small functionality of an application. It ensures that the source code is thoroughly unit tested and leads to modularized, flexible and extensible code. It focuses on writing only the code necessary to pass tests, making the design simple and clear.

Activities involved in Test-Driven Development (TDD)

1. Coding

The first activity that you do in TDD is to write a unit test case which is a single test that describes a feature of a program. To write a test, the developer must clearly understand the feature's specification and requirements. The developer can accomplish this through use cases and user stories to cover the requirements and exception conditions.

2. Testing

Run the test and see if all test cases now pass, the programmer can be confident that the new code meets the test requirements, and does not break or degrade any existing features. If they do not, the new code must be adjusted until they do. And then you write the simplest code possible to make the test pass.

3. Refactoring

Refactoring is an activity where you make the code efficient. You do not change the functionality, but rather alter the internal dynamics to enhance the performance. Some examples include identifying and removing duplicate and dead pieces of code, simplifying nested classes.

The benefit of using TDD

With TDD you get fewer bugs in code because you have tested out the main features. The other thing is the focus, what I am trying to say here is that your focus is narrowed to making the test passes. The third benefit of using TDD is that test act as documentation if you don’t know what a bit of code do you can read it and see what it does.

Conclusion

In test-driven development (TDD), a test is written first before writing the functional code. This doesn’t mean that TDD can replace traditional QA, but instead, it ensures effective unit testing. An effective unit test will ensure better code coverage.

My experience with Test Driven Development (TDD) and how to implement it in a project

Agnes Reina — Sat, 15 Feb 2020 11:41:53 +0000

Introduction

“For my first-time using TDD, I asked myself why should we write code to test other code that we don’t even have.`”

Activities involved in Test-Driven Development (TDD)

1. Coding

2. Testing

3. Refactoring

The benefit of using TDD

Conclusion

My experience with Test Driven Development (TDD) and how to implement it in a project

Agnes Reina — Sat, 15 Feb 2020 11:30:25 +0000

“For my first-time using TDD, I asked myself why should we write code to test other code that we don’t even have.`”

Activities involved in Test-Driven Development (TDD)

Coding

Testing

Refactoring

The benefit of using TDD

Conclusion

My experience with Test Driven Development (TDD) and how to implement it in a project

Agnes Reina — Sat, 15 Feb 2020 11:11:31 +0000