search back preload
Unified Blog
IS Unified v1.0.12.1831 Release Notes
PDF
Print
E-mail
Written by Lisbeth Cardoso   
Tuesday, 20 November 2012 12:45

 

ISU

IMPORTANT! What’s New on this latest version of ISU?

vProject Manager

  • Project Plan functionality added.
  • Budget functionality added.
  • Ribbon has been modified.
  • Scrum tab functionalities added
    • Release Plan/Sprints
    • Product Project/Backlog
    • Story Board
    • User Story Track
    • Burndown Chart
    • Velocity Report

vSQA

  • Show All functionality fixed.
  • Security added.

vApplication Manager

  • Design details fixed.
  • Save data when creating or editing an application fixed.
  • Module/Component functionality added.
  • Version functionality added.
  • Development Team functionality added.

vDocument Manager module added

See more....

Last Updated on Tuesday, 20 November 2012 14:01
 
The Risk Management and Predictability View of Scrum
PDF
Print
E-mail
Written by Lisbeth Cardoso   
Monday, 19 November 2012 18:09

                                                       RISK

As we discussed in a previous article, in the software development industry every project is unique and complex. Each project must be treated as a brand new project; as a consequence, uncertainties and risks may appear. Therefore, Scrum’s ability to detect, manage and tame these uncertainties and risks becomes imperative within the software development lifecycle.

First of all, Scrum eliminates the risk of not pleasing the customer by allowing him or her to see the product increment on regular basis - at the end of each Sprint -. This way, the customer can participate and monitor the project’s development, and give his or her feedback and priorities to the team.

Also, by maintaining this close and active customer’s involvement within the entire project’s lifecycle, Scrum guarantees that the team won’t have to take the risk of overworking because the customer suddenly changed his or her expectations.

Through the Daily Scrums, this innovative paradigm battles the risk of poor estimating and planning by providing daily up-to-date information of the project’s status. If at the end of the Sprint all its goals weren’t completed on time, Scrum will accommodate these goals through the Sprint Review and Sprint Planning meetings.

Besides, by prioritizing functionalities in each Sprint, Scrum assures that all the functionality or at least all the high priority functionality will be delivered.

Scrum also fights the risk of management not resolving issues in an efficient manner by requiring the active participation of management in the whole development process through the Daily Scrums.

Finally, Scrum guarantees the development cycle’s full completion. If there are any blockers with engineering practices, Scrum forces the team and the Scrum Master to confront them and solve them.

Scrum provides a win-win environment for customers and development teams by engaging everyone in the entire project’s lifecycle and, as a happy result, minimizing risks and uncertainties.

Last Updated on Monday, 19 November 2012 18:19
 
New product development view of Scrum
PDF
Print
E-mail
Written by Lisbeth Cardoso   
Friday, 16 November 2012 15:06

                                          SCRUMARROW

Software development is not a linear well-defined process. Even though projects may use established patterns and methodologies, each one of them is unique in terms of implementation, business rules and objects, transaction and services required; therefore each one of them demands a different approach to be solved.

Creating something new involves research, learning, creativity and adaptability. In software development these activities crave for non-traditional ways to assume projects’ estimation, planning and management.

Studies have shown that most innovative and competitive companies in the software development industry have succeeded because:

• Their teams are self-organized.
• Their team members have absolute freedom to do whatever they think is the best for the project.
• Discovery, invention and testing stages are continuously overlapped during the whole development process, ensuring involvement, commitment and initiative taking.
• Their team members remain up-to-date with outside sources of information so they can respond and adapt in a fast pace.
• Management maintains a subtle control to prevent chaos without interfering with the team’s performance.
• They create open work environments.
• They incorporate members of previous teams to new teams.

Scrum cherishes and encourages all of these traits. This is the reason why Scrum is the right solution when companies want to succeed in software development industry arena.

Last Updated on Friday, 16 November 2012 15:17
 
Scrum: no "magic" formula to follow
PDF
Print
E-mail
Written by Lisbeth Cardoso   
Thursday, 15 November 2012 15:01

                                       FISH

Scrum practices may look very simple and therefore not trustworthy at first sight, but they definitely have a strong impact in today’s way of thinking regarding what software is and how to experience its life-cycle.

Software development brings to life new products, innovative ones. Therefore, there’s no "magic" formula to follow. Each project is unique, and must be accompanied by the proper amount of research, creativity and adaptability. Here comes the answer to software development problems: Scrum.

But again, why is necessary to have all these Daily Scrums, and follow these whole iterative, continuous control within Scrum practices? Scrum meetings are not only to report what each member did, they allow to actively involve management and commit everyone, not only the team members, to do their best to accomplish the project’s goals.

“Scrum is about deep social interactions that bring trust among team members”, explained Ken Schwaber and Mike Beedle in their book “Agile Software Development with Scrum”.

To understand why Scrum works, we’ll be analyzing the following views in future articles:
   • New product development view of Scrum.
   • Risk management and predictability view of Scrum.
   • Kuhnian view of Scrum.
   • Knowledge creation view of Scrum.
   • Complexity Science view of Scrum.
   • Anthropological view of Scrum.
   • System Dynamics view of Scrum.
   • Psychological view of Scrum
   • Football metaphor.

We don’t pretend to provide you with a cumbersome and exhaustive explanation of each one of these views; we just want to give you a brief introduction into them to show you why Scrum is the right methodology to follow when it comes to software development.

Last Updated on Wednesday, 02 January 2013 20:45
 
Why Scrum Works?
PDF
Print
E-mail
Written by Lisbeth Cardoso   
Friday, 09 November 2012 14:55

                     TEAMRED

Evolution has taught us that those organisms that are able to adapt to new or hostile conditions are the ones that have more chances of survival. That’s were Scrum strength lies on, in its ability to adjust to the unexpected. That’s why it works!

Nowadays, complicated processes have become a trend in our daily lives. When activities are so complex that they are impossible to predict in advance and aren’t repeatable, the empirical process control model is then needed.

The empirical process control model is pretty simple and straightforward. It inspects what’s occurring and adjusts to produce desired outcomes.

Scrum uses this model. During a Sprint, the self-organized team empirically determines how to build a product increment given the technology and requirements. Daily Scrums controls the team’s performance by providing the information needed to empirically decide what the next steps will be. At the end of the Sprint, there’s another control: the Sprint Review, where all the delivered functionality is examined. Then, the Product Owner, the Scrum Master and the team decide what to do for the next Sprint.

Scrum thinks of every project as a unique one, teaches teams to work on their own as a unit, involves management in every step of the way, inspects the project status on daily basis and adapts to it to get the best possible outcome. How can it not work?

Last Updated on Friday, 09 November 2012 15:31
 
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>

RSS-header

RSS-bottom