Thursday, December 22, 2011

Effective Leadership Planning

Close after more than three decades of working with hundreds of directors, I realized that perhaps the biggest obstacle for many of them, a technique in comparison with the prospect of contracting is the ability and willingness to devote sufficient time, attention and importance to the planning process. I mean a planning process, as it is a first step, once a plan for me to have an event. By contrast, requires planning a series of variables such as attitude, knowledge, expert consultants, contingencies (also known as IFS) and drive a real commitment to the planning process.

First, why have a plan to drive? Many people get into positions of leadership without a compelling vision and objectives of the organization. They often say that (the general term "do not like, because I believe in micromanagement of my officers and employees.") In the leaves, and seem to think that only the results by stepping aside to achieve and delegate tasks and responsibilities . While the delegation should be encouraged, a true leader is to ensure that recognizes that the responsibility be carried out and that the individual is willing to commit themselves fully to accomplish the mission (or work). Unfortunately, I have seen many people who have their own risk as the leader against the possession, and had no plan for monitoring and periodic progress reports, etc.

Second great leaders can have a positive attitude. Full on the job best, and take careful planning process seriously. However, these people realize that to be implemented at some point, planning should lead to achieving the vision and / or goals, and plans must be in the action plans and action plans must be viable and meaningful actions , leading to an alteration, modification or adjustment, if necessary.

Executives must understand the need third of contingency planning and backup. Each plan should discuss in detail what would happen when the inevitable, and we created this plan, almost all eventualities. Great leaders always plan for unforeseen and unavoidable.

Fourth Before planning to have a leader to be ready for submission, and a deep leadership training. Too often there are people who make these programs lived a single day, and almost immediately proceed with the same old behavior, always anyway. Training should achieve true learning. Training and learning should be in situations where a person can be used under the supervision of the blame. Only after all this is satisfactory and successful, is a potential leader has the option of one. Real and effective as it is now, both the knowledge and experience.

Companies need to be in the leadership planning learning. The plan should include training in leadership, event planning and ongoing strategic planning, including assessment and reassessment of the mission statement. Planning organizations to develop the background of the vision, the real leaders.

Friday, December 9, 2011

systems development life cycle (SDLC) for Business Analyst

The systems development life cycle (SDLC), or software development life cycle systems engineering, information systems and software engineering, the process of creation or modification of systems and models and methods that people using these systems. The term generally refers to computer or information.

In software engineering the underlying concept of SDLC methodologies are many types of software development. These methods provide the framework for planning and control of the creation of an information system: the software development process.

Systems Development Life Cycle (SDLC) is a process used by the systems analyst for an information system, including requirements, validation, training development, and the user (stakeholder) property. Each SDLC should result in a high quality system that meets or exceeds customer expectations, within time and cost estimates, works effectively and efficiently in the current and future IT infrastructure, and is cheap to maintain and economic strengthening.

Computer systems are complex and often for any business analyst (particularly with the recent emergence of Service Oriented Architecture) linking traditional systems supplied by different vendors. To address these complexities, a number of SDLC models or methodologies are made, as the "waterfall", "spiral", agile, rapid prototyping, "incremental" and "sync and stabilize".