Loading ...
Sorry, an error occurred while loading the content.
57754
Looking for Change Hi Friends, I have started looking for change, so reaching out to your all, who know me and can vouch for me.  I am looking for opportunities and Project /
Rakesh Pandey
Apr 11
#57754
This message has attachments
  • DOC
    324 KB
    RakeshP.docx
57753
Re: More critical views on SAFe Hallo Charles, I didn't know you were in the hotbed of Scrumming (Denver). So I'm sure you'll jaw jaw with Mr Spearman.  Hallo Steve, Please see the thread
srinivas chillara
Apr 7
#57753
 
57752
Re: More critical views on SAFe Thanks to all for the feedback.  Lafable was actually on the original list that I sent, but I'm thrilled that you all highlighted it anyway. Srinivas, I'm
Charles Bradley - Professional Scrum Trai
Apr 6
#57752
 
Fetching Sponsored Content...
57751
Re: More critical views on SAFe Yes, the list is longer than most people would have patience for (I ddin't read all of that). However I did Ron Jeffries' article and it is very thoughtful.
srinivas chillara
Apr 3
#57751
 
57750
Re: More critical views on SAFe http://lafable.com/ was one of the best spoofs I've seen in a while. Kudos to Mike and team - my side still hurts. :-) Charles, thanks for compiling/keeping a
Mark Palmer
Apr 3
#57750
 
57749
xWin2
Apr 2
#57749
 
57748
Re: More critical views on SAFe That list is pretty good. IÆm still wondering how http://lafable.com got banned from Twitter. Though itÆs not as thorough as the others (particularly the
Michael James
Apr 2
#57748
 
57747
Re: More critical views on SAFe Hi Charles, You missed the Large Agile Framework Appropriate for Big, Lumbering Enterprises - L.A.F.A.B.L.E. http://lafable.com/ Chooooo-chooooooo Best Markus
Markus Gärtner
Apr 2
#57747
 
57746
More critical views on SAFe I'd like to highlight a couple of recent additions to the (moderately to mostly critical) views on SAFe:
Charles Bradley - Professional Scrum Trai
Apr 2
#57746
 
57745
Re: Retrospective activity for understanding commitments I agree completely. People (i.e. management) can use the team's "commitment" for business and resource management reasons which often results in the
Cass Dalton
Mar 14
#57745
 
57744
Re: Retrospective activity for understanding commitments I have discovered that teams sometimes over commit because they underestimate and they underestimate because they have not gotten good at decomposition.
Cass Dalton
Mar 14
#57744
 
57743
Re: Retrospective activity for understanding commitments Hi all, I agree you're going to get the most value out of examining the missing commitments if the team self-identifies that as an issue. Another exercise that
Tim Wright
Mar 14
#57743
 
57742
Re: Retrospective activity for understanding commitments Hello, Kurt, ... The word does not occur in the Scrum Guide. That does not mean that everyone agrees it should have been removed. Many prefer it. I think
Ron Jeffries
Mar 14
#57742
 
57741
Re: Retrospective activity for understanding commitments Has no one mentioned that there is no longer commitment in Scrum? It has been replaced with the much more reasonable ôforecastö. Commitment never sat right
Kurt Häusler
Mar 13
#57741
 
57740
Re: Retrospective activity for understanding commitments I wouldn't attempt to direct the retrospective towards missed commitments. Talk about what you are currently doing that works well, and solicit some ideas
Adam Sroka
Mar 13
#57740
 
Fetching Sponsored Content...
57739
Cass Dalton
Mar 13
#57739
 
57738
Re: Retrospective activity for understanding commitments Hi Greg Can you tell us what sort of commitments that the Team are not meeting please? There is a common misunderstanding about commitments! Regards
steveatootac
Mar 12
#57738
 
57737
Re: Retrospective activity for understanding commitments Greg, MikeÆs Speedboat suggestion is often a good tool to use. Can you tell us a little about how you are doing retrospectives now and what is coming out of
Chet Hendrickson
Mar 12
#57737
 
57736
Re: Retrospective activity for understanding commitments Take a look at the speedboat or similar activity from innovationgames its a great book and there are other resources available. Thank you. Mike Vizdos
Michael Vizdos
Mar 12
#57736
 
57735
Retrospective activity for understanding commitments Hi - I'm looking for a retrospective activity that can help dive into what is causing a team to miss its commitments. Any suggestions? Thanks! Greg
Greg Robinson
Mar 12
#57735
 
57734
Re: Handling small change requests I agree with Jesse . Our teams have successfully done that and are doing it consistently . This gives customer a lot of confidence . Cheers Kannan
Rajaraman Kannan
Feb 27
#57734
 
57733
Re: Handling small change requests Why not let them see it in action sooner then? If the customer wants it changed, then pick that up in the next sprint right at the start and produce an early
Jesse Houwing
Feb 27
#57733
 
57732
Re: Handling small change requests "badly done / bad product?" - quite often the customer isn't 100% clear what they want until they see it in action (which is after the sprint). There is post
Cormac Trant
Feb 26
#57732
 
57731
Re: Handling small change requests i think it is mostly UI/UX changes which is difficult to accommodate in on going sprints. ... -- Mohammad Asif Project Lead Azri Solutions
Asif Noor
Feb 25
#57731
 
57730
Re: Handling small change requests ... What does *small tweak* mean ? Does it mean * badly done ? * bad product ? ?, Thierry
thierry henrio
Feb 25
#57730
 
57729
Re: Handling small change requests Matt, ... The problem seems to be having a UAT *phase* rather than a UAT *activity*. How could you get the feedback you need earlier? Could these people look
George Dinwiddie
Feb 14
#57729
 
57728
Re: Handling small change requests mattellenburg, ... "The heart of Scrum is a Sprint, a time-box of one month or less during which a 'Done', useable, and potentially releasable product
Charles Bradley - Professional Scrum Trai
Feb 13
#57728
 
Fetching Sponsored Content...
57727
Re: Handling small change requests One other thing is to talk to the team about how they think they can do this! Thank you. Mike Vizdos www.michaelvizdos.com/contact
Michael Vizdos
Feb 13
#57727
 
57726
Re: Handling small change requests Hi Matt, ... A Sprint is a FIXED-LENGTH period of time. The reason for the time box is that it causes the team to learn how to hit a deadline with software
Ron Jeffries
Feb 13
#57726
 
57725
Re: Handling small change requests Hi Steve, Thank you very much for giving better clarity on this point. Best Regards, -Vikram
Vikram Boidapu
Feb 13
#57725
 
View First Topic Go to View Last Topic
Loading 1 - 30 of total 57,754 messages