![]() ![]() Because of the added complexities of the refugee and immigrant context, a deep understanding of their realities is needed. My advice would be to keep key guidance artifacts (such as project objectives, product roadmap, solution architecture) high level, lightweight and visual, and stick them on the wall along with the team’s User Stories and daily tasks.Providing contextually appropriate care and interventions for people with diabetes and/or obesity in vulnerable situations within ethnocultural newcomer communities presents significant challenges. So, in summary, an agile development team might break things into small pieces and deliver incrementally, but this makes it even more important to have the overall context always in mind. In my view, this can be an evolving picture, the kind of thing that is sketched on a whiteboard at the start of the project, with more details being filled in as the project progresses and as technical decisions are taken. High-level Solution Architecture – this doesn’t need to be a detailed design, but you do need some architectural guidance in order to understand key technologies, product structure and how the overall solution hangs together from a technical perspective.But it’s a guide to what’s intended at the outset, and should cover the main scenarios for an everyday user. And the solution may not look exactly like the visuals when it’s finished. The visuals don’t need to cover every single screen. Whatever form it takes, it’s a high level outline of how the solution will hang together from a user’s perspective. High-level Visuals – this could be wireframes for key screens, Creative visuals of a web site, a conceptual story board for the UI (User Interface), etc.This provides the team with some structure around Sprint Planning, with the Product Roadmap helping to inform the priorities of each Sprint and set Sprint Goals. Unlike a plan, a Product Roadmap is indicative and evolves as things change. High-level Product Roadmap – broad timeline across the top, perhaps in months or quarters highlighting key product features or milestones.So what artifacts help us to do this? There may be others, but here are some things I certainly like to see before getting down to User Stories on a Sprint-by-Sprint basis: It is important to look at individual User Stories in context of the overall solution. But what should you do before you get down to the detail of individual User Stories? I’ve written quite a few entries on my blog about them recently, and how to write good User Stories. With this guidance, the project team has some parameters to work within, and a clear understanding of the expected outcomes. And that guidance is more important than ever in an agile development approach, because of the freedom to change things along the way. The answers to these questions (and more, of course) give people important guidance. What is the specific problem or opportunity that the project is seeking to address? What is the vision for the project? What are the project objectives? What is the scope (broadly speaking)? What is the likely cost and timeframe? What are the benefits and how will they be realised? Who will work on the project and what is the project structure? If the development team is working on a project, many of the things defined in a more traditional project initiation phase are just as important in an agile development environment. Without necessarily being asked to work on a problem, or without being asked to come up with an idea, solutions to problems and new innovations will come to mind. With this information – if development teams have a real insight into the business context – people on the development team can be proactive. In my experience, development people can be quite innovative. Without this over-arching contextual information, any product development team is working with a major disadvantage. What is the business vision? What are the challenges and opportunities from a business point of view? What are the business goals – short, medium and longer term? Who are the customers? Why do they buy, and what do they use the solution for? What do they like and dislike about the product? Who is the competition and what are their solutions like? So, with this moving target, how do you keep sight of the bigger picture?Īlthough agile development is all about breaking things down – breaking things down into micro pieces and delivering on a piecemeal basis – it is also very important to have some overall guiding context.įrom my perspective, this context comes in 3 major forms: ![]() Features can be added, changed and removed throughout the project lifecycle. With an agile development approach, there is no big spec and no big design up-front. ![]()
0 Comments
Leave a Reply. |