Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
From Vision Statement to Product Backlog
1. From Vision Statement to Product Backlog: An Effective Way to Quickly Develop Project and Product Requirements Luiz Cláudio Parzianello [email_address] Brazil Scrum Gathering São Paulo, Brazil, 13/05/2009
6. So, how can I explore this “VALUE” in a Vision Statement? A Software Product
7. A Software Product It would be a software product a kind of resource to support a transformation in a business environment?
8. How a business process can help me to define a transformation scenario?
9. A Business Process Business Process Software A1 A2 A3 A4 A5 A6 Customer Customer People Tools Materials RESOURCES Requests Information Norms Regulations Indicators Procedures POLICIES Products Information Services Project targets User
10. A Business Process A1 A2 A4 A5 I1 I2 S1 S2 O1 O2 T1 T2 A3 M1 M2 C1 C2 AS IS A1 A2 A4 A5 I1 I2 S1 S2 O1 O2 T1 T2 A3 M1 M2 C1 C2 TO BE A project is a transformation process! Where you can find compliments ... Where you can find complaints ...
11. How can I structure a strategy for the transformation process?
12. Present State (PROBLEM) A Strategy of Change S.C.O.R.E. Model The minimum amount of information that needs to be addressed by any process of change or healing . Robert Dilts & Todd Epstein (1987) Complaints about bad results or unaddressed opportunities ( Symptoms ) Transformation Desire State (GOAL) The most noticeable and conscious aspects of a Goal ( Outcomes ) Rationale for the transformation ( Effects ) Underlying elements responsible for creating and maintaining symptoms ( Causes ) Underlying elements responsible for removing causes ( Resources )
13. Where? When? With whom? Logical Levels of Learning and Change Robert Dilts based on Gregory Bateson A Strategy of Change Environment When we find a problem at a particular level … … we can solve it at the next upper level! “ Bad behaviour can generate bad results … Good behaviour can generate good results!” Spirituality Purpose What do you do? Behaviour is perceived by my senses triggering a Capabilities and Strategies How do you do? is a conscious action supported by Who are you? Identity and Mission Are unconscious responses based on Why do you do that? Beliefs and Values are semiconscious actions based on personal
14. How can I write a story for the whole project using these models?
15. A Project Story Who are associated with the problem? When does the problem usually happen? Where can we see the problem? What is the mode or situation the problem occurs? How many times the problem usually happen? Why is the problem happening in your business? What is your problem?
16.
17. A Project Story THE PROJECT CHARTER: 1x A3 or 2x A4 Form Project Identification Present Scenario Desired Scenario Critical Success Factors Product Scope Cost Estimates
18.
19.
20.
21. A Project Story This is what we need to start the project … A1 A2 A4 A5 I1 I2 S1 S2 O1 O2 T1 T2 A3 Pre-Requirements (Setups) M1 M2 C1 C2 PROJECT Execution Conditions (Policies) Alternative Solutions Potential Risks This is what we consider to run the project … This is what we consider as project threats and impediments … This is what can be done if we face that problem …
22.
23. A Project Story Scrum Master Developer To lead the technical team and run business analysis Team members to develop System A 1 3 5.000,00 2.500,00 5.000,00 7.500,00 14.100,00 Computers For the technical team 4 1.000,00 4.000,00 Designer To conceive and prototype a GUI 1 3.000,00 3.000,00 10.000,00 Server Repository, Continuous Integration, V&V 1 3.000,00 3.000,00 System A is the critical path (4months) 66.400,00 94.600,00 Developer Team member to implement services in System B 16h 40,00 640,00 Developer Team member to implement services in ESB 16h 60,00 960,00 System A is the critical path (6months) A Unique Team Proportional to the project duration. costs X 4 months X 6 months
25. Software Product Scope Business Process Activity #1 Activity #2 Activity #3 Activity #4 Activity #5 Activity #6 Activity #7 Activity #8 Activity #10 Activity #11 Activity #12 Activity #13 Activity #14 Activity #15 “ Tell me about your activities and I’ll understand your User Stories”
26.
27.
28.
29. Software Product Scope Project Story Project Identification Present Scenario Desired Scenario Critical Success Factors Product Scope Cost Estimates Business Theme #3 Business Theme #2 User Story #3 User Story #2 User Story #1 Project Scope Process Scope Business Theme #1
30.
31. Thanks and enjoy your project! Luiz Cláudio Parzianello [email_address]
Hinweis der Redaktion
Este primeiro encontro com os Analistas de Sistemas tem como objetivo principal provocar nos participantes uma reflexão sobre os seus papéis e suas responsabilidades nas dificuldades que eles encontram no dia-a-dia. Ou seja, é fato que os Analistas de Sistemas encontram dificuldades em suas atividades devido à estrutura e demais recursos que eles tanto necessitam para tornarem mais eficazes suas tarefas. Por outro lado, também é fato, que as maiores dificuldades e limitações se encontram nos processos de comunicação e nos relacionamentos entre colegas, gerências, programadores e demais atores no processo de desenvolvimento de sistemas da informação.