Its defiantly assumes we don't mind working weekends! On 6 January 2017 at 17:06, Marc-Andre Carbonneau < marc-andre.carbonn...@ubisoft.com> wrote:
> Oh and I know Jira looks very ugly to artists but you can customize it to > make it work and "look" the way you want. > ;) > > -----Original Message----- > From: softimage-boun...@listproc.autodesk.com [mailto:softimage-bounces@ > listproc.autodesk.com] On Behalf Of Marc-Andre Carbonneau > Sent: January-06-17 11:45 AM > To: Official Softimage Users Mailing List. https://groups.google.com/ > forum/#!forum/xsi_list <softimage@listproc.autodesk.com> > Subject: RE: Using Agile Scrum in vfx production > > I don't believe this was mentionned yet but Jira from Atlassian is a very > good task tracking tool and has all the Agile methodology implemented > (Kabaan waterfalls, Agile etc...) and about 3 years ago, Shotgun > implemented a way to talk to Jira. Might be worth checking it out. Haven't > tested myself yet and now I can't find it on Shotgun's website... :S > > MAC > > -----Original Message----- > From: softimage-boun...@listproc.autodesk.com [mailto:softimage-bounces@ > listproc.autodesk.com] On Behalf Of Maurice Patel > Sent: January-05-17 1:40 PM > To: Official Softimage Users Mailing List. https://groups.google.com/ > forum/#!forum/xsi_list <softimage@listproc.autodesk.com> > Subject: RE: Using Agile Scrum in vfx production > > It is hard to say - it is whatever tools work best for you and your team > to understand the scope of the backlog. It could well be a whiteboard that > you update every meeting to start. I'd at least start there for a few > tests. Once you get an understanding for it and feel it works you can > formalize it with some digital tools. This is actually not really the hard > part of agile. > > There are a few other things to take into consideration when implementing > agile: > - How ready is the team to change the way they work? If the team is > hierarchical or you have team leaders who very much want to be in control > (micromanage) it is going to take a cultural shift in the team before agile > can be successful > - How good is the team at scoping work? The better you are at that the > easier it is to migrate to agile methods > > Scrum works well when everyone is aligned as to what needs to get done its > priority and its effort. The meeting than can focus on impediments and > resolving them. This is the real value of agile the continual course > correction that can happen on a daily basis. But its only effective if > everyone has a voice and everyone has a common if understanding on terms > and scope. Agile works badly if you spend the entire meeting discussing how > long it takes to do each task. > > You also need a strong scrum master to keep meetings on track (they are > facilitators not managers but they need to be empowered) and the product > owner (vfx sup) needs to understand their role is not to micromanage or > even to direct the scrum but to provide guidance on what needs to be done. > So team dynamics are pretty critical here. The product owner defines what > needs to be done - the scrum team figures out how much it can do and how it > needs to be done. > > You will have to go through several sprints before you can figure out > exactly how much can be done realistically and whether you are scoping > correctly. > > The challenge is that agile is a means of fast iteration and collaboration > - but to work you actually need to establish some things well in advance - > such as methods of scoping and prioritizing work. Agile methods can provide > tools for that too - such as epics and stories that are used to define the > importance of a feature set - but you can use your own. An important thing > to consider is ROI of work. Although it is impossible to actually quantify > you typically need some way of establishing the value of different types of > work. Having a good knowledge of the priority, effort and ROI of every item > in the backlog leads for much easier discussions > > Maurice Patel > Tél: 514 954-7134 > Cell: 514 242-6549 > > -----Original Message----- > From: softimage-boun...@listproc.autodesk.com [mailto:softimage-bounces@ > listproc.autodesk.com] On Behalf Of javier gonzalez > Sent: Thursday, January 05, 2017 12:43 PM > To: Official Softimage Users Mailing List. https://groups.google.com/ > forum/#!forum/xsi_list <softimage@listproc.autodesk.com> > Subject: Re: Using Agile Scrum in vfx production > > About the implementation, its better a simple white board for the kanban > board or use some agile tools for this and to calculate a burndown chart > etc? > Thank for the link maurice, i think i will ask to some software > development friends. > > 2017-01-05 11:42 GMT-05:00, Maurice Patel <maurice.pa...@autodesk.com>: > > It is an interesting article and as pointed out VFX shares a lot of > > commonality with the problems faced in software development where > > iterations, ‘feature creep,’ the subjective nature of product quality > > and disparate stakeholders create complexity and a high potential for > > budget and scheduling overruns. > > If you are interested in Agile methods such as Scrum and Sprints you > > can also find out more on websites like this one: > > https://www.versionone.com/agile-101/agile-methodologies/ > > This is just one of many companies that provides services in > > implementing Agile methods but they provide some background material > > into Agile methods on their website. Googling a bit will unearth more. > > The principles of Agile are reasonably simple – the trick is getting > > them to work for you. Ideally the system you develop will be adapted > > to your needs and it is not really a standard formula that can be > > applied generically. The usual advice is pick one or two projects and > > try to implement agile methods on them first – projects with low risk > and a high chance of success. > > Learning from that process should then enable you to deploy more broadly. > > Finding the right tools that work the best in your company is a > > discovery process. You can teach yourself (takes longer and has the > > potential for a lot of hiccups but definitely doable) or find someone > > with some experience in implementing agile methods and a good knowledge > of how you work to help. > > A scrum meeting is typically held daily, often at the start of the > > day, with all key stakeholders and its main goal is prioritize and > > align on the backlog (generic term for what needs to get done). > > However for the meeting to work the tools used to document and measure > > the state of the backlog need to be accurate and appropriate – and > > that is the real challenge of the implementation – which is why the > > FXGuide article focuses quite heavily on that aspect > > > > Maurice Patel > > Tél: 514 954-7134 > > Cell: 514 242-6549 > > > > From: softimage-boun...@listproc.autodesk.com > > [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Thomas > > Volkmann > > Sent: Thursday, January 05, 2017 9:30 AM > > To: Official Softimage Users Mailing List. > > https://groups.google.com/forum/#!forum/xsi_list > > <softimage@listproc.autodesk.com> > > Subject: Re: Using Agile Scrum in vfx production > > > > Very interesting read! > > Being new to that topic, Alok could you share some insight what a > > typical scrum looks like (how long does it take, is it at the start or > > the end of the day, etc). > > > > /Thomas > > > > Alok Gandhi > > <alok.gandhi2...@gmail.com<mailto:alok.gandhi2...@gmail.com>> > > hat am 5. Januar 2017 um 07:43 geschrieben: > > The article explains it all! Extremely well-written. Having been a > > member of the agile team, I can say that this is sounds very > > interesting for VFX Project Management. We use agile (though for > > software development for animation), our typical sprints are 7 days or > > 14 days. Scrums are every day. > > ------ > > Softimage Mailing List. > > To unsubscribe, send a mail to > > softimage-requ...@listproc.autodesk.com<mailto:softimage-request@listp > > roc.autodesk.com> with "unsubscribe" in the subject, and reply to > > confirm. > > > > > > > > ------ > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > with "unsubscribe" in the subject, and reply to confirm. > > > ------ > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > with "unsubscribe" in the subject, and reply to confirm. > > ------ > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > with "unsubscribe" in the subject, and reply to confirm. >
------ Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
