2Know Magazine: Sharing KM Knowledge
2Know: Sharing KM Knowledge
January 2015 - Magazine No. 184
January 2015 - Magazine No. 184
Edition:
Written By Meirav Barsadeh

How many times have you accidentally pressed the wrong button? In too many cases, it seems that site users might not understand the action they are required to perform. A state of uncertainty can cause the user to slow down, hesitate and maybe, accidentally, make a wrong move that may harm the mission.

There are three kinds of activities that can be performed by pressing a button:

  • A positive action: performing changes, sending or adding data.
  • A neutral action: either not changing anything or taking the user back to the previous screen.
  • A negative action: erasing data, formatting or blocking.

Usually, one screen will feature the following buttons. Our goal is to differentiate between the buttons in order to assist the user in completing his mission successfully. A differentiation can be performed using different colors or text. Color is an important feature in the user interface, not only as an aesthetic tool but also as an effective tool for instructing users. The text assists in understanding the essence of the activity, specifically by handicapped users.

 A clear contrast between the colors of the different buttons is an efficient method to direct users to clicking on the correct button. In order to receive a maximal contrast, it is recommended to design the positive action button featuring a calm color, such as blue, purple or green. The color tends to retreat to the background, and the white lettering stands out and catches the user's eye.

A button with a neutral or negative action located near a positive action button should remain uncolored, so as to prevent the user from confusing the buttons. Instead, leave only the outline so the button fades into the background. This way, the buttons won't "compete" for the user's attention. In other cases, it is recommended to color the negative action button with a "warm" color (such as red, yellow and orange) in order to highlight the danger in accidentally pressing this button. The user will surely think twice before pressing. If the activity the user must perform consists of choosing between a neutral action and a negative one, a distinct color contrast should be applied.

.

A neutral action button will never be presented alone. It will always be appear either next to a positive or negative button. Therefore, a bold outline will suffice in order to differentiate between the neutral and positive/negative buttons.

Note: do not color the outline of the button gray and/or color the text brightly. Users might mistakenly think this button defunct or inactive.

Review: Agile BI
Written By Anat Bielski

 

The term 'agile', when used in the world of software development, refers to an approach saying that software cannot be fully defined before it is completely developed; instead focus should take place on improving a team's ability to provide products quickly and react to demands made during the development.

 

Agility in the world of BI

Agility can be implemented continuously in BI in several ways:

  1. Time efficiency: In the traditional process of BI tool development, most developments are long term developments based on precise characterizing of each potential source and target of information. Agile Methodologies, on the other hand, deal with interactive developments in which the demands and solutions are developed through the cooperation between the different work teams (e.g. development, clients and customers) while focusing on quick prototypes that encourage the users to give feedback and thus specify their needs.
  2. A flexible solution easily adapting to changes: Agile BI is characterized by a total low cost of change implementation. This methodology encourages business users and IT personnel to think differently, ask new questions and illustrate the answers in various ways and tools, each adapted for the users' needs. One example of this adapting are the adjustments one can perform on the Dashboard or the fact one can create a new Dashboard if it is more suitable.
  3. Project management in the Agile world: Agile development requires Agile project management. When following the traditional approach, the planning is performed at the beginning of the work process and would often lead to a long term schedule and cumbersome execution. The Agile methodology focuses on a consistent cycle of planning, execution and feedback. The planning occurs at the beginning of each cycle, as opposed to the beginning of the project and the lessons learning process occurs at the completion of each cycle. Furthermore, it is possible to change the solution's scope during its development. At the end of each cycle, new useful tools are produced. The time spent on their production is substantially shorter than its equivalent in the traditional BI method.
  4. Creating intuitive tools for users: using the Agile methodology for BI provides intuitive Dashboards and designated user friendly analytical tools that can be applied in the organization. The result is an ability to enhance the independently created report services, improving continuously the user experience. Using friendlier interfaces can enable a quicker, more precise decision making process.
  5. ROI enhancement: organizations can enhance their ROI by decreasing their development resourcing and a temporary decrease of knowledge sharing.

 

How to apply Agile BI?

In order to apply Agile BI, we must first construct a work team comprised of IT personnel and business representatives. Following this, this team must identify and prioritize the demands dealt with, as well as decide which demands will be dealt with in the first cycle, and initiate an interactive development process. The IT must use, in this case, Agile BI tools that can match the organization's database.

 

To conclude, Agile BI promotes quick, flexible, cost efficient development of BI solutions. Using this methodology enables the organization to quickly react to changes in the business needs and provides users with intuitive tools in order to receive the best answers required for business decision making. Furthermore, the Agile approach is also relevant for complex projects such as updating search engines and KM management projects in general. Obviously, each case should be individually reviewed. Every solution has pros and cons and one should be sure, before running Agile projects that also here, the benefits are significant, and we all will smile at the end of the day.

 

References:

Agile software development

Why Agile BI?  

   

Written by Rom Knowledgeware
Fax 077-5020772 * Tel 077-5020771/3 * Bar Kochva 23 st., Bnei Brak Postal: 67135