a business context • Have 3 levels (or sprint’s if you prefer) - increasing in complexity. Please do not feel you need to complete all 3 – stop at any level. But, try to complete at least one level. • May have some resources to help you • Are realistic. They are the type of thing that you will be faced with on a regular basis as a professional developer Our scenarios…
after you've read each one... • Stop and think about it • Try to get the feel of it • Discuss it with others – everyone sees things differently • You will naturally gravitate towards one or more scenario's - but don't decide too soon! Start small
is right for the team • Identify what you are being asked to do • Tasks - split the problem into small manageable tasks • Options - what are the technical options available to you? • Re-read the scenario! Planning
is right for the team • Identify what you are being asked to do • Tasks - split the problem into small manageable tasks • Options - what are the technical options available to you? • Re-read the scenario! Planning
Small, Medium & Large is fine • Your estimate depends on your skillset and your experience, as well as the problem • It is your estimate – NOT someone else’s • The original estimate you give may change as the project progresses – this is normal • Your estimates get more accurate over time Estimating
the team have the right skill set and experience to handle the scenario? • Do you have people on the team who don’t need to be there? • Do you have people on the team who are likely to dominate – especially during the implementation phase? • Your team needs to work as a team – can they? The bottom line is only you and team can tell! Decide if the scenario right for the team
Understand how all the pieces fit together • Work as a team • Remember - you are not alone! If in doubt, something isn’t clear or you have questions - ask an expert Implementation