background preloader


Facebook Twitter

Project framework creation: IT manager's comprehensive view.


Process Flows. Word choice - "Functionalities" vs "features" - what's the difference? Design - Feature vs. Function - Software Engineering Stack Exchange. Agile. What Questions Do I Ask During Requirements Elicitation? 5 questions to ask before starting any technology project. 10 ways to discover what the problem really is. Enterprise Architecture. Business Process Mapping. IIBA BABOK Infographic. Training. Team Meetings. We’ve all walked out of meetings and thought, “Well, that could’ve been in an email!”

Team Meetings

One way to sidestep complaints about your own meetings is to make sure you’re actually ready to drop something on the calendar – and not just because you feel like you’re due for a chat. How can you tell where on that spectrum you fall? Use the signs below to diagnose your own situation and determine whether or not a team meeting is really necessary. Schedule that meeting if . . . 1. Every meeting needs a clear mission or objective, otherwise there’s really no point in getting together. 2. Once you’ve settled on your mission, it shouldn’t be a secret – loop in the rest of the team on what you’ll discuss and what you’re trying to get done. 3.

Types of Assets - List of Asset Classification on the Balance Sheet. An asset is a resource owned or controlled by an individual, corporationCorporation, or government with the expectation that it will generate future cash flows.

Types of Assets - List of Asset Classification on the Balance Sheet

Common types of assets include: current, non-current, physical, intangible, operating, and non-operating. Correctly identifying and classifying the types of assets is critical to the survival of a company, specifically its solvency and associated risks.

Business Process Modelling

Онлайн-тренинг «Product Owner: Разработка и управление требованиями в Agile» Learn Agile Easily with a Free Personalized Guide. The seven tenets of new age business analysis. The most radical period of change in industrial history is nearly upon us.

The seven tenets of new age business analysis

