January 2, 2017Windows Azure,IoT
A couple of weeks ago, I had the privilege of doing a live broadcast on Microsoft’s Channel 9 Developer Network. In the broadcast, I discussed various uses for the Internet of Things (IoT) across different industries. In particular, I followed an original story line from the previous couple of broadcasts that involved using BI for retail establishments to gather sales and marketing insights for driving revenue.
I’ve taken that story to the next level in examining some ways we can use IoT for predicting sales and being more proactive in marketing initiatives by monitoring human behavior. If you’re interested, check out the video.
August 31, 2016Microsoft Office
It seems that when Microsoft deployed their latest versions of Office, they forgot to adjust the DPI (dots per inch) settings for PowerPoint rendering the menus on second monitors extremely large. With the menu and its fonts so large, the design space on a secondary monitor is very limited, if not useless altogether.
August 9, 2016Windows Azure
Last week Microsoft just released Azure VNet peering – a highly-requested and long-awaited internetworking feature – into public preview. VNet peering provides the ability to join two VNet’s, or virtual networks, in the same region using Microsoft’s Azure backbone network. Because of this functionality, all resources appear to be on the same network as compared to being on two separate networks that are simply connected. VNet peering is just another giant step in making Microsoft Azure a game-changer for hybrid networks.
February 27, 2016ALM,Agile,Quality Assurance
The scatter diagram, or scatter plot, is a type of mathematical diagram of XY coordinates used to display values for a set of data. Typically, one value is under control while the other varies based on our control. For a quality assurance example, our control may be the number of features, while the variable is the number of bugs. The data for a scatter diagram is based over time or experience.
A Pareto Chart allows you to quickly identify the problem areas of your application by reporting those areas that have the greatest number of issues. The philosophy of the Pareto Chart is based on the 80/20 rule – by identifying and fixing the larger areas first, the application can be stabilized a lot quicker. Or, more specifically, correcting 20% of the currently known bugs will stabilize 80% of the application.
February 26, 2016ALM,Agile,Quality Assurance
A histogram is a very simple diagram and doesn’t take much time to create. It illustrates a data point in history in order to calculate the probability of something happening in the future. In general, if we notice a trend of a event or action happening in a specific period, we can plan for the same event or action in the future, given the same circumstances.
Control charts are used for statistical analysis to determine if a process is in a stable state of control. Control charts are very similar to run charts, except that control charts have additional lines for upper and lower control limits. Control charts help us to determine the effectiveness of our quality control over time and view irregularities in order to improve our control quality.
A stratification diagram, also known as a flowchart or run chart, is used to determine the relationship between two or more sets of data. Stratification diagrams are helpful for making patterns visible when data is coming from a wide variety of sources. These patterns can be compared to the various systems under test so that we can, once again, adjust our processes in order to improve quality.
The check sheet is, by far, the easiest report to produce. The only thing required is an Excel-type application for columns and rows. The header should be a fact for the dimension you are tracking. This fact is usually something like a day of the week, week of the month or another time-based milestone, but it doesn’t have to be. The row dimensions are the defect types you are tracking. So, as an example, let’s say we are tracking defects on a web application that’s under development.
February 23, 2016ALM,Agile,Quality Assurance
The Ishikawa, or Fishbone, diagram (or, affectionately known as the “Fishikawa” diagram), is one of the easiest diagrams to create. No special software is needed, per se. The content for the Ishikawa diagram is constructed using The 5 Why’s as discussed in the previous post. The answer to each question can be classified under one of six outside factors which makes up a bone from the fish’s scale.
Subscribe to receive new posts in your inbox.