martes, 28 de julio de 2015

Scrum retrospective (Don’t Forget to Sharpen the Saw)

Hi there,

The retrospective meeting is one of the most important SCRUM artifacts with the objetive to improve continuosly the quality of the product that we are developing, the team's productivity and more.

The team analizes the way we have worked during past iteration, why we are reaching (or not) the objetives (iteration commitment) and why the product delivery piece is what the client is expecting (or not).

As a standard format we can use the one suggested here (spanish content). On this video is explained with the addition of the safety-check (pretty interesting!) but is nice to innovate and try other formats as starfish for example. We have used many times and has the advantage that you can compare in an easy and visual way the evolution of the meetings during the entire project.

It would be great that you could spend some time and go trough all the introductory scrum videos from scrummethodology. Each video takes a few minutes and all the concepts are explainend very well.

I'm sharing the following article to remember why is so important to celebrate the retrospective meeting on every iteration:

Don’t forget to sharpen the saw

"I recently encountered a Product Owner who had been doing an excellent job in his role, but who pushed back on taking time to do a retrospective at the end of a sprint.    He said, “We have momentum and we’re making progress.  Why would we possibly want to stop and waste time doing this now?”

Steven Covey tells the following story in “Seven Habits of Highly Effective People”:

There’s a guy who stumbled into a lumberjack in the mountains. The man stops to observe the lumberjack, watching him feverishly sawing at this very large tree. He noticed that the lumberjack was working up a sweat, sawing and sawing, yet going nowhere. The bystander noticed that the saw the lumberjack was using was about as sharp as a butter knife. So, he says to the lumberjack, “Excuse me Mr. Lumberjack, but I couldn’t help noticing how hard you are working on that tree, but going nowhere.” The lumberjack replies with sweat dripping off of his brow, “Yes…I know. This tree seems to be giving me some trouble.” The bystander replies and says, “But Mr. Lumberjack, your saw is so dull that it couldn’t possibly cut through anything.” “I know”, says the lumberjack, “but I am too busy sawing to take time to sharpen my saw.”
In the spirit of continuous improvement, we don’t want to do unproductive and useless things.    Within a sprint, team members are empowered to fix tasks that aren’t working, or eliminate tasks that don’t add value.   The restrospective at the end of a sprint provides a way for the team as a whole to see things that individuals may not see by themselves.     So if you notice the saw getting dull, stop and sharpen it now, don’t wait.    And If you don’t happen to notice the saw getting dull, but knowing that saws tend do get dull with use, stop every once and a while and check for dull blades."


lunes, 15 de junio de 2015

Scrum - Backlog grooming meeting or Backlog refinement?

Hi there,

One of the different artefacts that SCRUM offers to us is the backlog grooming meeting 

Time ago someone told me that in some places the word "grooming" has a negative meaning so it tooked my atenttion and I decided to search further. Finally the meaning is negative (this doesnt' mean that we shouldn't celebrate the meeting!!!!)

I think as best practice we should use one of the many equivalent names: Backlog refinement, backog estimation, story time 

Till next time!

viernes, 5 de junio de 2015

TFS - Moving to a new server (not conventional way)

Hi there,

On my current project we have the necessity to do a server migration because the OS unit can't extend and all the time we are getting the out of space error.

We plan the migration moving the C unit (OS + TFS) and the F one (Databases) to the new server.
Of course TFS wasn't working so we started with the configurations.
The post title is "not conventional way" because we didn't use the TFS installation wizzard. Get it will demand us a lot of time and in the meanwhile the team was working blind. We had to do something and quick.
We have followed the next steps as a recipe:
  • Reconfigure reporting section: We have logged in into the new server with administrator credentials and use the Reporting Services Configuration Manager. Is very important to modify the database connection and the report urls. For more information you can go to msdn.
  • TFS configuration database remapping (Tfs_Configuration). For this we are going to need a TFS tool known as TfsConfig. You can find it under %programfiles%\Microsoft Team Foundation Server 2010\Tools folder (this can change according TFS version). First of all we have to close the TFS Administration console and then run the following commands:
TFSConfig RemapDBs /DatabaseName:[Server];TFS_Configuration /SQLInstances:[Server] /continue
TfsConfig RegisterDB /SQLInstance:[Server] /DatabaseName:TFS_Configuration
        Replace [Server] with you server's name.
  • TFS re configuration: Enter TFS administration console and start the collection again. Modify the app urls (application tier option) and the reports / jobs information (under reports section)
  • Modify cache folder: You can use this link. Basically you have to change it ont the application tier web.config file.


Show SSRS Reports properly in Chrome and Safari

Hi there!

To make the change permanent you have to then go to your SSRS Server then on the path where SSRS is installed you have to do some modifications on the js file called ReportingServices.js. By default in SQL Server 2012 it will be inC:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportManager\js
Open the file, you will notice it will be a minified js.
Go to the bottom part then copy and paste the following js code.


Till next time!

Announcing the visual studio 2015 product line

Mitra Azizirad announces the new VS product line!


TFS - @CurrentIteration on queries!!!

@CurrentIteration is now available for queries and more! According to de VS Team:

We are happy to let you know that we have addressed this suggestion. It will be enabled on Visual Studio Online this week, and if you have an on-prem installation, it will be included in TFS 2015 RTM.
More info here.