Technology is evolving faster than humanity is able to keep up with it. There is now a need for rapid, sustained and growing innovation in what the World Economic Forum has dubbed the Fourth Industrial Revolution . The first industrial revolution brought in steam to mechanize power; the second brought in electricity to power mass production, and the third was the dawn of the information era with the rise of the internet. This has massively transformed the way businesses are conceived and run. 1. Traditional businesses have needed to own physical assets in order to provide any sort of services to end customers. CBAP® in 4 months - My Study Approach. How to Manage negative stakeholders? (Sorry you can't shoot them) How to manage negative stakeholders?

How to Manage negative stakeholders? (Sorry you can't shoot them)

(Sorry you can’t shoot them) I wish you do not face the need to manage negative stakeholders in your project lives. But life is not going to fair all the time and you need to learn to manage negative stakeholders. Negative stakeholders will try to break your morale, make you cry in the restroom (for no fault of yours). But then, one grows only in adversity. You may be surprised why such a stakeholder group would exist. They may have a personal grudge against the sponsor. UAT Tips and Templates. Facilitators skills - Getting the most from your workshop.

What is Visual Paradigm? Industry Data Models. Untitled. Best Requirements Management Software. 2,000+ businesses use Capterra each week to find the right software.

Best Requirements Management Software

You have selected the maximum of 4 products to compare Requirements, prototyping and diagrams - all in one! The iRise collaborative platform helps teams define, communicate, and validate requirements in a visual and interactive way that's far more effective and efficient than traditional methods. We also integrate with the leading ALM tools like Jira, TFS, Rally and Blueprint, so you can bring the value of collaborative prototyping to your existing tool-set. View Profile. Принцип пирамиды Минто (Барбара Минто) Top 10 Articles for 2015. 2015 saw growth for in the number and quality of content on our site.

Top 10 Articles for 2015

Личный кабинет. Система Управления Знаниями: функциональность. Что такое Система Управления Знаниями?

Система Управления Знаниями: функциональность

Система Управления Знаниями - приложение, предназначенное для: Передачи экспертных знаний в компании; Поддержки принятия решений; Решения оптимизационных, прогнозных задач; Качественного анализа бизнес-информации. Ключевые особенности СУЗ состоят в возможности автоматического получения логических выводов на основании аксиом и фактов, и возможности отвечать на вопросы пользователя, сформулированные в терминах концептуальной модели.

ТриниДата: редактор онтологий - редактор онтологий с веб-интерфейсом.

ТриниДата: редактор онтологий

Он предназначен для составления и редактирования информационной модели, используемой в АрхиГраф.СУЗ и АрхиГраф.MDM. Редактор доступен в режиме он-лайн по адресу Вы можете зарегистрироваться, и попробовать поработать в нем. Для знакомства с возможностями редактора доступы краткая и полная версии пользовательской документации. Сервисная шина "Бизнес Семантика" Наш основной продукт - сервер "Бизнес Семантика".

Сервисная шина "Бизнес Семантика"

Этот продукт является сервисной шиной предприятия (Enterprise Service Bus). Он выполняет передачу данных между интегрируемыми информационными системами, контролируя права доступа, обеспечивая целостность передаваемых данных. MIKE SUCKS. Интернет-радио аналитиков. The Business Analyst's Toolkit - Business analysis fundamentals for the information technology professional. Thanks for Subscribing! - The Business Analyst's Toolkit.

Fundamentals of Business Analysis - Udemy. Course Overview This course provides everything you need to get started in your career in business analysis.

Fundamentals of Business Analysis - Udemy

Our courses focus on how analysis is performed in the real world, and they’re full of examples, case studies and lessons learned from actual Business Analysts on the job. This is a perfect first course in any business analysis curriculum. Stay tuned for upcoming courses by following us on Facebook or Twitter! Плохие новости для должников и кредиторов – еще впереди - Финансы - PROBUSINESS.BY. «Про бизнес.», 3 марта 2015. Business Analysis. Agile RM Q&A. Agile RM Q&A Пишите вопросы в конец плс Change requests, change management methods, risk management methods, Acceptance cryteria, BDD - please, give us examples of good A.C and C.R. Чем принципиально отличается управление требованиями для Agile и "обычных" проектов?

Процессы по каждому проекту всегда отличаются. Каждый проект получается уникальным в управлении. Есть методика и получается не придумывать велосипед? Agile RM – Конспект. Agile RM – Конспект I.Вводная часть pbi - product backlog items Шаблоны декомпозиции Пользовательских Историй (patterns splitting user stories) II. Общие слова об Agile Объяснение на примере Scrum (каркас для построения процесса) Роли: product owner, scrum master, team. Russian IT Business Analysis by Alexander Belin. Untitled. eMag: Agile Project Estimation and Planning. Estimation is often considered to be a black art practiced by magicians using strange rituals.

It is one of the most controversial of activities in Agile projects – some maintain that even trying to estimate agile development is futile at best and dangerous at worst. There are indeed times when estimating is unnecessary and/or pointless. If the work is novel, nothing like it has been attempted before, the skills of the team (or who the team will be) are unknown or the work just has to be done (either the value to be derived from having the product is compelling or it is a compliance or survival project) then estimating may be a waste of time and effort. The more common reality is that there is a need to provide at some sort of estimate of the likely time and cost needed to build the product. Business decisions need to be made regarding which initiatives to fund and the allocation of funds and people to do the work. Boatmans Home Start. Онлайн-курсы по бизнес-анализу. Good Books You Should Read.

Use Cases

UML. BA Videos. IT Школа бизнес-анализа. What Goes Into a Functional Specification? If you find yourself in a business analyst role on an IT project, it’s likely that at some point you’ll need to create a functional specification. But what is a functional specification? Why do you create a functional specification? And, perhaps more importantly, what goes into a document like this? The purpose of a functional specification is to define the requirements to be implemented by the software solution. Now, as business analysts, not all aspects of our solutions are software-based.

But since so much of business today is supported directly by IT systems, many times solving a problem means upgrading or building new software…and that means specifying functional requirements. Functional Specifications Take Many Forms Depending on your methodology and business analysis practices, a functional specification can come in a variety of different formats. The Functional Spec is Where Business Meets IT.