23 Results Found
Effective requirements collection at the outset of the project is the key step that will ensure that the project manager can deliver what is actually expected. In this respect, the business analyst must become a key ally and advisor to the project manager. Most project managers are not trained business analysts, so taking advantage of the skill set that a business analyst can offer can greatly enhance the possibility of project success.
The principles in this white paper help you introduce greater predictability into your own Agile requirements activities, both individually and across your organization. As you start to apply these ideas and pose these questions, you'll likely see certain patterns emerge that will help you establish your own set of practices that make Agile work for you.
Many people believe that cloud computing requires server (or desktop) virtualization. But does it? We will look at using virtualization without cloud computing, cloud computing without virtualization, and then look at using both together. In each case, we'll look at where each deployment might be most useful, some use cases for it and some limitations.
One of the most significant new features in Microsoft Windows Server 2012 is the Hyper-V Replica (HVR) capability. Whether you are considering this for your own organization or just prepping for your Windows Server 2012 MCSA, this white paper presents the essentials of deploying this disaster recovery feature.
In this paper, we explore the basic usage of PowerShell in the pursuit of automating the management of Hyper-V deployments. This paper is targeted to IT professionals who have been "GUI-bound" to their management interfaces and have been working with or are embarking on the journey of Hyper-V administration. We'll explore the usage of Hyper-V specific cmdlets with the intent of ultimately being able to include multiple cmdlets in a "script" to allow for pushing one button and accomplishing the combined actions of many multiple mouse clicks in the GUI. No more repetitive tasks!
We build requirements at a quantum level to connect the vital elements, which are needed to realize a requirement. As we consider the relationships between the behaviors, actions, and responses, we begin to identify and associate the characteristics and conditions, which will drive and constrain the behaviors. Realizing a requirement means joining these elements together and noting them as elements of the requirement.
Linking business analysis skills with the methods of The Open Group’s Architecture Framework, TOGAF®, facilitates stronger IT results that drive business value.
Resource management is always an issue in any project, especially when the stakeholders from whom we need time have operational duties to perform. If our requirements team was at our disposal 100 percent, always completed activities on target, and worked a full eight hour day without distraction or a loss of productivity, then estimating time would be simple. In this paper, we explore standard approaches to time estimation, the dangers of multi-tasking, and estimation alternatives, which consider work habits and productivity norms.
A structured business analysis interview is much more than a conversation; it is a controlled event requiring attention to detail, cautious design, and a strong social foundation from which to build a trusting and lasting relationship.
When designing a structured business analyst interview, it’s crucial to have a goal in mind, a clear set of questions planned, and an understanding of how those questions may deviate from the intended goal. An interview has an intended line of questioning; it may also have alternate lines of questioning and unanticipated paths where the interviewee has raised issues or answered questions in a way the business analyst had not considered or planned. In short, an interview is a social process.