This document discusses various tools, techniques and best practices for Scrum project management including using Jira and burn down charts for tracking progress, conducting regular retrospectives with cross-functional teams, gathering requirements through interviews and prototypes, designing systems with architectural diagrams and managing stakeholders by addressing their needs and concerns. It also covers topics like Scrum team metrics, facilitating collaboration between developers and Scrum Masters, defining project milestones and information gathering before starting new projects.
This document discusses various tools, techniques and best practices for Scrum project management including using Jira and burn down charts for tracking progress, conducting regular retrospectives with cross-functional teams, gathering requirements through interviews and prototypes, designing systems with architectural diagrams and managing stakeholders by addressing their needs and concerns. It also covers topics like Scrum team metrics, facilitating collaboration between developers and Scrum Masters, defining project milestones and information gathering before starting new projects.
This document discusses various tools, techniques and best practices for Scrum project management including using Jira and burn down charts for tracking progress, conducting regular retrospectives with cross-functional teams, gathering requirements through interviews and prototypes, designing systems with architectural diagrams and managing stakeholders by addressing their needs and concerns. It also covers topics like Scrum team metrics, facilitating collaboration between developers and Scrum Masters, defining project milestones and information gathering before starting new projects.
o Jira, Trello, VersionOne for backlog management. o Burndown Charts, Velocity for tracking progress. 2. Scrum Best Practices: o Regular retrospectives. o Cross-functional teams. o Time-boxed iterations. 3. Scrum Team Key Metrics & Reports: o Velocity: Work completed per sprint. o Burn-down Chart: Remaining work over time. 4. Project Architecture: o High-level design of the system. o Components, modules, and interactions. 5. Stakeholder Management: o Identify stakeholders. o Understand their needs. o Communicate effectively. 6. Handling a Tough Stakeholder: o Active listening. o Address concerns empathetically. o Find common ground. 7. Requirement Gathering Tools & Techniques: o Interviews, Workshops, Surveys. o Prototyping, Use Cases, User Journeys. 8. Design Planning of IT Systems: o Architectural Diagrams, Flowcharts, Wireframes. o Design Patterns, Component Diagrams. 9. Approaching a Dev Developer as a Scrum Master: o Understand their perspective. o Facilitate collaboration. o Remove obstacles. 10. Project Delivery Milestones: o Key points in the project timeline. o E.g., alpha release, beta release, production launch. 11. Information Gathering Before Starting a New Project: o Business Case, Stakeholder Analysis. o Project Charter, Risk Assessment. 12. Implementation Techniques: o Big Bang, Phased, Pilot, Parallel.