Quality Assurance of DevOps Project

When we discuss about the quality of software, we discuss about how we can deliver less bugs software and correct. This can be done by having a dedicated members that focusing in quality of a software. It can be software tester, quality assurance engineer, or software development engineering test. This article will discuss what we need to do when we have a DevOps project and need to make sure the quality of the outcome. Failure Reason Let's we ask ourselves, why the result of our DevOps project / Software Engineering project goes wrong? Incorrect requirements Team issues (productivity, miscommunication, mis-coordination) Untested software (have no time to test) Radical changes in software (unstable requirements) Wrong architectural design (wrong technology, wrong design, wrong approaches) medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; What we need to do So how we can make sure the result of the DevOps project is sufficient. And the failure risk can be reduced by the QA role. Failure riskQA ActionTask on DevOpsIncorrect requirements Validate the user stories with the customerCheck the actor or roles. Check the feature Check the user story Team Issues Doing weekly QA based on the outcome/ deliverable Learning the demonstration from the developer teamsCheck the deliverable and commitment of the teams in Kanban board Check the status of the story closed when it is tested Untested SoftwareRetested by doing daily QA with development team Retested by doing weekly QA with the customerPut bugs and additional tasks to developer team Creating test plan, test case, and test suite Creating manual based on test resultRadical Changes in software Creating meeting notes for bugs Creating notes for changes Put bugs and monitor the progress Validates the changes, if changes is approved Wrong architectural designDiscussing the information architecture issues with the development teams Discussing the solution architecture with the development teamsCreating tasks that related with architecture changes. medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

what should i do in daily sprint?

Daily scrum or daily standup is a way to communicate between team members to understand the heart beat of the project. Daily scrum duration can be 5 minutes to 30 minutes. If you have daily scrum meeting more than 30 minutes, it means you should create another technical discussion informally. The question is, what should i do in daily scrum. Daily Scrum Agenda The product owner or development teams open the daily scrum  The development team share updates from the previous day  The development team share the challange or question related with the product  The development team share what they will do in today  medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; Sprint Review The development team tests the software The development teams provide feedbacks based on the specification The development teams will revise based on the feedback The development teams will send the result to the customer The product owner will collaboate with the customer to do demo session The customer will give a feedback in demo session The product owner will note the feedback  The development team will accept / postpone the feedback  The product owner will send the updated sprint plan The customer approves / rejects the sprint plan Sprint Restropectives  Development team discusses what should improve in the next iteration  development team discusses what went well in the last iteration the team will commit the next iteration  medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

The Simplicity in User Manual

User manual is still needed. However, it should as simple as possible. The real question is, what the content of user manual that can be as simple as possible and provide simplicity guide for the user. This article will guide it for you. If you are Scrum or XP user, this agile user manual is for you. This is the improvement of my previous post Creating Agile User Manual (ridilabs.net) What you Put in Your Manual Technically not everything on the DevOps work item. You can put the essential information such as Product vision, mission, and success criteria Product version and history Product actor. Who will use the product? Product feature. List of features Product user story Product guide how to use the user story. User story limitation and rules medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

Implement Scrum Product Backlog on Azure Boards

On this article, we will discuss how to implement product backlog on azure boards. It assumed that you already have the feature list. Product backlog is an ordered list for anything that need to build product. Some people said that product backlog is the user story. Yes, it is! But product backlog already has priority and order. This product backlog shall be prepared by the product owner. The product owner can be assigned with the basic license or stakeholder license for the Azure Boards. Backlog hierarchy (docs.microsoft.com) medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; Requirements Before we go to the product backlog implementation on Azure Boards you should have: Product owner can access the Azure Boards. The good news is the Stakeholder license in Azure DevOps is free of charge! Product owner already discussed the priority of the product backlog with the customer Product owner already estimated the business value of the product backlog Product owner already have portfolio backlog What we should do On this step, we will do several tasks: Creating the product backlog. It includes the description and acceptance. It will follow the use story format. If you don't know the user story format you can visit this video Relating the product backlog with the feature Giving priority, business value, and value area Let's get started On this video, I will show you how create, relate, and giving priority of the backlog What's next After this step, we can estimate the effort and assigning into the sprint. medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

Global eXtreme Programming, ALM, and Visual Studio 2010

Software engineering is independent. It’s not related with a specific tools. It can be applied in any tools whether Visual Studio, Eclipse, Net Bean, or anything. However, selecting a correct tool and correct method will boost your team productivity. Microsoft Visual Studio 2010 has a good relationship worth Scrum method. As I mentioned in this post, Scrum has good advantages in integration. However, if you are using XP or Global XP. I created an Indonesian article how to use GXP in Visual Studio ALM. The article is based on our experience in building a project in distributed model. Adopting Global eXtreme Programming in Visual Studio ALM If you are still in the middle of nowhere. Here are the rule of thumbs what Agile method that suitable for your project Scrum is great for middle to enterprise project that has planning driven development. Global eXtreme Programming  is a great stuff  for small to medium project when we thinks entirely in code quality and distributed productivity. How about ICONIX? or RUP?. Well we will discuss it in another post. @ridife

Scrum as a Simple Software Method

Adopting scrum is just like adopting any agile method such as extreme Programming or ICONIX. However, Scrum lays out the playing field and rules for the game. the software construction is a game for Scrum. Scrum adoption has two aspects. First, Scrum is rolled out. a mentor teach a team how to play the game of product development using Scrum, the second aspect is do the SCRUM itself including your team and client. A good guide about scrum can be downloaded here 15 pages of Scrum Guide Schwaber (2007) in his book called Enterprise and Scrum already have 1,2,3 rules to adopt Scrum. Creating backlog, a simple user story model Iteration activity as a heart of the Scrum And working software that increment the functionality The rules is done by three roles the Product Owner, the team, and the Scrum Master. All management responsibilities in a project are divided between these three roles. The Scrum Master is responsible for the Scrum process, for teaching it to everyone involved in the project, for implementing it so that it fits within an organization's culture and still delivers the expected benefits, and for ensuring that everyone follows its rules and practices. The Scrum process is simple and mostly focused how team collaborate effectively using daily plan and appropriate tools. You can learn and develop a software with fun using this method. For further knowledge I recommend you to buy book about Scrum medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

Topics Highlights

About @ridife

This blog will be dedicated to integrate a knowledge between academic and industry need in the Software Engineering, DevOps, Cloud Computing and Microsoft 365 platform. Enjoy this blog and let's get in touch in any social media.

Xbox

Month List

Visitor