• Blog
  • Info Support
  • Career
  • Training
  • International Group
  • Info Support
  • Blog
  • Career
  • Training
  • International Group
  • Search
logo InfoSupport
  • Latest blogs
  • Popular blogs
  • Experts
      • All
      • Bloggers
      • Speakers
  • Meet us
  • About us
    • nl
    • en
    • .NET
    • 3D printing
    • Advanced Analytics
    • Agile
    • Akka
    • Alexa
    • Algorithms
    • Api's
    • Architectuur
    • Artificial Intelligence
    • ATDD
    • Augmented Reality
    • AWS
    • Azure
    • Big Data
    • Blockchain
    • Business Intelligence
    • Chatbots
    • Cloud
    • Code Combat
    • Cognitive Services
    • Communicatie
    • Containers
    • Continuous Delivery
    • CQRS
    • Cyber Security
    • Dapr
    • Data
    • Data & Analystics
    • Data Science
    • Data Warehousing
    • Databricks
    • DataOps
    • Developers life
    • DevOps
    • Digital Days
    • Digital Twin
    • Docker
    • eHealth
    • Enterprise Architecture
    • Event Sourcing
    • Hacking
    • Infrastructure & Hosting
    • Innovatie
    • Integration
    • Internet of Things
    • Java
    • Machine Learning
    • Microservices
    • Microsoft
    • Microsoft Bot Framework
    • Microsoft Data Platform
    • Mobile Development
    • Mutation Testing
    • Open source
    • Pepper
    • Power BI
    • Privacy & Ethiek
    • Python
    • Quality Assistance & Test
    • Quality Assurance & Test
    • Requirements Management
    • Scala
    • Scratch
    • Security
    • SharePoint
    • Software Architecture
    • Software development
    • Software Factory
    • SQL Server
    • SSL
    • Start-up
    • Startup thinking
    • Stryker
    • Test Quality
    • Testing
    • TLS
    • TypeScript
    • Various
    • Web Development
    • Web-scale IT
    • Xamarin
    • All
    • Bloggers
    • Speakers
Home » RUP and when to go to the next phase?
  • RUP and when to go to the next phase?

    • By Richard Zaat
    • Various 16 years ago
    • Various 0 comments
    • Various Various
    RUP and when to go to the next phase?

    RUP itself has some clear milestones, for each phase (Inception, Elaboration, Construction, Transition). Trouble is that you usually can't just say: I've saved the last document of Inception, now we are ready for Elaboration.

    Reaching a milestone is something which doesn't happen all of the sudden. And this means that closing out a phase is not always clear.  Have we really "All risks have been identified and a mitigation strategy exists for each." covered that part? How do you know? Have you really identified all the risks when you are confident you have taken all required actions to identify them? You will always have a feeling that it is possible that you missed something… and this usually makes closing out a phase difficult. At the end of Inception usually some of the projectmembers are already doing some elaboration work. So when can you continue to the next phase? As soon as someone starts taking up activities from the next phase? Or when all work from the current phase is completed?

    No. Closing out a phase is not binary (yes or no). It is a feeling that the milestone has been reached. This will probably leave some doubt whether the decision to go to the next phase was right or not. And that is why this decision should not only be taken by the projectmanager, but by everyone involved.

    I use phase assessments and evaluations. The evaluation is for the improvement of the team itself. The assessment is to see whether everyone agrees on the fact that the milestone has been reached. Talk about the indifferences. Write down the milestones, and ask each stakeholder if the milestone has been reached (let them give a rating of 1-5). If a milestone is 4 or higher, there is no need to discuss it. When the milestone reaches an average of 3, you have a discussion at hand. If it is below 3, you cannot continue to the next phase.

    The rating helps to change the gut feeling into something which can be discussed. So, discuss the milestone with the whole team (or at least the most important players within your team) and make a decision together.

    Sometimes our outcome is that we have reached the milestone, but only once a specific list of actions has been taken. In this case the assessment helps to set the focus for the short time period.

     

    Conclusion

    Decide together if you have reached the milestone. If not, make a list of actions required to reach the milestone anyway.

    Share this

Richard Zaat

View profile

IT Training at Info Support

Which training fits you?

Consultancy

Consultancy

Related blogs

  • Configuring SQL Server encrypted connections using Powe…

    Configuring SQL Server encrypted connections using Powe… Léon Bouquiet - 3 months ago

  • Video Conferencing en OBS Studio koppelen: online prese…

    Video Conferencing en OBS Studio koppelen: online prese… Maaike Brouwer - 3 years ago

  • Verantwoordelijkheid pakken in jouw eigen persoonlijke …

    Verantwoordelijkheid pakken in jouw eigen persoonlijke … Stephan Versteegh - 3 years ago

Data Discovery Channel

  • Data+AI Summit 2023

  • Blijf je Azure cloud omgeving de baas met CloudXcellence

  • MLOps

Nieuwsbrief

* verplichte velden

Contact

  • Head office NL
  • Kruisboog 42
  • 3905 TG Veenendaal
  • T +31 318 552020
  • Call
  • Mail
  • Directions
  • Head office BE
  • Generaal De Wittelaan 17
  • bus 30 2800 Mechelen
  • T +32 15 286370
  • Call
  • Mail
  • Directions

Follow us

  • Twitter
  • Facebook
  • Linkedin
  • Youtube

Newsletter

Sign in

Extra

  • Media Library
  • Disclaimer
  • Algemene voorwaarden
  • ISHBS Webmail
  • Extranet
Beheer cookie toestemming
Deze website maakt gebruik van Functionele en Analytische cookies voor website optimalisatie en statistieken.
Functioneel Always active
De technische opslag of toegang is strikt noodzakelijk voor het legitieme doel het gebruik mogelijk te maken van een specifieke dienst waarom de abonnee of gebruiker uitdrukkelijk heeft gevraagd, of met als enig doel de uitvoering van de transmissie van een communicatie over een elektronisch communicatienetwerk.
Voorkeuren
De technische opslag of toegang is noodzakelijk voor het legitieme doel voorkeuren op te slaan die niet door de abonnee of gebruiker zijn aangevraagd.
Statistieken
De technische opslag of toegang die uitsluitend voor statistische doeleinden wordt gebruikt. De technische opslag of toegang die uitsluitend wordt gebruikt voor anonieme statistische doeleinden. Zonder dagvaarding, vrijwillige naleving door uw Internet Service Provider, of aanvullende gegevens van een derde partij, kan informatie die alleen voor dit doel wordt opgeslagen of opgehaald gewoonlijk niet worden gebruikt om je te identificeren.
Marketing
De technische opslag of toegang is nodig om gebruikersprofielen op te stellen voor het verzenden van reclame, of om de gebruiker op een website of over verschillende websites te volgen voor soortgelijke marketingdoeleinden.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
Voorkeuren
{title} {title} {title}