How to keep requirements stable

Everytime, i meet with customer. i feel so happy. This is the first meeting to discuss the requirements. Creating product backlog, creating features, and creating business constraints quites fun. Just imagine, how happy when we get the new project. It means new income, new hope, and new experience. The dream is washed after we in the middle of the projecr. The missing features, the bugs, tha changes from the customer. It drives us crazy when the cost is higher than we expected. The developer team and the product owner conflicts about the requirements. The product owner conflict with the customer about the missing features and business changes.  This article provides you five steps that you can do to limit the changes.  1. Create a mockup before the working solution. You can use mockup to gather feedback from  your customer.  2. Create a regular meeting with customer. weekly meeting with 30 minutes length is fine, 60 minutes is ok. Discuss any progress that you have and any changes that expected by the customer. 3. Create a demonstration session between you and your team. Let's your team demonstrate offered solution and you validate the working product with the mockup 4. Create sprint review with your customer. you demo the solution and get feedback from the customer. Tell them that this solution is based on the feedback in proposed mockup  5. Create documentation workflow to document your meeting, changes, and others artifaces In Azure DevOps you can 1. Use Microsoft Teams to do meeting and demonstration session  2. Use Microsoft Whiteboard to discuss the idea of your product  3. Use Microsoft PowerPoint storyboard to create your low level mockup 4. Use Microsoft Wiki in DevOps to record the meeting notes 5. Use Microsoft Azure Boards to document the user story  6. Use kanban board to understand the changes,      Changes is unavoidable so prepare for the changes happen

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 ( 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 ( 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";

Five Things that you do in Visual Studio 2019 to Improve your codes

Building codes is one of the top missions of any software developer in the world. Improving our codes to improve code readability, maintenance, and performance. Today, we will discuss five things that you can do to improve your code's quality by using Visual Studio. Let's get started   // #1 Code analyzers This is a good feature to understand your codes better. This technique uses FX cop to analyze your codes. You will have a recommendation, code-tips, and comments about your codes based on common coding practices #2 Code Cleanup You can run code cleanup to clean and to eliminate useless codes. You can configure the clean up just like a disk cleanup in windows. Less is more. #3 Live share Need a code monkey or support from the expert pals. You can get in touch with them by using Live Share. Live share is a code-sharing feature by using live streaming protocol. You can collaborate with more than five persons to build codes on the same pages. The editing process will be live just like document editing in Office 365. Just give them a link, and you are ready to go #4 Refactoring Refactoring comes with quick action features that allow you to improve the codes through a contextual recommendation. Just hover your codes and choose quick actions and refactoring, you will amaze how refactor process can help you to compose efficient codes. #5 Say no to Copy and Paste Codes Visual Studio has a code clones features to help you identify the repetitive codes. You can run the code clones, and the Visual Studio will help you identify the replicated codes and how to manage it. Pro Tips: Run the code clones, and then refactoring will make you. That's it five tips to manage your codes easily by using Visual Studio 2019, have other tips to improve your codes? Just put in the comment, and I will add it to the list. Enjoy your weekend //

Converting Business Process to User Story

As an Agile developer, you might need to convert your business process to user story. The hard part is to make sure that the user story doesn't eliminate or reduce the clarification of software requirements. On this article, we want to share about five steps to convert your business process to user story. In order to reproduce this tips, we encourage you to register into and understand the DevOps Board. So let's get started // Step 1. Identifying roles / actor This is an easy step; you should convert the swim lane in business process modelling notation / flowchart into a actor or roles. You should identify the relation between one actor with the other. For example, member actor is a registered user who pay the subscription bill. Or admin is a registered user who promoted by another admin. Step 2. Converting the block diagram into action Each block can be converted into a user story action. For example, the order entry can be an action for sales. The credit criteria validation is an action for Management. The action phrase can be used as a title of your backlogs. Step 3. Creating user story phrases Remember the class? You can use this formula to create user story As an (actor) I want to (action) so that (outcome) For example, as a member I want to view unlimited learning videos so that I gain XP (eXperience Point) and knowledge. You can put the title into Boards Step 4. Managing Epic, Features, and Story / Backlog You can start your user story as a baseline of your user requirements. Here is the rule of thumbs: Mission can be an Epic for a software Capability can be features One feature will have one – many user story Our recommendation is start with the user story or features. You can add it into your Azure DevOps. Step 5. Add the Usage Scenario in User Story Description If the business process should be clarified, you can add the detail of business process in the description of the user story. In Azure DevOps you can put business rules and the other process in the description That's it steps to convert the business process to a user story. Happy weekend //

5 Things that you might be forget in Azure DevOps

One DevOps solution that can be used for free and is easy to use is; ah Azure DevOps. Azure DevOps has many features for teams that want to deliver solutions quickly and sustainably. In this article we will discuss five things that you might forget when using Azure DevOps. #1 You Can Import Your Github Repos to Azure DevOps You have a project that has been saved on Github. And you have the desire to continue on Azure DevOps? The good news is that Azure DevOps supports imports from Github. The thing to do is quite simple, just choose import from repository and all your code will be copied. For more details, please refer to the following link  // #2 Converting your private project into public  You have a personal project and want to share it as an open source project. So Azure Devops supports the process of changing projects from private to public and vice versa. Just follow the steps below and you can share the spirit of open source with the world #3 Choosing the Software Method Maybe you are accustomed to using Scrum, but did you know that Azure DevOps has various Agile or formal methods support. You can choose basic, CMMI, agile, and Scrum. When choosing a different process, the terminology, approach, and also Boards will change. Intrigued by the difference please see the following link #4 Managing Requirements Better  Azure DevOps especially Azure Board has a solution to manage software requirements. Azure DevOps can manage work items, sprints, and test cases. Check out the various software at Azure DevOps that can help you here #5 Productive with Queries  When we finish a project. Bugs, work items, and tasks need to be searched and traced quickly. Some use the default search engine, some scroll from one page to another. Did you know if there is a repeat search approach with queries. Check out how to do the following link //

Beginner Guide for Azure Artifacts

You have three teams. The team has a new project called Hotel Technology. Hotel Technology provides end to end solution for room reservation and guest management. You create two main system the first one is web app (team A) and the second one is a windows app (Team B). Both developed with .NET Standard. The problem is two apps need one custom package namely Hotel Backend package. Hotel Backend Package is a custom package that updated by another teams (Team C). The question is how to make sure that the Team A and Team B always obtain the latest version of the Team C custom package. This kind scenario can be helped by the Azure Artifacts. medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; Azure Artifacts is a new kid on the block that help teams to maintain a development package that can be used across the team. Imagine the concept of custom dependency for a project. Azure Artifacts helps you to manage the package. Let's get started how we do that. Creating new feeds Registering feed to Package Manager Configuring the Builds Pipeline Obtain the feed artifacts Creating new feeds On this scenario, team c creates a feed. Feed is endpoint that broadcasted the custom package. In the Azure artifact, you can create new feed easily. The feed will be broadcasted as an URL that can be consumed through Visual Studio or another system. Feed works like NuGet Registering feed to Package Manager After creating a feed, you will obtain unique URL that can be registered in Visual Studio. This can be done by visiting NuGet package manager and add the package sources. Configuring the build pipeline The registered feed can be pushed by the Azure Pipeline. With NuGet Push, we can push the result of the build to the feed. Obtain the feed The feed can be obtained by refreshing the feed in visual studio or Azure artifacts page That's it, enjoy the artifacts and package management medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

Beginner Guide for Azure Test Plan

Hi Folks, we continue with our journey in Azure DevOps. Today, we will discuss the Azure Test Plan. Testing is a big deal in the software development process. The quality of the software comes from quality Azure Test Plan. This article will cover beginner guide for Azure Test Plan. In order to make it simple, we will separate some of technical detail in another post. So lets get started. Before we start In order to do Azure test plan, you should have Up and Running Azure DevOps. This service is free of charge. You can register to Kanban Board is ready. You should already setup your Azure Boards. You can see the beginner tutorial of Azure Board here If you want do a Load Test, having Azure Subscription is great, you can get in Beginner Guide Scenario On this guide, we will create a test plan, a test case. We will discuss load test in the next guide. medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; Step by Step Scenario Create a test plan. We will start creating a test plan. A test plan is a collection of a test case. It can be related with features or iteration. In this case, we will create a test plan based on iteration. We create a test plan in Sprint 1. Create a test case Test case is a set condition based on use case or user story to make sure the software satisfy the requirements. Test case is grouped into a test plan. In the test plan, we can create a test plan You should relate a test case into a use case or a user story. You can do that by add the link the user story as shown on the picture The most important things in a test case is step by step of the user action. Run a test case You can run a test case for web or desktop. Unfortunately, there is no option to run the test for mobile application For this example, we click run for web application. Your browser will create a pop up. You can do use acceptance testing by opening the web and then click based on the scenario You can click the checklist button if test is passed. Otherwise, you can click the cross button if failed test step. On this example, we have failed test in step 4. In this step you can fill the comment section Beside comment you can put the attachment and create bug. On this example, lets create a bug. The repro step is created, we just need to add the bug name, put the severity, add the effort estimation. Managing the Bugs The bugs will be stored in Azure Boards, and the test result will be on failure state. We can restart the test or edit test the case when necessary Conclusion On this step, we setup a test plan, create a test case, run a test, create a bug. In the next section will discuss automated testing. See you medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

Beginner Guide for Azure Repos

Repository (a.k.a Repos) is the core of source code storage. Today, I want to show you how to choose and to manage your source codes in Azure Repos. The need of Repository Repository helps you to store the codes and collaborates with the others. There are two types of modern repository. The first type is centralized, the second type is distributed. SVN (Source Code Versioning), TFVC (Team Foundation Version Control), and Subversion were the examples of centralized repository. The GitHub and Bitbucket are the examples of distributed repository. When choosing between centralized and distributed is a matter of the need and commonality. For example, GitHub was popular in open source community while the TFVC was commonly used for private or inhouse software development. Regardless with the repository model, we can use the Azure Repos for this kind purpose. Beginner Guide On this post, I will show you how to initialize, to operate, and to maintain the codes repository. We assume that you already has the Azure DevOps account , medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; Step by Step Guide Activating the Public Projects Choosing the repository Model Initializing the repository Opening the repository in Visual Studio #1 Activating the GIT support Visit the, login with your account and we ready to do an action. By the default, Azure DevOps doesn't allow you to create public project. It means you can use Azure DevOps to share your open source project. This step will activate the public project for your source codes. Just visit the policies setting and set to On. You will have confirmation to activate the public project. NOTE: never do this if you just want to share the project to the others member. This action will make your codes exposed to the public. #2 Choosing the Repository Model You can choose between GIT or TFVC. This action is not reversible. Once you already select the TFVC you can't convert to the GIT, vice versa. Choosing repository model can be done when you create a new project. Microsoft recommends the GIT. My recommendation is stick with your productivity by choosing the easiest one according yourself. #3 Initializing the repository There is no extra step to initialize the repository. On TFVC, you will see that you can download as zip and upload files. You can see the changes history in changesets. You can do selected pending based on Shelvesets On GIT, you will see a lot of option. You will see commits log, pushes activity, branches that you have, tags identification and pull request. It is quite powerful and complex. I recommend you to visit #4 Configuring the codes in Visual Studio When you open the visual studio 2019. You can select the first option namely Clone or Check out code. After that you just need to enter the URL or browse repository. You can login first with the Azure DevOps Account. By default, your visual studio will configure itself as GIT provider. You can change the behavior in Tools – Option – Source Control. However, the default source control will be ignored if you open the existing project that already have source control. After that you can do commit, push, and many others action based on your selected repos.   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.


Month List