1 / 28

מסגרת הפרויקט

מסגרת הפרויקט. הפרויקט מחולק ל – 4 גירסאות (שניים בסמסטר, 6 שבועות כל גירסא ) גירסא 1 – תכנון על ואב-טיפוס גירסא 2-4 – פיתוח באג'יל תוך יישום עקרונות מסקראם וקאנבן שבוע אחרון – סגירת פרויקט, ייצוב, יישור מסמכים וכד' כל גירסא מחולקת לשלש איטרציות של שבועיים ) סה"כ 6 שבועות)

kasper-blair
Download Presentation

מסגרת הפרויקט

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. מסגרת הפרויקט • הפרויקט מחולק ל – 4 גירסאות(שניים בסמסטר, 6 שבועות כל גירסא) • גירסא 1 – תכנון על ואב-טיפוס • גירסא 2-4 – פיתוח באג'יל תוך יישום עקרונות מסקראםוקאנבן • שבוע אחרון – סגירת פרויקט, ייצוב, יישור מסמכים וכד' • כל גירסא מחולקת לשלש איטרציות של שבועיים ) סה"כ 6 שבועות) • בסוף כל איטרציה תהיה הדגמה (בשיעור הראשון של האיטרציה הבאה) • במהלך האיטרציה תהיינה פגישות פרטניות עם הצוותים לבחינת תוצרי ביניים והתייעצויות • יוקם Scrum Master forum עם ה- scrum masters של הצוותים השונים להנחיות והתייעצות לגבי התהליך האג'ילי בצוות.

  2. תוכנית פיתוח – גירסא 1 (בקלוג ראשוני, תכנון על)

  3. גירסא2 - פיתוח ה-Minimal Viable product

  4. Why Agile ?

  5. The Magic Circle… • Methodologies to make the software development process more disciplined and predictive: • More planning • Tie down scope and sign-off • Detailed and documented design before coding • Strict change control to suppress change During the last 40 years there is a high failure rate in software development projects The Arms? The Results?

  6. Poor Success Rate! Why? Need a methodology that conforms to the paradigms

  7. Software Development Paradigms • Traditionally, software development projects are built around false assumptions: • The customer knows what he wants and what the system should do (and understand specs) • The system analyst /architect can describe the solution in unambiguous way • The developers understand the specifications and know how to estimate and build them • There will be no changes along the way

  8. Why Agile ? Because almost everything is changing Scope Our understanding Our estimates Organizational constrains And we must have new framework that based on this new paradigm

  9. In a world of moving targets… • Waterfall is like a cannonball • Agile is like a homing missile Source: HenrikKniberg

  10. The main reasons that software delivery organizations implement Agile development are* The need to manage rapidly changing priorities The need to accelerate time-to-market The need to increase productivity The need to improve quality Efficient Integration and portfolio alignment Improve visibility into the development lifecycle Agile! * Survey conducted by VersionOne and The Agile Alliance in August 2006 on “The State of Agile Development”. The findings are based on working with thousands of Agile teams around the world.

  11. What is Agile?

  12. Agile Manifesto - 2001 • individuals and interactions over processes and tools • working software over comprehensive documentation

  13. working software over comprehensive documentation Req Design Code Test The waterfall approach The Agile way Surprise ! Value to the customer Risk reduction

  14. Agile Manifesto - 2001 • individuals and interactions over processes and tools • working software over comprehensive documentation • customer collaboration over contract negotiation • responding to change over following a plan While there is value in the items on the right,we value the items on the left more

  15. Agile is all about early feedback – why? • What is the most expensive bug ?

  16. Split your organization Agile in a nutshell Split your product • Large group spending a long time building a huge thing • Small teams spending a little time building a small thing • ... but integrating regularly to see the whole Optimize process Optimize business value $$$ Split time January April $ Henrik Kniberg

  17. Agile Release lifecycle

  18. Scrum - Potentially releasable code delivered every 2-4 weeks

  19. Scrum • Product Owner • Scrum Team • Scrum Master Iteration Daily Meeting Scrum Planning Session Committed USs + Tasks Sprint Sprint Demo GA Retrospective Iteration Backlog (team level) (USs) Release Planning (Epics & USs) Release Backlog Scrum Flow Timeboxes, Roles, Rules

  20. Product Discovery • Discovery – understanding the right product to build. • Delivery – building the product right

  21. Source: Naresh Jain, Product Discovery Workshop

  22. The Agile Inception Deck Template http://agilewarrior.wordpress.com/2010/11/06/the-agile-inception-deck/

  23. Project: online road-closure system for mapping which roads were closed by date on a given construction site Write down all the reasons why your company would want to spend money on this project in the first place. Then pick and highlight the most important one.

  24. Elevator Pitch/Handshake Pitch Imagine… you walk into an elevator and one of the key influencers in the company is standing beside you. You have 90 seconds to explain: • What are you building and why? • + what are benefits • + how it differs from competitors Must be: short and memorable

  25. Elevator Pitch Template For (insert your target market) who need (insert key requirements of your target market) we provide a (insert type of your product / solution) that is (insert key features or aspects of your product or solution) unlike (insert competitors) our (insert type of your product or solution again and add key differentiators) * Template from Geoffrey Moore’s Crossing the Chasm

  26. The elevator pitch

  27. Product box <product name> fun picture <slogan> Point here is to get your team looking at your project through the eyes of your end customer. <benefit #1> <benefit #2> <benefit #3>

  28. The NOT list Before starting your project move all the UNRESOLVED ones to either IN or OUT.

More Related