RUP iteration planning
|
|
- Madlyn Gallagher
- 7 years ago
- Views:
Transcription
1 Page 1 of 13 Copyright IBM Corporation Search for: within All of dw Use + - ( ) " " Search help IBM home Products & services Support & downloads My account developerworks > Rational RUP iteration planning Anthony Crain IBM 12 Jul 2004 from The Rational Edge: This article traces the steps required to plan sequential software project iterations while following the IBM Rational Unified Process. The author illustrates RUP templates and associated workflows in order to produce a plan relevant to the essential RUP disciplines. When planning an iteration using IBM Rational Unified Process, or RUP, people often get confused about how to start. Although templates in RUP itself and MS Project tools can help auto-generate a RUP style plan, creating a plan manually can really help you understand and manage your RUP iteration. Contents: Input artifacts Creating the iteration plan Summary Notes About the author Rate this article Subscriptions: dw newsletters dw Subscription (CDs and downloads) In this article I will show how simple it is to create an accurate iteration plan using the basic RUP toolset. Input artifacts To create your iteration plan you really only need two basic inputs. First, you need to know what RUP phase the planned iteration belongs to, and second, you need a well-written RUP development case. Knowing the phase will allow you to create the right kind of plan. Having the development case will tell you exactly what the plan should contain. Development case redefined Creating a plan from a development case is actually fairly easy, as you will see, once we understand what this artifact is all about. I have been told by RUP enthusiasts that the development case artifact is not useful. This is wildly untrue. In fact, I will show you how it can single-handedly drive your project management planning. I will note that, as with almost every RUP template I ve ever used, the development case artifact could be improved. However, don t misinterpret that statement. RUP templates are far better than anything I could create from scratch. But given their elevated starting point, along with my ability to architect information for maximum communication, I see room for improvement. Naturally, each of us brings great experience to the table that we can use to improve a basic set of artifacts. And if we don t keep reusing and improving each others' basic artifacts i.e., starting points we will always be starting from scratch and will only get so far in our effort. By launching ourselves from someone else s starting point we can fly high indeed and start to create world class artifacts. Therefore, to create a fully optimized development case artifact, I started with the RUP template. You will notice that RUP is heavily artifact-focused, yet there is little guidance on how to use those artifacts differently in each phase. The definition in RUP for the development case states: The development case describes the development process that you have chosen to follow in your project. So the artifact focus of the development case template doesn t completely reflect its definition. In my current best practice development case template, I recommend focusing on what workflow details you plan to execute, then focus on the artifacts within the context of each workflow detail. If you are not sure what a workflow detail is, click on any RUP discipline, and the activity diagram will show the workflow details. For example, there are only six workflow details in the Requirements discipline. The Rational Edge--June 2004
2 Page 2 of 13 Figure 1: The RUP Requirements workflow Note that the RUP discipline workflow diagrams (which are actually stereotyped UML activity diagrams) cover one iteration from the point of view of this discipline. The start state at the top is the start of the iteration, and the end state is the end of the iteration. Some misinterpret this as the start and end of the project, a throwback from waterfall thinking; or they mistake this as the start and end of the discipline, assuming that each discipline occurs in chronological order. In other words, some assume that the end state depicted here precedes the start state of the Analysis and Design workflow, but that isn t necessarily true. By acknowledging that this is the start and end of the iteration, and not the project, we can encourage more parallel work, and study the dependencies between tasks. Therefore, these activity diagrams drive iterative project planning. Writing the development case As I mentioned, to create your iteration plan, you will need a development case. Therefore, it is important that you ensure it gets completed quickly and correctly. It shouldn t take but a few hours for a new team to assemble a first draft for the current iteration. To write the development case, assign the nine disciplines (or the subset of disciplines you are using on your project if not all nine) to the most appropriate team members. Their job is to look at the workflow details and decide which ones they will actually need to execute, and which ones they won t. At first it feels like you have to know a lot about RUP to make that judgment, but that isn t necessarily the case. Knowing the definitions of the four RUP phases may be all you really need. Let s look at an example.
3 Page 3 of 13 Figure 2: The RUP Requirements workflow Tasks on plan Given that the Inception phase involves creating a first-cut usage model of the solution and establishing the measurable value of the solution idea but not gathering the detailed requirements, the question becomes: Which of the workflow details shown in Figure 2 (which is identical to Figure 1) will you need? Let s consider what each of these workflow details requires. Analyze the problem is about agreeing on the problem and creating the measures that will prove its value to the organization. Understand stakeholder needs is about sharing the problem and value with key stakeholders and finding out what their needs are surrounding the solution idea. Define the system is about creating features from needs and outlining use cases, activities which show nicely the high-level requirements and the overall usage model of the system. Manage the scope of the system is about modifying the scope of what you will deliver based on results so far and selecting the order in which to attack the use-case flows. Refine the system definition is about detailing use-case flows with the stakeholders in order to create a detailed Software Requirement Specification (SRS) that can serve as the contract between your team and your client and that can drive design and test activities. Manage changing requirements is about how to handle incoming requirement changes once the project has begun.
4 Page 4 of 13 Based on these descriptions and the description of Inception, I would probably expect analyze the problem, understand stakeholder needs, define the system, and manage the scope of the system to be planned for the first inception iteration, but not the other two workflow details. If Inception had more than one iteration I might see manage changing requirements kicking in, but still not refine the system definition. Your decisions might be different and it might also differ for each project under your care. It is not the project manager s job to decide which workflow details to perform in each iteration; it is the team s decision. Basically, the job of the project manager comes down to three tasks, and everything else folds up into them: 1. Plan/Re-Plan 2. Track to Plan 3. Manage Risks to the Plan. That s pretty much it. I consider status activities part of tracking-to-plan. And I m open to disagreement on this simplification. After the team decides what to do via a development case, the project manager should create the plan from the development case they create. Let s consider one more example of how to tailor the generic RUP workflow based on the current RUP phase, this time using the Analysis and Design workflow in RUP. Figure 3: The RUP Analysis and Design workflow Picking which workflow details to include in the development case for the Inception phase is easy, even without individual descriptions of each workflow detail. The activity diagram (Figure 3) clearly indicates that in the Inception phase the only workflow detail needed is to perform architectural synthesis, which is an ugly term for building an architectural proof of concept. As shown in Figure 3, this workflow detail is optional; however, my projects rarely skip this step. The workflow detail perform architectural synthesis consists of two major steps: 1) deciding if you need a proof of concept, and then 2) building it if you decide you needed one. Most projects need to analyze their risks to determine if a proof of concept is needed, and there are some great best practices to help you make this decision. Therefore, deciding on the need for a proof of concept is not a step that is usually skipped, and I don t see perform architectural synthesis as more optional than the other five workflow details in Figure 3 for most projects. The optional guard is likely tied to the fact that most projects do NOT need an Inception proof of concept, so the building portion of perform architectural synthesis is optional and frequently skipped in the Inception phase. In the Elaboration phase, teams build an incremental release (internal or external) that proves the chosen solution architecture can
5 Page 5 of 13 support the requirements of the solution. This requires taking the highest-risk requirements all the way through code to test and possibly internal or external deployment. Given this, we will probably need all five of the other workflow details in the Elaboration phase. During the Construction phase, we build the rest of the flows that we didn t build as part of elaboration, and we are no longer worried about architecture, focused instead on delivering the highest value solution possible. Based on this, we probably would only need analyze behavior, design components, and design the database. During the Transition phase, when we are supporting the solution once it has been fully deployed, we would use the same activities as in Construction; but the focus would be more on change requests than use cases. You can repeat this exercise for the workflow details of the Requirements discipline shown above and for all of the other seven disciplines of RUP. The best part is that you don t need to do this for all four phases at once! Remember that writing the development case and planning based on it is iterative, so you can focus on this iteration only and, therefore, only on the current phase. If the next iteration on the plan will belong to the next RUP phase, then you can proceed to detail your next phase in your development case. This is easier, quicker, and more accurate than waterfall planning for an entire project at once. Children tasks If you do the above for each workflow it shouldn t take too long to create a development case for a single phase. But we do need to add a few children tasks. Many managers try to add the activities within each workflow detail, but in general this will cause problems. First, this will result in significant delays to creating your plan, as there are an awful lot of activities within the workflow details. You will likely spend more time planning some of these tasks than implementing them. You can create a very manageable plan without that added level of detail. Second, many of the activities repeat in different workflow details. Just check out the first four workflow details in the requirements discipline, and you will see the develop vision activity appear every time, with no indication of what is different in each RUP phase. So I recommend that you avoid using the RUP activities on your project plan. On the other hand, we do need to understand what resources are being applied to what tasks. So instead of making each activity a child task to the workflow detail in our development case, we should create one child task per role involved in the workflow detail that we plan to use. Let s look at some examples. Figure 4: Details for the Perform Architectural Synthesis workflow detail
6 Page 6 of 13 Notice in Figure 4, in the yellow rectangle, that there is only one resource with three activities. In this case we do not need to add any children tasks to the plan, as the single role will handle all activities. Figure 5: Details for the Define a Candidate Architecture workflow detail In the workflow detail shown in Figure 5, we have two participants: the software architect and the designer. So we will create two child tasks for this workflow detail. We need to invent names to represent each subtask on the plan. If the activity does not repeat, we can use its name directly. Architectural analysis does repeat, but only in perform architectural synthesis; so we can call this child task architectural analysis here, because we haven t already used that name. Use-case analysis, on the other hand, occurs in so many workflow details that we avoid using that name. We chose use key abstractions instead. That is, we know from experience that using key abstractions is one of the major concepts of this step. Until you gain similar experience you will have to make your best guess. Another way to look at this is that we are creating children tasks per yellow area, not per activity. We then abstract a new name based on the whole yellow area s purpose. We can use the activity name if it occurs uniquely within RUP. In my opinion, RUP authors should not reuse activity names, but this approach allows me to manage that for myself. Knock-off tasks The last step after finding the children tasks is to list key "knock-off tasks" in the development case and to include key input or output artifacts as well. A list of knock-off tasks is like a to-do list of small objectives. (If you don t like the term knock-off task, you can use a different one, but it should indicate that the list includes fairly granular to-do items.)
7 Page 7 of 13 Identifying the knock-off tasks is an area in which a consultant or someone with significant RUP experience can dramatically reduce the time to value. We are NOT trying to duplicate RUP here. We are simplifying RUP considerably in this step. You will still need to use RUP for additional details. Here are a couple of examples. For Analysis and Design, the knock-off tasks for each workflow detail might look like the list in Table 1, which I ve taken from the standard development case I give to my clients. Table 1: A simple development case
8 Page 8 of 13
9 Page 9 of 13 This standard example is fairly simple. It does not describe the input and output artifacts, but this amount of detail is extremely valuable to the team. And although this development case is fairly simplistic, it fits on a single page, which also can be an advantage to a new team. 1 Table 2 shows more complex entry for a single workflow detail in the project management discipline. This is taken from another development case template that I share with my clients (note that the business context in Table 2 is different from that in Table 1). Table 2: A more complex entry for a single workflow detail Conceive New Project Knock-off tasks Purpose Role Average time Established environment New environment Write business case Write Risk List Share with PRA and gain funding for Inception phase Purpose is to justify funding by putting together a quick document to show the idea for the project. In the future, new team members can read this to see how the project has been positioned to the PRA, and to get a high-level introduction to the system. The business case will be updated at each iteration. The risk list will be updated often. Project manager 1 day 1 day Input Artifacts: None Output Artifacts: business case, risk list, review record funding inception Tools: IBM Rational ClearQuest for risk list, Word for business case, with acceptance for review record In the example shown in Table 2, far more detail has been provided. This level of detail evolved over time. Trying to get to this level of detail on every workflow detail at once would take more time than our projects have to spare. Remember, while it is the job of the project manager to ensure a development case is written to guide their planning, the team that will be following the plan should create the development case together. This is how the team influences what gets placed on the plan. Creating the iteration plan At this point you should have the development case in place. You have probably figured out that creating the work breakdown structure won t be hard once the development case is written. But there are still a few final tips and thoughts I d like to share. Using a planning tool, such as Microsoft Project, you will find it simple to place each workflow detail onto the plan. On previous projects I have tried two different approaches for organizing the work breakdown structure (using Gantt charts like the one in Figure 6 below). I ve tried to organize the tasks on the plan in chronological order, and I ve tried organizing the tasks by discipline. These two approaches have different advantages and drawbacks. Let s take a look at an actual project in which our current best practices for laying out the tasks in the work breakdown structure were determined in RUP. Grouping tasks: A lesson in confusion In chronological order, the plan might appear as depicted in Figure 6. Based on an actual project on which I was a consultant, each task was color coded to match (as closely as possible using MS Project s color palette) the colors of the RUP disciplines.
10 Page 10 of 13 Figure 6: Iteration plan organized chronologically While you can t easily read the details of this plan, you can tell by the colors, and by the position of the Gantt chart bars, that this plan was not organized by discipline but rather by time. Each task precedes or starts with the next one. For example, the first two tasks are in the project manager discipline, and so are the last two. Clearly, the PM discipline tasks were not grouped. Using a sequential order gave project managers a clearer understanding of what came next in this project, but it became difficult to reconcile this sequence with the development case because the development case was grouped according to discipline in other words, all the project manager tasks were together, all of the requirement tasks were together, and so forth. The table of contents based on that development case is shown in Table 3 below. Table 3: A development case organized by discipline
11 Page 11 of 13 So the plan was in sequential order, but the development case was in discipline order, and the project managers had a harder time trying to reconcile the two. To fix this problem, the project managers attempted to modify the template so that the workflow details were in sequential order to better match the iteration plan. The table of contents then looked more like Table 4. Table 4: Development case reorganized by sequence
12 Page 12 of 13 This worked well for planning because the project managers could, for the most part, cut and paste the table of contents into their project plan. But now it became harder for the rest of the team to find the tasks they owned, since they were no longer logically grouped, so ultimately this was deemed a poor choice. We saved the template, of course, to remind ourselves of the attempt. By the way, the current recommendation for iteration plans in RUP is to organize both the plan and the development case by discipline. Writing queries to identify critical tasks During that project, we also created a few Microsoft Project queries to help the project managers look for a clear, single view of interdependent tasks. This is because the plans could span pages vertically, and a task listed low on a given page might be slated for the first week with many entries for subsequent weeks above it. The queries are easy to write: List all tasks starting this week (or whatever dates you choose), list all tasks ending this week, and list all tasks ongoing this week. The project manager would then run these three queries and print out the results, then proactively wander around to the team asking Are you going to start this on time? Are you going to complete this on time? How are these items going? How can I help? Using the RUP work order In addition to the workflow details, I recommend that you put in the role-specific children tasks as well, and assign them the appropriate resources. But DON T put in the knock-off tasks, or your plan will be too granular to manage well. It will take too long to create and will be difficult to modify when changes become necessary. Instead, use another RUP artifact called the work order, which RUP defines as follows: The work order is the project manager's means of communicating what is to be done, and when, to the responsible staff. It becomes an internal contract between the Project Manager and those assigned responsibility for completion. It goes on to say you can use a whiteboard, and the project plan for tracking, or use IBM Rational ClearQuest to track them automatically. The idea is you jot down the knock-off tasks with the resource responsible for the task separate from the project plan. When the knock-off tasks are done, the work order is complete and we mark it complete in MS Project. There is even an integration between MS Project and ClearQuest that allows you to plan in MS Project, generate work order records, and have the plan update itself when the work orders are marked complete in ClearQuest. Another technique is to assign all the work orders to the team member, who can jump from one to another if the work orders get blocked, raising any needed risks (also via IBM Rational ClearQuest) in the process. If a team member ever runs out of work orders he can camp out in front of the PM s office with a sandwich until he gets new ones, or he can switch to another project and get new work orders from different managers. The point is this: If you plan too deeply, your planning will simply take too long and be difficult to manage and track against. Work orders can give you the granular level of management you need without the overhead.
13 Page 13 of 13 Summary A well-written development case should show the project s process not just the artifacts. The process is described by outlining which workflow details the project will be targeting. The project team writes the development case. The project manager uses the development case to create a work breakdown structure in his preferred tool and works with the team to assign times and dependencies. The plan should not detail the activity level but should have one subtask per workflow detail if there is more than one role involved. The development case should list detailed knock-off tasks for each task, but these should not be in the iteration plan. Instead, work orders should be used to track the more granular knock-off tasks. Notes 1 In appearance, this development case differs widely from the standard RUP template in that it doesn t discuss artifacts at all. See my article on the artifacts of Analysis and Design to understand the three artifacts you will need to use for all six of these steps. About the author Anthony Crain is a software engineering specialist with the IBM Rational Services Organization. In addition to helping clients roll out the IBM Rational Unified Process, or RUP, he also trains engineers in requirements management with use cases, Object-Oriented Analysis and Design (OOAD), and RUP. He learned OOAD and use-case modeling while at Motorola for five years, then sharpened his skills at Rational. An honors graduate from Northern Arizona University, he holds a B.S. in computer science and engineering. What do you think of this document? Killer! (5) Good stuff (4) So-so; not bad (3) Needs work (2) Lame! (1) Comments? Submit feedback developerworks > Rational About IBM Privacy Terms of use Contact
Basic Unified Process: A Process for Small and Agile Projects
Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.
More informationChapter 3. Technology review. 3.1. Introduction
Technology review Chapter 3 3.1. Introduction Previous chapter covers detail description about problem domain. In this chapter I will discuss the technologies currently available to solve a problem in
More informationUser experience storyboards: Building better UIs with RUP, UML, and use cases
Copyright Rational Software 2003 http://www.therationaledge.com/content/nov_03/f_usability_jh.jsp User experience storyboards: Building better UIs with RUP, UML, and use cases by Jim Heumann Requirements
More informationThe Rap on RUP : An Introduction to the Rational Unified Process
The Rap on RUP : An Introduction to the Rational Unified Process Jeff Jacobs Jeffrey Jacobs & Associates phone: 650.571.7092 email: jeff@jeffreyjacobs.com http://www.jeffreyjacobs.com Survey Does your
More informationHow To Adopt Rup In Your Project
08Bergstrom.C08 Page 127 Thursday, December 4, 2003 12:06 PM 8 How to Adopt RUP in Your Project Support Projects with Mentoring Make a High-Level Adoption Plan and Develop a Communication Plan Project
More informationThe role of integrated requirements management in software delivery.
Software development White paper October 2007 The role of integrated requirements Jim Heumann, requirements evangelist, IBM Rational 2 Contents 2 Introduction 2 What is integrated requirements management?
More informationProcess Streamlining. Whitepapers. Written by A Hall Operations Director. Origins
Whitepapers Process Streamlining Written by A Hall Operations Director So, your processes are established and stable, but are clearly inefficient and you are not meeting your performance expectations.
More informationLeveraging RUP, OpenUP, and the PMBOK. Arthur English, GreenLine Systems
Software Project Management Leveraging RUP, OpenUP, and the PMBOK Arthur English, GreenLine Systems GreenLine Systems Inc. 2003 2013 My Background 30+ years of IT project management experience with both
More informationSTEP 5: Giving Feedback
STEP 5: Giving Feedback Introduction You are now aware of the responsibilities of workplace mentoring, the six step approach to teaching skills, the importance of identifying the point of the lesson, and
More informationGetting Started with WebSite Tonight
Getting Started with WebSite Tonight WebSite Tonight Getting Started Guide Version 3.0 (12.2010) Copyright 2010. All rights reserved. Distribution of this work or derivative of this work is prohibited
More informationMind Mapping Improves Software Requirements Quality, Communication and Traceability
Mind Mapping Improves Software Requirements Quality, Communication and Traceability A tech brief published by QAvantage Copyright 2008 QAvantage All trademarks referenced are the marks of their respective
More informationPersuasive. How to Write Persuasive. Social Media Proposals
Persuasive Social Media Proposals How to Write Persuasive Social Media Proposals How to Write Persuasive Social Media Proposals! You got started in social media because you wanted to connect with people
More informationRequirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
More informationThinking Skills. Lesson Plan. Introduction
xxx Lesson 18 Thinking Skills Overview: This lesson provides basic foundational information about two types of thinking skills: critical and creative. Students have used critical and creative skills each
More informationWorkflow and Process Analysis for CCC
Section 3.6 Design Workflow and Process Analysis for CCC This tool introduces the importance of workflow and process improvement in a community-based care coordination (CCC) program, describes the value
More informationSupporting Workflow Overview. CSC532 Fall06
Supporting Workflow Overview CSC532 Fall06 Objectives: Supporting Workflows Define the supporting workflows Understand how to apply the supporting workflows Understand the activities necessary to configure
More informationChap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
More informationManaging Agile Projects in TestTrack GUIDE
Managing Agile Projects in TestTrack GUIDE Table of Contents Introduction...1 Automatic Traceability...2 Setting Up TestTrack for Agile...6 Plan Your Folder Structure... 10 Building Your Product Backlog...
More informationIn this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?
In this Lecture you will Learn: Systems Development Methodologies What a systems development methodology is Why methodologies are used The need for different methodologies The main features of one methodology
More informationThe «include» and «extend» Relationships in Use Case Models
The «include» and «extend» Relationships in Use Case Models Introduction UML defines three stereotypes of association between Use Cases, «include», «extend» and generalisation. For the most part, the popular
More informationIT Governance In The Cloud: Building A Solution Using Salesforce.com
WHITE PAPER IT Governance In The Cloud: Building A Solution Using Salesforce.com By Jason Atwood and Justin Edelstein Co-Founders, Arkus, Inc. Cloud computing has the potential to create a new paradigm
More informationTHE AGILE WATERFALL MIX DELIVERING SUCCESSFUL PROGRAMS INVOLVING MULTIPLE ORGANIZATIONS
THE AGILE WATERFALL MIX DELIVERING SUCCESSFUL PROGRAMS INVOLVING MULTIPLE ORGANIZATIONS Amit Aggarwal FIS Consulting Services 800.822.6758 Overview The fintech explosion, the Internet of Things and the
More informationObject-oriented design methodologies
Object-oriented design methodologies An object-oriented methodology is defined as the system of principles and procedures applied to object-oriented software development. Five years ago, there was no standard
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 15 Agile Methodologies: AUP 1 Agile Unified Process (AUP) Proposed by Ambler as a simplified version of the Rational Unified Process (RUP).
More information44-76 mix 2. Exam Code:MB5-705. Exam Name: Managing Microsoft Dynamics Implementations Exam
44-76 mix 2 Number: MB5-705 Passing Score: 800 Time Limit: 120 min File Version: 22.5 http://www.gratisexam.com/ Exam Code:MB5-705 Exam Name: Managing Microsoft Dynamics Implementations Exam Exam A QUESTION
More informationA GUIDE TO PROCESS MAPPING AND IMPROVEMENT
A GUIDE TO PROCESS MAPPING AND IMPROVEMENT Prepared by the CPS Activity Based Costing Team December 2012 CONTENTS 1. Introduction Page 3 2. What is process mapping? Page 4 3. Why process map? Page 4 4.
More information3C05: Unified Software Development Process
3C05: Unified Software Development Process 1 Unit 5: Unified Software Development Process Objectives: Introduce the main concepts of iterative and incremental development Discuss the main USDP phases 2
More informationPlan-Driven Methodologies
Plan-Driven Methodologies The traditional way to develop software Based on system engineering and quality disciplines (process improvement) Standards developed from DoD & industry to make process fit a
More informationProject Management in the Rational Unified Process
CS2 Software Engineering note 3 Project Management in the Rational Unified Process In the last two Software Engineering lectures we have considered the outline description of the Rational Unified Process
More informationA Guide to Cover Letter Writing
A Guide to Cover Letter Writing Contents What is a Cover Letter?... 2 Before you get started - Do your Research... 3 Formatting the letter... 4 Cover letter content... 5 Section 1 - Opening... 5 Section
More informationThe Five Levels of Requirements Management Maturity
Copyright Rational Software 2003 http://www.therationaledge.com/content/feb_03/f_managementmaturity_jh.jsp The Five Levels of Requirements Management Maturity by Jim Heumann Requirements Evangelist Rational
More informationCase study: Improving performance in HR London Camden
Case study: Improving performance in HR London Camden The London Borough of Camden is in the heart of London and employs over 5,000 people. The borough s HR directorate has a major influence on the core
More informationISO 9001:2000 Its Impact on Software
ISO 9001:2000 Its Impact on Software Norman P. Moreau, PE, CSQE, CQA Theseus Professional Services, LLC Westminster, Maryland 410-857-0023 / nmoreau@erols.com / http://theseuspro.com Presented to American
More informationAvatar: Appearance Changing Your Shape. 1-1.2 Introduction. 1-1.2.1 Instruction. 1-1.2.2 Practice LEVEL: 1 MODULE: AVATAR: APPEARANCE MISSION 2
Avatar: Appearance Changing Your Shape LEVEL: 1 MODULE: AVATAR: APPEARANCE MISSION 2 1-1.2 Introduction Now that you have a default avatar, it s time to start customizing it to your liking! Fortunately,
More informationDevelopment Methodologies. Types of Methodologies. Example Methodologies. Dr. James A. Bednar. Dr. David Robertson
Development Methodologies Development Methodologies Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar Dr. David Robertson dr@inf.ed.ac.uk http://www.inf.ed.ac.uk/ssp/members/dave.htm
More informationFive Core Principles of Successful Business Architecture
Five Core Principles of Successful Business Architecture Authors: Greg Suddreth and Whynde Melaragno Strategic Technology Architects (STA Group, LLC) Sponsored by MEGA Presents a White Paper on: Five Core
More informationProcess Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
More informationDeveloping SOA solutions using IBM SOA Foundation
Developing SOA solutions using IBM SOA Foundation Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 4.0.3 4.0.3 Unit objectives After completing this
More informationEasy Casino Profits. Congratulations!!
Easy Casino Profits The Easy Way To Beat The Online Casinos Everytime! www.easycasinoprofits.com Disclaimer The authors of this ebook do not promote illegal, underage gambling or gambling to those living
More informationFormally speaking: How to apply OCL
Page 1 of 6 Copyright IBM Corporation 2004 http://www-106.ibm.com/developerworks/rational/library/5390.html Search for: within All of dw Use + - ( ) " " Search help IBM home Products & services Support
More informationClub Accounts. 2011 Question 6.
Club Accounts. 2011 Question 6. Anyone familiar with Farm Accounts or Service Firms (notes for both topics are back on the webpage you found this on), will have no trouble with Club Accounts. Essentially
More informationAction Steps for Setting Up a Successful Home Web Design Business
Action Steps for Setting Up a Successful Home Web Design Business In this document you'll find all of the action steps included in this course. As you are completing these action steps, please do not hesitate
More informationPractical Strategy and Workflow for Large Projects: A Realistic Solution
Practical Strategy and Workflow for Large Projects: A Realistic Solution Marco Brasiel/Diego Faria Frazillio & Ferroni SE3193 This class presents a strategy for development of structural projects using
More informationIncreasing Development Knowledge with EPFC
The Eclipse Process Framework Composer Increasing Development Knowledge with EPFC Are all your developers on the same page? Are they all using the best practices and the same best practices for agile,
More informationComputer Training Centre University College Cork
Computer Training Centre University College Cork Project 2013 Table of Contents What's new in Project 2013... 1 Manual scheduling... 1 Graphical Reports... 1 Trace task paths... 1 Easier view customization...
More informationXtreme RUP. Ne t BJECTIVES. Lightening Up the Rational Unified Process. 2/9/2001 Copyright 2001 Net Objectives 1. Agenda
Xtreme RUP by Ne t BJECTIVES Lightening Up the Rational Unified Process 2/9/2001 Copyright 2001 Net Objectives 1 RUP Overview Agenda Typical RUP Challenges Xtreme Programming Paradigm Document driven or
More informationHow To Proofread
GRADE 8 English Language Arts Proofreading: Lesson 6 Read aloud to the students the material that is printed in boldface type inside the boxes. Information in regular type inside the boxes and all information
More informationTips for writing good use cases.
Transforming software and systems delivery White paper May 2008 Tips for writing good use cases. James Heumann, Requirements Evangelist, IBM Rational Software Page 2 Contents 2 Introduction 2 Understanding
More informationPage 18. Using Software To Make More Money With Surveys. Visit us on the web at: www.takesurveysforcash.com
Page 18 Page 1 Using Software To Make More Money With Surveys by Jason White Page 2 Introduction So you re off and running with making money by taking surveys online, good for you! The problem, as you
More information1. The Fly In The Ointment
Arithmetic Revisited Lesson 5: Decimal Fractions or Place Value Extended Part 5: Dividing Decimal Fractions, Part 2. The Fly In The Ointment The meaning of, say, ƒ 2 doesn't depend on whether we represent
More informationUsing Use Cases for requirements capture. Pete McBreen. 1998 McBreen.Consulting
Using Use Cases for requirements capture Pete McBreen 1998 McBreen.Consulting petemcbreen@acm.org All rights reserved. You have permission to copy and distribute the document as long as you make no changes
More informationFidelity National Financial Drives Improvements in Software Development and Reuse with IBM Rational Software Development Platform and Flashline
IBM Customer Success Fidelity National Financial Drives Improvements in Software Development and Reuse with IBM Rational Software Development Platform and Flashline Overview The Challenge Following a series
More informationQuality Meets the CEO
Quality Meets the CEO Jeffery E. Payne jepayn@rstcorp.com Reliable Software Technologies Corporate management does not care about quality. This is the cold, hard reality of the software world. Management
More informationProcess Discovery The First Step of BPM
Process Discovery The First Step of BPM Table of Contents Introduction... 3 Process Discovery Challenges... 3 The Problems with Current Options... 5 A New Approach to Discovery... 6 Your Next Step... 9
More informationUsing games to support. Win-Win Math Games. by Marilyn Burns
4 Win-Win Math Games by Marilyn Burns photos: bob adler Games can motivate students, capture their interest, and are a great way to get in that paperand-pencil practice. Using games to support students
More informationRedesigned Framework and Approach for IT Project Management
Vol. 5 No. 3, July, 2011 Redesigned Framework and Approach for IT Project Management Champa Hewagamage 1, K. P. Hewagamage 2 1 Department of Information Technology, Faculty of Management Studies and Commerce,
More informationRUP and XP, Part I: Finding Common Ground
RUP and XP, Part I: Finding Common Ground by Gary Pollice Evangelist, The Rational Unified Process Rational Software extreme Programming (XP) is hot! Attend any software development conference today and
More informationThe Dynamics of Project Management
The PROJECT PERFECT White Paper Collection Abstract The Dynamics of Project Management Eric Tse This white paper suggests project management methods and practices can move from a static, unidirectional
More informationPlanning and Writing Essays
Planning and Writing Essays Many of your coursework assignments will take the form of an essay. This leaflet will give you an overview of the basic stages of planning and writing an academic essay but
More informationNPI Number Everything You Need to Know About NPI Numbers
NPI Number Everything You Need to Know About NPI Numbers By Alice Scott and Michele Redmond What is an NPI number, who needs one, how do you get one, when do you need two NPI # s, what is a taxonomy code
More informationThe Software Process. The Unified Process (Cont.) The Unified Process (Cont.)
The Software Process Xiaojun Qi 1 The Unified Process Until recently, three of the most successful object-oriented methodologies were Booch smethod Jacobson s Objectory Rumbaugh s OMT (Object Modeling
More informationTHEME: T-ACCOUNTS. By John W. Day, MBA. ACCOUNTING TERM: T-Account
THEME: T-ACCOUNTS By John W. Day, MBA ACCOUNTING TERM: T-Account A T-Account is a template or format shaped like a T that represents a particular general ledger account. Debit entries are recorded on the
More informationTo download the script for the listening go to: http://www.teachingenglish.org.uk/sites/teacheng/files/learning-stylesaudioscript.
Learning styles Topic: Idioms Aims: - To apply listening skills to an audio extract of non-native speakers - To raise awareness of personal learning styles - To provide concrete learning aids to enable
More informationHandouts for teachers
ASKING QUESTIONS THAT ENCOURAGE INQUIRY- BASED LEARNING How do we ask questions to develop scientific thinking and reasoning? Handouts for teachers Contents 1. Thinking about why we ask questions... 1
More informationWRITING EFFECTIVE REPORTS AND ESSAYS
WRITING EFFECTIVE REPORTS AND ESSAYS A. What are Reports? Writing Effective Reports Reports are documents which both give a reader information and ask the reader to do something with that information.
More informationSample Cover Letter Format
Sample Cover Letter Format Your Contact Information Name Address City, State, Zip Code Phone Number Email Address (Times New Roman font, 11-12 point) Date Employer Contact Information (if you have it)
More informationREVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS
REVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS Lisana Universitas Surabaya (UBAYA), Raya Kalirungkut, Surabaya, Indonesia E-Mail: lisana@ubaya.ac.id
More informationUpgrade from Sage Instant Accounts v15
Upgrade from Sage Instant Accounts v15 Sage Instant Accounts 2014 is the market-leading software that puts you in control of your cashflow. Whether you re dealing with quotes and invoices, customers or
More informationSales Training Programme. Module 7. Objection handling workbook
Sales Training Programme. Module 7. Objection handling workbook Workbook 7. Objection handling Introduction This workbook is designed to be used along with the podcast on objection handling. It is a self
More informationDevelopment Methodologies
Slide 3.1 Development Methodologies Prof. Dr. Josef M. Joller jjoller@hsr.ch Development Methodologies Prof. Dr. Josef M. Joller 1 Session 3 Slide 3.2 SOFTWARE LIFE-CYCLE MODELS Development Methodologies
More informationMSP How to guide session 2 (Resources & Cost)
MSP How to guide session 2 (Resources & Cost) 1. Introduction Before considering resourcing the schedule it is important to ask yourself one key question as it will require effort from the scheduler or
More informationProject, Portfolio Management (PPM) for the Enterprise Whose System is it Anyway?
Project, Portfolio Management (PPM) for the Enterprise Whose System is it Anyway? Protecting Your Investment with a Bottom-up Approach Revised December 2012 Heather Champoux, PMP http://epmlive.com Contents
More informationThe value of modeling
The value of modeling Level: Introductory Gary Cernosek, Marketing Manager, IBM Rational Eric Naiburg, Group Market Manager Desktop Products, IBM Rational 15 Nov 2004 from The Rational Edge: This article
More informationProject Time Management
Project Skills Team FME www.free-management-ebooks.com ISBN 978-1-62620-981-3 Copyright Notice www.free-management-ebooks.com 2014. All Rights Reserved ISBN 978-1-62620-981-3 The material contained within
More informationEp #19: Thought Management
Full Episode Transcript With Your Host Brooke Castillo Welcome to The Life Coach School podcast, where it s all about real clients, real problems and real coaching. And now your host, Master Coach Instructor,
More informationIntroduction to Systems Analysis and Design
Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.
More informationTeacher Evaluation Using the Danielson Framework 6. A Professional Portfolio: Artifact Party A. Using Artifacts to Help Determine Performance Levels
Teacher Evaluation Using the Danielson Framework 6. A Professional Portfolio: Artifact Party A. Using Artifacts to Help Determine Performance Levels Artifact Party Guidelines CHARLOTTE DANIELSON: Of course,
More informationSpecial Reports. Finding Actionable Insights through AdWords Reporting
Special Reports Finding Actionable Insights through AdWords Reporting Introduction We re closer than we ve ever been to understanding which aspects of our marketing work. Impressions, clicks, conversions
More informationStarting Your Fee Based Financial Planning Practice From Scratch (Part 2) FEE008
Starting Your Fee Based Financial Planning Practice From Scratch (Part 2) FEE008 Episode Transcript Host: Scott Plaskett, CFP Okay. So let s get onto the feature segment. And this is a continuation from
More informationMOST FREQUENTLY ASKED INTERVIEW QUESTIONS. 1. Why don t you tell me about yourself? 2. Why should I hire you?
MOST FREQUENTLY ASKED INTERVIEW QUESTIONS 1. Why don t you tell me about yourself? The interviewer does not want to know your life history! He or she wants you to tell how your background relates to doing
More informationIn this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice
In this Lecture you will Learn: Development Chapter 5C About the Unified Software Development How phases relate to workflows in an iterative life cycle An approach to system development Major activities
More informationModellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 18-19 The Unified Process Static dimension Glossary UP (Unified
More informationRingCentral for Desktop. UK User Guide
RingCentral for Desktop UK User Guide RingCentral for Desktop Table of Contents Table of Contents 3 Welcome 4 Download and install the app 5 Log in to RingCentral for Desktop 6 Getting Familiar with RingCentral
More informationGlobal Software Update Rollout: Global Learning Management System
Journal of IT and Economic Development 5(2), 18-31, October 2014 18 Global Software Update Rollout: Global Learning Management System Heather Budriss, Tamikia Life, Denise Sarpong, Cham Williams College
More informationMath 4310 Handout - Quotient Vector Spaces
Math 4310 Handout - Quotient Vector Spaces Dan Collins The textbook defines a subspace of a vector space in Chapter 4, but it avoids ever discussing the notion of a quotient space. This is understandable
More informationDesigning a Marketing Email That Works
Designing a Marketing Email That Works Tips for designing marketing emails that get opened and help your business grow. 2013 Copyright Constant Contact, Inc. 13-3450 2013 Copyright Constant Contact, Inc.
More informationCHAPTER 1: INTRODUCTION TO RAPID APPLICATION DEVELOPMENT (RAD)
CHAPTER 1: INTRODUCTION TO RAPID APPLICATION DEVELOPMENT (RAD) 1. INTRODUCTIONS RAD refers to a development life cycle designed Compare to traditional life cycle it is Faster development with higher quality
More informationThe Power of Relationships
The Power of Relationships How to build long-lasting customer relationships to help you do more business 2014 Copyright Constant Contact, Inc. 14-3931 v1.0 Helping Small Business Do More Business When
More informationDynamics CRM for Outlook Basics
Dynamics CRM for Outlook Basics Microsoft Dynamics CRM April, 2015 Contents Welcome to the CRM for Outlook Basics guide... 1 Meet CRM for Outlook.... 2 A new, but comfortably familiar face................................................................
More informationThe Stacks Approach. Why It s Time to Start Thinking About Enterprise Technology in Stacks
The Stacks Approach Why It s Time to Start Thinking About Enterprise Technology in Stacks CONTENTS Executive Summary Layer 1: Enterprise Competency Domains Layer 2: Platforms Layer 3: Enterprise Technology
More informationCREATIVE S SKETCHBOOK
Session Plan for Creative Directors CREATIVE S SKETCHBOOK THIS SKETCHBOOK BELONGS TO: @OfficialSYP 1 WELCOME YOUNG CREATIVE If you re reading this, it means you ve accepted the We-CTV challenge and are
More informationThe AEC Professional s Guide to Outsourcing BIM Management
The AEC Professional s Guide to Outsourcing BIM Management A good BIM manager is vital to an AEC firm s success. But what constitutes good BIM management? What does it mean to outsource BIM management,
More informationModerator: Albert Jeffrey Moore, ASA, MAAA. Presenters: Albert Jeffrey Moore, ASA, MAAA Kelly J. Rabin, FSA, MAAA Steven L. Stockman, ASA, MAAA
Session 59 PD, The Need for Agile Actuaries: Introduction to Agile Project Management Moderator: Albert Jeffrey Moore, ASA, MAAA Presenters: Albert Jeffrey Moore, ASA, MAAA Kelly J. Rabin, FSA, MAAA Steven
More information15 Most Typically Used Interview Questions and Answers
15 Most Typically Used Interview Questions and Answers According to the reports made in thousands of job interviews, done at ninety seven big companies in the United States, we selected the 15 most commonly
More informationUML basics. Part II: The activity diagram. The activity diagram's purpose. by Donald Bell IBM Global Services
Copyright Rational Software 2003 http://www.therationaledge.com/content/sep_03/f_umlbasics_db.jsp UML basics Part II: The activity diagram by Donald Bell IBM Global Services In June 2003, The Rational
More information(BA122) Software Engineer s Workshop (SEW)
Training for the Business Analyst (BA122) Software Engineer s Workshop (SEW) Duration: 4 days CDUs (Continuing Development Units): 28 Description: A practical workshop covering the role of the Business-Systems
More informationWeb Application Development Process
Web Engineering Web Application Development Process Copyright 2013 Ioan Toma & Srdjan Komazec 1 Where we are? # Date Title 1 5 th March Web Engineering Introduction and Overview 2 12 th March Requirements
More informationGrade 2 Lesson 3: Refusing Bullying. Getting Started
Getting Started Lesson Concepts You can refuse to let bullying happen to you or to others. Being assertive is one way to refuse bullying. Key Words Refuse, assertive Objectives Students will be able to:
More informationProgramming Lists of Data
Chapter 19 Programming Lists of Data As you ve already seen, apps handle events and make decisions; such processing is fundamental to computing. But the other fundamental part of an app is its data the
More informationSession 7 Fractions and Decimals
Key Terms in This Session Session 7 Fractions and Decimals Previously Introduced prime number rational numbers New in This Session period repeating decimal terminating decimal Introduction In this session,
More information