Splitting user stories – Why, When, How

Feb 1 13:33:48 by mozaicworks.com

One of the dangers of writing user stories is that they can get pretty big if there’s no one on the team to point it out. The scope of a user story becomes broader than it should be. In the following article, I’m going to walk you through the reasons why you should aim for... Read moreThe post Splitting user stories – Why, When, How appeared first on Mozaic Works.

#1   49%      4
Microsoft's plan to bridge its infrastructure and platform cloud services is unfolding

Feb 14 16:47:00 by www.zdnet.com

Microsoft is bringing more of its Azure PaaS capabilities to its IaaS customers this year. First up: Support for larger VM Scale Sets and Managed Disks.

#2   97%      6
Google pushes ahead to make its cloud better for Windows enterprise users

Feb 2 15:04:00 by www.zdnet.com

Google is looking to attract Microsoft enterprise customers with new beta versions of images for SQL Server Enterprise and Windows Server Core for Google Compute Engine.

#3   92%      2
Angular and React: Brief Comparison Based on a 2-Year Long Experience

Jan 25 8:01:00 by dzone.com

During the last two+ years, our team at DashBouquet Development has worked on great variety of projects, including the ones on Angular, Angular 2, and React. Almost all of them have gone to production. Modern front-end development assumes the use of enormous libraries, like AngularJS (true for both Angular 1 and 2), React, and many others. Each has its pros and cons and you would never be able to tell which one is better unless you use them both. Here, we'd like to share our experience, which is based on the past 3-year practice in front-end development. Because at DashBouquet we mostly use Angular and React, we will have a look at these two frameworks.

#4   103%      8
5 Reasons to Estimate Agile Development with Story Points

Jan 31 13:25:00 by blogs.starcio.com

#5   169%      6
Microsoft plugs continuous delivery into Visual Studio, Azure

Feb 8 11:00:00 by www.infoworld.com

Microsoft is adding continuous delivery capabilities to its Visual Studio 2017 IDE. The Continuous Delivery Tools for Visual Studio extension, announced this week, lets developers set up an automated build, test, and release pipeline on the Visual Studio Team Services cloud ALM platform. It works with ASP.Net 4 and ASP.Net Core applications targeting the Azure App Services and Azure Container Services. Developers can monitor their pipeline with notifications in the IDE that alert them of any build failures in a continuous integration run.To read this article in full or to leave a comment, please click here

#6   171%      4
Of Gods and Procrastination: Agile Management

Feb 8 17:01:00 by dzone.com

The year was 2001. A new methodology appeared in a still young, yet maturing industry of software development. It came with the Agile Manifesto. The new way, the Agile management way, came to break the old, strict, narrow and deep hierarchy in which the developer was way too far from the software’s user. Quickly embraced by some, completely ignored by others, Agile management spent the last decade and a half gaining popularity. Today it has become one of the most trendy phenomena, and most companies claim to have adapted and applied its principles. And indeed, that is true, yet almost always in a modified, and even sometimes in a corrupted, way.

#7   87%      4
Top 3 Challenges of Agile Transformation

Feb 2 13:01:00 by dzone.com

Agile needs no introduction in today's world. The term gets used more often than "computer" in business contexts. Organizations are increasingly looking at Agile as their default approach for software delivery. As larger organizations attempt to apply Agile software development methodologies at the enterprise level, I am attempting to specify the top three challenges, blockers, and barriers: Lack of executive commitment. People and culture. Neglecting the need for technical excellence. Let's elaborate briefly each of these challenges.

#8   22%      4
Automating Azure Analysis Services processing with Azure Functions

Feb 9 11:00:13 by azure.microsoft.com

