search back preload
Unified Blog
Enhancing Engineering Practices through Scrum
Written by Lisbeth Cardoso   
Monday, 22 October 2012 18:42

Definitely, engineering practices can either boost or hinder team’s performance.

If any of the team members reports that he or she is working on a model during a Daily Scrum, it’s very healthy for the team to gather with the Scrum Master after the Scrum to discuss the adopted modeling practice.

Does the team build models to guide its thinking or because it’s being told to do so? Does the team become more productive if models are optional? Does the code quality suffer if models aren’t used? Team members might respond these questions first before taking any decision.

Definitely, keeping models synchronized with code can become a Herculean task within any organization. Scott Ambler recommends using the Agile Modeling, which encourages communication, simplicity, feedback, courage, and humility.


No matter what, daily builds should happen. Without them, team members won’t be able to know if the code holds together, and testing the delivered product won’t be possible as well. Daily builds guarantee that the team moves forward as a whole at all times.

Last Updated on Thursday, 25 October 2012 12:46
Written by Lisbeth Cardoso   
Saturday, 13 October 2012 16:40


When it comes to implement Scrum, Scrum Masters must determine first if it’s for a new or an ongoing project. Their initial approach varies according to this variable.

If the Scrum Master is facing a new project, the first step becomes working with the team and the Product Owner for several days in order to define the initial Product Backlog. At first, either the team or the costumers have a defined and solid idea of what the Product Backlog must be, and it usually consists of some business functionality and the technology requirements.

Within the first Sprint, teams usually settle into a development environment that allows them to build functionality, and construct a working part of the system to present to the Product Owner and customers by the end of the Sprint.

While the team is focused on its work, the Product Owner adds more Product Backlog; therefore, the goals to accomplish will become more defined and transparent.

On the other hand, when the Scrum Master is called to assist an ongoing project, it’s usually because the team is struggling with requirements and difficult technologies, and management wants it to be more productive.

In this case, the Scrum Master needs to find out what’s impeding the team and remove any existing blocker. The first Daily Scrums can go for hours if it’s necessary, but he team has to express their frustrations and explain what problems they are facing. Then, the Scrum Master needs to remove any impediments, invigorate the team members and ask them what functionality they can build during the Sprint.

The important idea to remember by everyone is that, as long as the team delivers some product increment, the customers will become interested, and the team will gain more confidence and commit to more work.

Last Updated on Tuesday, 16 October 2012 18:36
Revolutionizing practices through Scrum
Written by Lisbeth Cardoso   
Saturday, 13 October 2012 15:48


It’s a fact that Scrum encapsulates all the existing engineering practices. Introducing new methodologies or cultures is usually quite difficult; this is not the case when it comes to Scrum. Scrum simplifies work by allowing management and the team focus on what truly matters: deliver a product increment by the end of the Sprint.

It definitely changes the way people experience work. When the Sprint begins, managers might feel they have nothing to do because the team is the one taking absolute control of its performance. As the manager participates in the daily Scrums, he or she starts making important decisions, removes any blocker affecting the team’s progress and helps the team focus on the Sprint goal.

As a happy result of Scrum, as an organization starts using it, workers become empowered and give their best; managers do less paperwork and accomplish more.
Every organization has its very unique way to react to Scrum. In the meantime, Scrum is incrementally delivering results.

Last Updated on Saturday, 13 October 2012 15:53
IS Unified
Written by Lisbeth Cardoso   
Wednesday, 10 October 2012 15:16


ISU Corp is honored to present you IS Unified, a next generation system that focus on Enterprise Resource Planning for the digital economy.

IS Unified focuses on maximize work efficiency through its fully integrated modules; these modules allow users to do Project management, Asset management, Tier One support and help desk, as well as a variety of other functions.

IS Unified provides a secured and unique platform to facilitate organization for all stakeholders during the project development lifecycle, tracks and manages resources, allows to do research and analysis, provide estimations, manages long term plans of action designed to achieve a particular set of goals, and much more.

In conclusion, IS Unified is the all-in-one management tool your organization was waiting for!

Do you want to know more? Click here!

Last Updated on Wednesday, 10 October 2012 16:18
Sprint Review Meeting
Written by Lisbeth Cardoso   
Friday, 28 September 2012 18:27


In essence, the Sprint Review is an informational meeting where the team exposes the built product increment to the Product Owner, management, and users.

The Product Owner attends this meeting to find out how much functionality the team has built so far. Management, on the other hand, joins the Sprint Review to see what the team has accomplished using the given resources. Customers come to see if they like what the team has delivered. Other developers might participate as well to learn what the team was able to do with the technology and how.

The one in charge to organize and conduct the Sprint Review meeting is the Scrum Master. He meets with the team to plan how the Sprint results will be presented, in which order, and by whom. He has to set the Sprint Review meeting’s date to the day after the Sprint ends.

It’s recommended that the Scrum Master begins the meeting giving a compact overview of the Sprint. Also, the Sprint Backlog and Sprint goal must be compared and any resulting discrepancy, explained. In the meeting, every product functionality demonstration must be end-user oriented. All attendants, at the end, should understand the system and its design, technical architecture, functionalities, strengths and weaknesses.

The Sprint Review encourages brainstorming as well. Discussions, observations, and questions should happen. The Sprint Review becomes a success when everyone is well informed about the product increment and prepared to give their best efforts to the next Sprint.

Last Updated on Friday, 28 September 2012 18:31
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>