In this post, we’ll walk through a simple example on how you can setup Azure Functions to process Azure Analysis Services tables. Azure functions are perfect for running small pieces of code in the cloud. To learn more about Azure Functions, see Azure Functions Overview and Azure Functions pricing. Create an Azure Function To get started, we first need to create an Azure Function 1. Go to the portal and create a new Function App. 2. Type a unique Name for your new function app, choose the Resource Group and Location. For the Hosting plan use App Service Plan. Note: As the duration of processing Analysis Services tables and models may vary, use a Basic or Standard App Service Plan and make sure that the Always On setting is turned on, otherwise the Function may time out if the processing takes longer. Click Create to deploy the Function App. 3. In the Quickstart tab, click Timer and C#, and then click Create this function. Configure timer settings Now that we’ve created our new function, we need to configure some settings. First, let’s configure a schedule. 1. Go to the Integrate > Timer > Schedule. The default schedule has a CRON expression for every 5 minutes. Change this to any setting you would like. In the example below I used an expression to trigger the function at 3AM every day. Click Documentation to see a description and some examples for CRON expressions. 2. Click Save. Configure application settings Before we begin writing our code, we need to configure the application. Important: Make sure you have the latest data providers installed on your computers. To get more info and download, see Data providers for connecting to Azure Analysis Services. After installing the providers, you’ll need these two files in the next step: C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\Microsoft.AnalysisServices.Core.dll C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\Microsoft.AnalysisServices.Tabular.dll 1. In the new Azure Function, go to Function app settings > Go to Kudu, to open the debug console. 2. Navigate to the function in D:\home\site\wwwroot\yourfunctionname, and then create a folder named bin. 3. Navigate to the newly created bin folder, and then drop the two files specified in the previews point. It should look like this: 4. Refresh your browser. In Develop > bin, you should see the two files in it (If you don’t see the file structure, click View files). 5. Before we write our code, we need to create a connection string. In Function app settings, click Configure app settings. 6. Scroll to the end of the Application settings view, to the Connection strings section, and then create a Custom connection string. Provider=MSOLAP;Data Source=asazure://region.asazure.windows.net/servername; Initial Catalog=dbname;User ID=user@domain.com;Password=pw Add code Now that we have our function’s configuration settings in-place, we can enter the code. You’ll need to reference the DLLs we uploaded, but other than that it looks like any other .Net code. Note: In this example, I included some commented lines to only process a table or the model. #r "Microsoft.AnalysisServices.Tabular.DLL" #r "Microsoft.AnalysisServices.Core.DLL" #r "System.Configuration" using System; using System.Configuration; using Microsoft.AnalysisServices.Tabular; public static void Run(TimerInfo myTimer, TraceWriter log) {     log.Info($"C# Timer trigger function started at: {DateTime.Now}");       try             {                 Microsoft.AnalysisServices.Tabular.Server asSrv = new Microsoft.AnalysisServices.Tabular.Server();                 var connStr = ConfigurationManager.ConnectionStrings["AzureASConnString"].ConnectionString;                 asSrv.Connect(connStr);                 Database db = asSrv.Databases["AWInternetSales2"];                 Model m = db.Model;                 //db.Model.RequestRefresh(RefreshType.Full);     // Mark the model for refresh                 //m.RequestRefresh(RefreshType.Full);     // Mark the model for refresh                 m.Tables["Date"].RequestRefresh(RefreshType.Full);     // Mark only one table for refresh                 db.Model.SaveChanges();     //commit  which will execute the refresh                 asSrv.Disconnect();             }             catch (Exception e)             {                 log.Info($"C# Timer trigger function exception: {e.ToString()}");             }     log.Info($"C# Timer trigger function finished at: {DateTime.Now}");  }   Click Save to save the changes, and then click Run to test the code. You’ll get an output window where you will be able to see the log information and exceptions. Learn more on Azure Analysis Services and Azure Functions.

#9   87%      2
Microsoft's Windows 10 Cloud version: Alleged screen shots leak

Feb 3 21:18:00 by www.zdnet.com

Alleged screen shots of Microsoft's coming Windows 10 'Cloud' variant (which may actually have nothing to do with the cloud) have leaked to the Web.

#10   65%      3